-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
🚀 Feature: Automatically strip exif data on upload #5950
Comments
@d4rckh, thanks for raising this request! 🙏🏼 For now, I would recommend:
The function can be useful to do any sort of post-processing of the file including resizing to reduce the file size. For an example, check out Building a Location-Based App with Appwrite. |
Thanks for the suggestion! Hopefully it will also be added into appwrite :) |
I wonder if we should force this check for every image being uploaded or enable this as a feature that can be turned on and off. Would love to hear feedback and learn more about use cases where exif data is crucial for the application. |
@eldadfux In my opinion this would be good as a toggle. EXIF data could be crucial if your app needs the GPS coordinates, like displaying where photos were taken on a map. It's possible to unset specific parts of EXIF data too, so if enabled, we can remove sensitive data but keep information crucial to displaying the image correctly like rotation/contrast/saturation etc. |
🔖 Feature description
When an image is uploaded to a bucket, the server will automatically strip exif data on images, similarly to how they get compressed. A toggle would be added (perhaps under compression) that enabled would remove the sensitive information embedded in images (location, model, camera specs, etc).
🎤 Pitch
This is a highly important feature for every app in which images get uploaded (avatars, chat, posts, etc.). Any platform that accepts images does strip exif info to protect its users from accidentally leaking sensitive info.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: