[ b / kemono / coomer ]

/kemono/ - kemono.party

Kemono Development and Discussion
Name
Email
Subject
Comment
Verification
File
Password (For file deletion.)

File: 1748039335968.png (394.27 KB, 1349x798, Screenshot_4.png)

 No.54343

Is there any fix to getting the images from this guy? it's the only one whose links seem to be bizarrely just corrupted no matter what.

 No.54505

Bumping again

 No.54511

Admin said a few weeks ago he looked at this and the images as originally uploaded are just a broken mess. He's mostly amazed that Patreon somehow manages to display them correctly.

My guess would be you need a custom tool to fix them up.

 No.54512

So there is no way to fix them then? damn unfortunate as heck.

 No.54587

File: 1748410033989.jpg (5.88 KB, 257x127, photo_2025-05-28_08-11-06.jpg)

More than half of the contents of any of his broken files is what's looking like a zip bomb packed into zip-compressed description field. When we get to the image data stream, there is whatever is on the screenshot. It's quite literally designed to crash one half of the png parsers and halt the other before the actual data stream comes.

My current hypothesis is that these are some maliciously crafted files designed to work with and only with a library Patreon uses to generate previews.

Also, he tells us to SUCK. (recurrent thing among all the files i tried)

 No.54698

will someone fresh reimporting fix this

 No.54757

It's fixable, personally I just used Notepad++ with a hex editor plugin, but any text editor with a hex editor should work, just delete all the chunks before the IHDR chunk if there are some, don't delete the PNG header though, those between the IHDR chunk and the first IDAT chunk, note that the chunk actually starts 4 characters before the chunk name, those between the 1st and 2nd IDAT chunks, and then change the part of the 2nd IDAT chunk that indicates the chunk length with the Hex editor, which is the previously mentioned 4 character before the chunk name, after this 2nd IDAT chunk there is only the IEND chunk, from that you can get the length of the IDAT chunk and then convert it to hex, can be done with the Windows calculator in programmer mode, and use the hex editor to actually write the hex length on the length part of the IDAT chunk.
There's no need to keep reimport this guy's gallery every 2 days, every image seems to be recoverable from what I tested, though he somewhat changes what he does time to time, like, older imports with <8 MB files are recoverable from using the compress to die corrupted png tool, and some even older images actually open on the standard Windows image software, but not on browser.

 No.54789

>>54757
Genius, thanks. The whole process got old fast so I just made a pythons script to automate it. Only thing is the blaze drummer set came out with some weird inverted colors, but everything else I tried seemed fine.

 No.54807

>>54757
Hi! It's >>54587 and in my investigation I went literally through every single one of your steps but didn't get a result so I didn't post a guide. I found my mistake. I deemed first IDAT gibberish and deleted it too. It contains literally single byte of information, but this byte was the reason my pics weren't working. Thank you! Was I the one to bait you into this madness?

Radioneet is a weirdo. Hey, shitass, if you are reading this, try harder.

 No.54811

>>54789
You wouldn't be willing to share the script would you?

 No.54815

>>54811
https://pastebin.com/cTz3irGH

Accepts directory as parameter. So save all broken files in a folder and provide that folder name when running it, it will create a new file x_repaired.png for each

 No.54825

>>54807

if it's harder and impossible to reverse

what would you all do?

 No.54829

Hey I'm literally illiterate when it comes to tech, could you please kindly tell me how i am supposed to use the code in the pastebin? My greatest thanks.

 No.54831

>>54829
Assuming you have python installed and on your path (if not, install python, plenty of guides for that already) make a folder. Put all the broken images in it. Download the script, save it in the same folder as the .py file.

Either shift right click in the folder and open a cmd/powershell window or type cmd in the file explorer address bar with the folder open to open a terminal in that directory. By this I mean the window that appears should read something like C:\folder1\brokenImagesFolder>

Type

python repair_pngs.py .

and press enter. This will only work if the cmd is opened in the same folder as the images and the script.


If this isn't enough just paste the .py file in chatgpt and ask "How do I run this"

 No.54832

>>54831
>save it in the same folder as the .py file
same folder as the images*

 No.54834

Oh my it worked, Thank you so much kind sir

 No.54848

I had to add the folder path after python repair_pngs.py to get it to work despite powershell being pointed at the directory but it worked great after that
there's still some that have weird inverted colors that I don't enough about image editing to fix though

 No.55003

holy thank you too

 No.55109

What the hell?

 No.55187

Sorry bumping

 No.55286

another burying post to bury cp ignore these please thank you and fuck pedos

 No.55416

boats

 No.55511

Burying bump



[Return][Go to top] [Catalog] [Post a Reply]
Delete Post [ ]
[ b / kemono / coomer ]