@falkreon I'm pretty sure removing copyright information is illegal.

@SoniEx2 EXIF has a copyright field that basically nobody uses, and isn't useful in meaningful ways for me as a consumer to look up the author's page to throw money at them. On the other hand, it often contains a whole host of other personally-identifying information like the program that edited it, the OS, the model of camera, and the GPS coordinates a photo was taken at. We *should not* allow users to unintentionally dox themselves.

@SoniEx2 I strongly advise using accompanying text with an image post with a patreon/gofundme/kickstarter/ko-fi link, and that allows people to just boost your post while maintaining attribution

@falkreon That's why you should have an opt-in keep-exif option, and not strip exif from other instances.

@SoniEx2 "Strip exif from other instances" this is literally not a thing you can enforce. You can only strip or not strip from your instance, and federate what you have. Other instances will do whatever other instances do.

@falkreon don't strip incoming exif from other instances.

or, to make everything simple: strip all exif EXCEPT copyright. and add an UI for emoji and images to view exif. clicking an emoji should definitely open its exif.

@SoniEx2 Technology is really bad at solving social problems. I think instances should have much better ways to express their federation, moderation policies, list and attribute their emoji, etc. I'd love to see automated tooling for that. Over-focusing on EXIF (which doesn't even exist for the png/apng that mainline requires for emoji) is a disservice to content creators.

@falkreon I'm pretty sure EXIF does exist in PNG now...

@falkreon oh nvm it hasn't been approved yet.

@falkreon oh nvm that nvm, it has been approved, it's just that there isn't a new version of the png spec.

but eXIf is definitely a png chunk now.

@falkreon https://sourceforge.net/p/png-mng/mailman/message/35943430/

@SoniEx2 Still, it's a poor solution to emoji attribution, one that most users simply won't see. I'd rather put it in a place users can see, which is really about the instance framing - and the instance framing *does* need a lot of work.

@falkreon I wanna be able to click other instances' emoji and view their info from the convenience of the web UI.

@SoniEx2 from the developer console? Yeah, I'd rather it be on the "about this instance" view where *anyone* can see it.

@falkreon no, look at tumblr.

it has a little icon you can click.

now, for emoji, instead of clicking that little icon, you'd just click the emoji, and a new column would open, with the emoji in higher resolution + metadata.

@SoniEx2 That's also acceptable. Another thing I'd like to see is SVG emoji, which would let you pack a lot of metadata into the file while simultaneously keeping the filesize really small, so it's nice for servers, content contributors, and end-users. Everybody wins.

@falkreon yes, please go contribute this to mastodon, with the caveat that it'll be entirely unusable/useless for the time being because mastodon is an exif/copyright/metadata-stripping piece of shit, but at least the groundwork will be there

@SoniEx2 Not a great attitude imo. Hyper-focusing on this exif thing that's not what you really care about, talking shit about the program's design while offering nonviable solutions that put more people at risk is not building this community up into a better place.

@falkreon I would really, really enjoy if custom emoji were more, uh, descriptive I guess.

I don't care how it's done tbh, I just care about opening custom emoji in a column and listing some metadata, like original source, author, license, description, recommended usage, etc.

@SoniEx2 @falkreon let's ***not*** support copyright, actually. legality is irrelevant.

@trwnh @falkreon I support copyleft.