It’s a real bummer that so much EXIF data get scraped away from images on the internet (right up there with stripping color profiles)–with photographs, there’s a lot of cool information to be learned from location, to license, to camera lenses. We need a better way to expose that data rather than making users re-enter that data (or do it incorrectly by accident). Obviously not all images or formats need this, but others could benefit.
Unlike with color profiles, retaining EXIF data can be a huge privacy issue. Sharing a photo on the Internet I took at home shouldn’t mean revealing my address to everyone who has the image.
Can. It can also help others find interesting locations. I think if it were visible, folks might remember to scrape that data on more private photos.
It’s much better to make it opt-in, like Flickr does.
You won’t hear me disagree with that! Blind stripping is what drives me mad–especially when the license is stripped which has legal implications or the color profile which now renders the image not as intended. I find it strange a open protocol like Pixelfed strips this since it supposed to be displaying largely photos people take and I assume this is done for size, but it still feels off.
Ok, but all of this is sh, not emacs, right?
it is about emacs letting you compose the functions provided by the utilities, provide ways to trigger (M-x or even a key combination when used often), and provide a presentation of the result.
As an Emacs user, if the feature is well integrated and useful, I’m not too fussy about its implementation.
The feature, though using a tiny shell script and command line utility, is surfaced via Emacs M-x. It knows whether to apply functionality to current image buffer or file selection in dired. When I use it, I interact with Emacs.
Or really, perl (exiftool).