Opened 13 years ago
Last modified 11 years ago
#94 closed defect
exif data handling for users — at Initial Version
Reported by: | Deb Nicholson | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | |
Component: | programming | Keywords: | |
Cc: | deletesoftware@… | Parent Tickets: |
Description
At some point, we will need to address exif data. I think it would be nice for the user to be able to access and search for their exif data, but we also want to be able to let the user scrub it before posting to their network. The best case is where the user has access to exif data by default and the viewer does not. Usecase 1: I want to search for all the photos from my trip to Greece 4 years ago using my exif data. Usecase 2: I do not want people to access the exif info for my kid's elementary school or my company's colo. Usecase 3: I want to see the exif info for last year's awesome mushroom foraging spot, but absolutely do not want it made public. Finely tuned control of exif data would represent a tangible feature that we could offer that is not offered by flickr. I don't have a strong opinion about how this would look on the back end. On the front end it should be very clear what's happening and the default should be to strip it out before posting so no one posts exif data unless they specifically choose to.
Note:
See TracTickets
for help on using tickets.