pngcrush... you had one job
-
@0xabad1dea It crushed up another png and added it to the top of yours like a crunchy topping mmm yum yum
@kestral @0xabad1dea biscoff png
-
@kestral @0xabad1dea biscoff png
@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
-
pngcrush... you had one job
@0xabad1dea upgrade to pngquant
-
pngcrush... you had one job
@0xabad1dea I can't believe I am suggesting this abomination but: this could be a scenario where webp is finally not worthless
-
(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?!)
@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?
-
@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
-
(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?!)
@0xabad1dea see also forcing mp4 and webp conversion when whatever was originally uploaded is objectively smaller.
-
(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?!)
@0xabad1dea the command line version says it will, but I'm not sure if it actually does
-
pngcrush... you had one job
And here I am, still using oxipng -
pngcrush... you had one job
@0xabad1dea we use optipng at work
-
R relay@relay.infosec.exchange shared this topic
