If you are speaking about the people publishing this on Danbooru, then fair.
If you are speaking about MentalEdge, then you underestimate the time this would accumulate if done for every of their daily posts. As an example I spend over 5 hours a month (approximate guess, as I do it in big batch sessions and the last one was last month, so I can’t remember well) searching for images and processing them into posts. And most of the processing (lookup of title, tags, artist socials, composing the body text) is already done by automated software.
Right. The links, title, and ensuring the image data is intact to preserve reverse-searchability (which your file destroyed, while failing to maintain the metadata when actually hosted) is wildly insufficient.
If you are speaking about the people publishing this on Danbooru, then fair.
If you are speaking about MentalEdge, then you underestimate the time this would accumulate if done for every of their daily posts. As an example I spend over 5 hours a month (approximate guess, as I do it in big batch sessions and the last one was last month, so I can’t remember well) searching for images and processing them into posts. And most of the processing (lookup of title, tags, artist socials, composing the body text) is already done by automated software.
MentalEdge can automate everything posted from danbooru (the source) to XMP, and more.
But why? Why would I do that?
Especially as literally no one ever looks at that on lemmy, and a fraction of the fraction of people who save the images do it.
Not to mention the poor survivability of such metadata when hosted, federated, proxied, thumbnailed, or worse, screenshotted.
If you want neatly organized files, I suggest writing a danbooru ripping script yourself.
Why would I bother to do that for you? As you’re essentially the sole case that would benefit.
I will soon enough.
Same reason @age_jaco isn’t in your basement: Accreditation.
Right. The links, title, and ensuring the image data is intact to preserve reverse-searchability (which your file destroyed, while failing to maintain the metadata when actually hosted) is wildly insufficient.