Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we have a section on privacy recommendations when sharing images? #189

Open
leo-barnes opened this issue Mar 10, 2022 · 1 comment
Labels

Comments

@leo-barnes
Copy link
Collaborator

There are many features in HEIF that can have privacy implications. In many cases these implications apply to all image formats, but some are specific to the features enabled by HEIF. Many of the features are genuinely useful (storing depth-maps as auxiliary images for instance), so we don't want to forbid them. But it might make sense to have a section on recommended best practices when sharing/editing images.

For example, when sharing or exporting an image for sharing purposes, the following should ideally be done unless the user explicitly does not want it to happen:

  • Location data should be stripped
  • Other types of identifying metadata should be stripped (i.e. author, unless that is used for copyright)
  • Auxiliary images that are not used when rendering the main image (i.e. everything but alpha) should be stripped
  • Image overlays should be flattened
  • Unless user wants to share all images in a collection, all but the selected image in the collection should be stripped
  • If the file contains both a still and video tracks, strip the video unless the user wants to share it
  • Thumbnails that do not match the main image should be stripped
  • Fully transparent pixels should be zeroed
  • Grid padding should be zeroed or replicate the edges
  • The contents outside of 'clap' should be zeroed or replicate the edges

There may be other use-cases that could benefit from having recommendations, but sharing seems like the most obvious one.

@Xredmi

This comment was marked as off-topic.

aarongable pushed a commit to chromium/chromium that referenced this issue Jun 9, 2023
Based on a revert of commit 6c184c0.

Require the clean aperture to be anchored to (0, 0) to reduce privacy
risks. See AOMediaCodec/av1-avif#188 and
AOMediaCodec/av1-avif#189.

Bug: 1167422
Change-Id: I92ffd82d10aeb1321565ed88d07500c74d381e76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4585301
Commit-Queue: Wan-Teh Chang <[email protected]>
Reviewed-by: Dale Curtis <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1155616}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants