Dupe and Broken Image Reports for Anons

Old uploads:  
I) >>2942938t (merged) II) >>2942939t (merged)
 
New Uploads:  
I) II)
 
I) Same resolution except the new is PNG and the old is JPG, but both images didn’t appeared in the duplicate section…
 
II) Both PNG uploads, except the new one is slightly higher res than the old one.

Old upload:https://ponybooru.org/images/2796420  
New Upload:https://ponybooru.org/images/2954056
 
The image uploaded today contained errors which have been fixed

@Tolpain  
Dealt with, apologies for the earlier snafu.

Thank you!

Old Upload: 1114x717 JPG 49 kB  

 
New Upload: 1114x717 JPG 63 kB  
>>2954840t (merged)
 
Same image, same size, same file type. Difference in file size but that might just be something caused by image optimization. If I’m not mistaken a larger file is available from the source anyway:  
IMAGE SOURCE  
IMAGE LINK

old upload: https://ponybooru.org/images/2959011  
New upload: https://ponybooru.org/images/2959059  
updated version
 
This one is the english translation, don’t delete it plz: https://ponybooru.org/images/2959060

Thanks!

Old Upload:  
 
842x776 PNG 245 kB
 
New Upload:  
>>2962739t (merged)  
842x776 PNG 245 kB
 
Same image. Has anyone checked to make sure De-dupe is working?

@Anonymous #4C57  
Yeah, in theory it should be working, but I’m guessing philomena devs decided to tune the sensitivity of the automatic dupe checker. It’s detecting a lot less false positives, but we’re also getting a tonne more false negatives (ie pics not being picked up by the algorithm)  
Gonna bitch and moan about it to Zizzy, maybe he can just remove the commit in question.

Old Upload  
 
600x600 00:00.18 GIF 77 kB
 
New Upload  
>>2976009t (merged)  
498x498 00:00.25 GIF 420 kB
 
New one is smaller. Slight speed difference.

Old Upload:  
 
1970x1022 PNG 813 kB
 
New Upload:  
>>3011518t (merged)  
1024x532 JPG 103 kB
 
The old upload is larger and a better file format.

@Anonymous #784E  
Taken care of

Old Upload:  
 
2889x3874 JPG 1.8 MB
 
New Upload:  
>>3046856t (merged)  
850x1140 JPG 226 kB
 
New Upload is much smaller.

@Anonymous #C335  
fixed

Old Upload:  
>>3046857t (merged)  
850x1002 JPG 209 kB
 
New Upload:  
 
3072x3622 JPG 1.77 MB
 
New Upload is much larger, came from the artist’s Twitter account.

@Anonymous #EC26  
Done.

Old Upload:  
 
2500x2078 PNG 574 kB
 
New Upload:  
>>3051832t (merged)  
414x344 JPG 43 kB
 
New Upload is freaking tiny.

@Anonymous #EC26  
Done.

>>1868404  
>>3057069 (merged)

@Dex Stewart  
fixed

Old Upload:  
 
2048x1122 JPG 205 kB
 
New Upload:  
>>3065248t (merged)  
2048x1122 JPG 205 kB
 
Same size, same file type.

@Anonymous #E2F8  
Done.

So there was a change upstream to how philomena processed the thumbnails for transparent GIFs back in September of 2020 but it does not apply retroactively to images that were posted before then. There was a few commits. this was one of them
 
Could you please regenerate the thumbnails for these images?
 
>>2757548  
>>2739519  
>>2726248  
>>2624617
 
(easier for me to post them here then to report them all and explain for each one)

@LinuxPony  
Went ahead and repaired them. Seems the jaggies were taken care of on the thumbnails but the ‘after effect’ type of visual glitch for a couple remains still. If you notice another batch, feel free to bring them up.
 
Also if you’d like to use the report function for batch images for any reason (such as this), simply make a single report for one of the images, and include in the report any additional image numbers, instead of making multiple reports. Makes it easier for us to handle that way anyway so we certainly don’t mind.
 
Or posting here works fine too. Either way.

@ArchiveAnon  
fair point. I will keep that in mind for next time