post #6125522 http://img0.joyreactor.com/pics/post/full/chibikki-comics-robot-girl-robot-7213476.png
Third-party image sample.
Updated by Unbreakable
Posted under General
post #6125522 http://img0.joyreactor.com/pics/post/full/chibikki-comics-robot-girl-robot-7213476.png
Third-party image sample.
Updated by Unbreakable
post #457692 https://pictures.hentai-foundry.com/c/CMan4/28517/CMan4-28517-Samus.png
Seems to be an image sample? Still researching a little on the artist- they ceased activity since 2011.
Updated by Unbreakable
post #6135958 sample uploaded without source https://cdn.donmai.us/original/6e/63/6e63382c30a8a6bfde747bc2a16266ef.png
Updated by Unbreakable
https://danbooru.donmai.us/posts/6080835
https://files.catbox.moe/2djdw1.png
Fixed up an image with significant compression artifacts.
https://danbooru.donmai.us/posts/6014057
https://files.catbox.moe/d34z9o.png
Fixed compression artifacts. File is also 1/3 the size (8.1 ->2.4 MB).
https://danbooru.donmai.us/posts/5391607
https://files.catbox.moe/gv09mj.png
Artifacts.
https://danbooru.donmai.us/posts/5859136
https://files.catbox.moe/es28rp.png
Artifacts. Not bad unless zoomed, but somewhat apparent.
https://danbooru.donmai.us/posts/5851671
https://files.catbox.moe/7i3h3i.png
Prominent artifacts.
Updated by Unbreakable
Imanaya said:
https://danbooru.donmai.us/posts/6080835
https://files.catbox.moe/2djdw1.png
Fixed up an image with significant compression artifacts.https://danbooru.donmai.us/posts/6014057
https://files.catbox.moe/d34z9o.png
Fixed compression artifacts. File is also 1/3 the size (8.1 ->2.4 MB).https://danbooru.donmai.us/posts/5391607
https://files.catbox.moe/gv09mj.png
Artifacts.https://danbooru.donmai.us/posts/5859136
https://files.catbox.moe/es28rp.png
Artifacts. Not bad unless zoomed, but somewhat apparent.https://danbooru.donmai.us/posts/5851671
https://files.catbox.moe/7i3h3i.png
Prominent artifacts.
@imanaya Not interested in any of your third-party edits.
Updated by Unbreakable
We're not going to replace images with random users' edits just because they have JPEG artefacts. They're typically not even allowed.
Updated by Unbreakable
Which is why you'd try to repair/salvage them if possible, if they're otherwise worthwhile and tagged for potential deletion anyway.
https://danbooru.donmai.us/posts/6014057 in particular seems to be a lossless capture(?) of a lossy image, or was transcoded for some reason.
Updated by Unbreakable
By "they" I'm talking about third-party edits. I figured it would be obvious from context. post #6014057 is the only one that might be acceptable since it doesn't come from an actual artist account, but you threw it in with four that would never be replaced so they all get ignored.
Updated by Unbreakable
Talulah said:
By "they" I'm talking about third-party edits. I figured it would be obvious from context. post #6014057 is the only one that might be acceptable since it doesn't come from an actual artist account, but you threw it in with four that would never be replaced so they all get ignored.
I see.
"but you threw it in with four that would never be replaced so they all get ignored"
That may be how you should expect it actually works in practice, but it's also passed the point where I can reasonably make it my problem. I started going through the tag and saw a few that were easy fixes with clear improvements, I provided them. And that's it.
Although I do appreciate the feedback and advice.
Updated by Unbreakable
ehh said:
post #6142566
https://yt3.ggpht.com/bvWHvbVJ4m930uyTH78Q9AMrIyFtvzPukRdBRxSQVVPHkLrfzbiwEWwzp9EeTnPq12ibUNmW7g4-5g=d
Slight differences...
Updated by Unbreakable
post #1726697 https://danbooru.donmai.us/media_assets/8274225
Tumblr sample.
Updated by Unbreakable
I've noticed some images that have unneccesarily massive filesizes. For example I saw a iirc 3600x5900 png that was 55 MB, most likely the artist or their exporting program just didn't put much effort into compressing the output There are ways of optimizing that which are visually lossless (pixel exact) for most image types. What is the general policy on this?
Updated by Unbreakable
Imanaya said:
I've noticed some images that have unneccesarily massive filesizes. For example I saw a iirc 3600x5900 png that was 55 MB, most likely the artist or their exporting program just didn't put much effort into compressing the output There are ways of optimizing that which are visually lossless (pixel exact) for most image types. What is the general policy on this?
@imanaya Still not interested in any of your third-party edits.
Updated by Unbreakable
RaisingK said:
@imanaya Still not interested in any of your third-party edits.
They wouldn't be edits, and they wouldn't strictly be the originals either. The decoded image output is 1:1 identical, lossless. It's just stored more efficiently.
I suppose overall there's no reason to say it isn't still the original.
Updated by Unbreakable
Imanaya said:
They wouldn't be edits, and they wouldn't strictly be the originals either. The decoded image output is 1:1 identical, lossless. It's just stored more efficiently.
I suppose overall there's no reason to say it isn't still the original.
It changes the md5, so it's an edit and thus not the original file. I.e. after changing the hash, someone else could upload the original file again, creating more duplicates. It'd be a pixel perfect edit, but an edit nonetheless.
Updated by Unbreakable
redtails said:
It changes the md5, so it's an edit and thus not the original file. I.e. after changing the hash, someone else could upload the original file again, creating more duplicates. It'd be a pixel perfect edit, but an edit nonetheless.
True, good point. Doesn't danbooru in addition to direct hash matching also use some other visual similarity metric like iqdb does though? I don't really recall, I vaguely remember it returning matches that were just visually similar. You could hash a decoded output and then store and key to it hashes of different full file uploads which match that decoded hash. Eh, just thinking hypothetically.
RaisingK said:
@imanaya Still not interested in any of your third-party edits.
I actually just want to second the first two in particular.
Imanaya said:
https://danbooru.donmai.us/posts/6080835
https://files.catbox.moe/2djdw1.png
Fixed up an image with significant compression artifacts.https://danbooru.donmai.us/posts/6014057
https://files.catbox.moe/d34z9o.png
Fixed compression artifacts. File is also 1/3 the size (8.1 ->2.4 MB).
The quality of the first one is so bad that solid colored macroblocking and banding is visible without even zooming in. There's not a particular region to point to as it's essentially the whole image. The background, hair, everything has major blocking. Not sure what went wrong, but the artist's jpeg encoder really did a number on what is otherwise a really good work. Check it out, I'd say the method used probably restores it to something closer to what the artist had before they exported it.
The second one, I'm not really familiar with the source. If it was a lossless screenshot of a lossy image, if it was extracted from game files, etc. As it stands, taking the source that exists, I'd say it's not only greatly improved but without the artifacts the file size is reduced by 70%(!). Check out the orange tendril thing that the eye in the center of the frame is attached to for a clear example. The line definition and jpg block noise is much cleaner.
Updated by Unbreakable
If we accepted third-party edits, on the premise that they were "improved" or "losslessly compressed/optimized", it just opens us up for potential data loss when this isn't done correctly. Thus, the safest way to prevent this is to disallow it outright. It's not a criticism against you, and I'm sure that you'd be capable of doing it properly, but editing of source files is just not something that danbooru wants to deal with. For archival purposes, the original source file is the best option.
Storage is very cheap these days, and by default a sample image is shown (instead of the original file), helping to save bandwidth. Though, in your account you can set to disable this behavior. You have good intentions to want to help with reducing storage/bandwidth, but it's not something that you need to worry about. Third party redistributions of danbooru's data, such as gwern's, are of course able to and allowed to run optimizers on their data in an attempt to make redistribution and storage easier.
Updated by Unbreakable
