-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add privacy setting to strip EXIF image data on import #2015
Labels
New Feature
A new addition, whose complexity hasn't been evaluated yet
Comments
ProbablePrime
added
the
New Feature
A new addition, whose complexity hasn't been evaluated yet
label
May 9, 2024
github-project-automation
bot
moved this to Backlog
in ProbablePrime's Task Organization
May 9, 2024
ProbablePrime
moved this from Backlog
to In progress
in ProbablePrime's Task Organization
May 9, 2024
Glad it got implemented, thanks for the work. |
Not yet, we're on the way to though! |
Can you please include info in the description that the data can include location? I know that the description mentions GEOTIFF metadata, I just fear that is far too technical for most users and won't understand what that means. |
Sure! |
Updated: Yellow-Dog-Man/Locale@3e24f71 |
I think that works! |
ProbablePrime
moved this from In progress
to In review
in ProbablePrime's Task Organization
May 26, 2024
github-project-automation
bot
moved this from In review
to Done
in ProbablePrime's Task Organization
May 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Requiring users to strip EXIF before they import.
Additional Context
This report came via the ticket desk as a security issue, but I see it as more of a privacy feature, additionally as the FreeImage changes need to be public due to the nature of FreeImage, it makes sense to open a public issue.
Requesters
No response
The text was updated successfully, but these errors were encountered: