Custom Query (1173 matches)
Results (169 - 171 of 1173)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #854 | fixed | exif hangs with 100% cpu on a specific jpg file without any EXIF data | ||
| Description |
File in question is https://www.dropbox.com/s/m5l185qxq9w5mzk/raspberry-pi-gpio-cheat-sheet.jpg My solution involved changing exif extlib to a submodule and updating to the latest, only the last part is actually required to fix the bug of course. |
|||
| #94 | wontfix | exif data handling for users | ||
| 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. |
|||
| #1056 | fixed | endpoints redirect to trailing / endpoint if missing | ||
| Description |
When you request a URL without a tailing / at the end a redirection rather than the content you requested. This should work with or without the / e.g. https://my.gmg.instance/api/user/Tsyesika/feed should resolve to the same endpoint as https://my.gmg.instance/api/user/Tsyesika/feed/ |
|||
Note:
See TracQuery
for help on using queries.
