pngcrush... you had one job

[0xabad1dea@infosec.exchange]

(I understand that the algorithm may find there's nothing left to crush, but in that case, surely it should return the original file and not a worse one?!)

[wyatt_h_knott@vermont.masto.host]

@0xabad1dea It had to add some notes: "I tried to crush this but it dodn't work"

[jackeric@beige.party]

@kestral @0xabad1dea biscoff png

[kestral@masto.hackers.town]

@jackeric @0xabad1dea my cupboard is so full of peanutbutter.png hang on let me run it through the cruncher wait it was already crunchy now it's getting bigger AHHH HELP MY KITCHEN

[meluzzy@woof.tech]

@0xabad1dea upgrade to pngquant

[elrohir@mastodon.gal]

@0xabad1dea I can't believe I am suggesting this abomination but: this could be a scenario where webp is finally not worthless

[lewisworkshop@mastodon.online]

@0xabad1dea what happens if you try to re-crush a pre-crushed png file? Does it keep increasing, or just remain at the same slightly enlarged size?

[piggo@piggo.space]

@kestral @jackeric @0xabad1dea epic infinite pb exploit

[kawa@mas.to]

@0xabad1dea see also forcing mp4 and webp conversion when whatever was originally uploaded is objectively smaller.

[irina@critter.cafe]

@0xabad1dea the command line version says it will, but I'm not sure if it actually does

[csolisr@hub.azkware.net]

And here I am, still using oxipng

[ask@infosec.exchange]

@0xabad1dea we use optipng at work