Danbooru

Image Replacement Request Thread

Posted under General

This topic has been locked.

BrokenEagle98

Mikaeri said:

EDIT: Um, is the parser broken? The markup tags look totally fine to me. (trying to explain to myself the hanging [/quote] thing when quoting forum #139720 and previewing).

Lists need to be closed out with a blank line. Otherwise they can cause issues like the above.

BrokenEagle98

Just a PSA, but I created a new set of tags to indicate problems with an image on Danbooru that necessitates it being fixed.

Eventually there might be an ability given to Builder+ to fix such images if at least the fullsize is good, but until then, making use of the image replacement function will be required.

To start off with, I populated the tag with 6 posts that I found:

md5:cc5967533f5ecb74aa299e82718f88da,17ededa54baf0954bb1efd4dcf0f744b,b4f7c6f4c8483053bc2b51d5333d3250,7d11776455d5e93c31b18a2c6a36db90,152d936a41831b156b6f451d5d1b588a,886cde438c8336d30f71332f47bfba13

or

bad_danbooru_sample

Please replace those at your earliest convenience. Thank you.

nonamethanks

I was not sure where to ask this so I'm posting this here.

I've developed a script to search for pixiv revisions to upload, and in the process I ended up using PIL to detect file difference pixel-by-pixel ( link ). Diff files created with that library end up being solid black boxes if the two images are identical pixel by pixel, which makes it very easy (albeit heavy on CPU and a bit slow) to detect if an image and its pixiv source are visually completely identical.

I was thinking of automatically adding replaceme to these posts, but I then noticed that most of the files tagged with it haven't really been given much attention lately, most likely due to the restructuring of replacement privileges that made them mod-only. (Admittedly, replaceme source:*pixiv* is empty but I'm not sure if it's because nobody used it that way in months or because they are frequently taken care of).

Should still do that? Or would it be better for me to just collect all of the posts with this property and list them all here once I'm done, for someone to replace in batch? (That'll probably take me months at this pace.)

I realize an effortless alternative would be to just leave them alone since there's effectively no difference in them, but the md5_mismatch tag is already pretty bloated and removing some hundreds of posts from there would make it cleaner and also easier to check for revisions/files with real differences, as these identical files have no pattern and must be analyzed one by one otherwise, if one is not manually keeping track of each of them.

Pinging @RaisingK since I can't think of anyone better to ask about this.

RaisingK

I'm not really concerned about md5 mismatch being bloated, and I'm not in the habit of replacing mismatch posts in batch. There is some small amount of appeal to clearing the 'mismatch' status of these verified posts, but I'm not sure it's worth it, so I'll wait for some other opinions.

1 3 4 5 6 7 8 9 10 11 35