Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
1–10 of 26 posts
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#2This looks nice, bookmarked!
Maybe expose some simple quality setting to the user?
As far as I can tell after glancing at the code, the only optimization that's done is re-encoding the image with quality set to 75, so a quality slider would be nice imho.
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#3IMHO these JPEG optimizers need to explain what optimization they actually do.
At the very least, it should mention if the optimization is lossless (by dropping metadata, optimizing Huffman table/progressive scan parameters etc.) or lossy: because they have very different use cases (sometimes you need the image to be pixel-wise identical).
Even better, if lossy, "how lossy" it is.
I'm aware it's using mozjpeg [1] which is pretty good (guetzli [2] is another good one for the interested); still, it comes with many settings and routines (both lossless and lossy) that can be configured.
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#4This looks nice, bookmarked! Maybe expose some simple quality setting to the user? As far as I can tell after glancing at the code, the only optimization that's done is re-encoding the image with quality set to 75, so a quality slider would be nice imho.
Thank you :)
My initial plan was to replicate the functionality of tools like tinyjpg, thus just offering users a simple interface with good defaults. But I already had in mind the lossy/lossless re-encoding functionality, as well as the quality slider, which I plan to add sometimes in the future
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#5Ahhhh the times we live in, when it specifically needs to be said that something like a image optimizer is privacy-aware. :(
Anyway - looks nice and something I'll use from time to time, thanks!
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#6Okay, privacy is achieved by never leaving one's browser. But how secure is that? One's browser is the home of an unknown number of trackers, as well as heavy interest and efforts in breaching tab boundaries. The browser has turned into something we need to completely start over, without Google or any of the FAANG crowds' participation.
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#7IMHO these JPEG optimizers need to explain what optimization they actually do. At the very least, it should mention if the optimization is lossless (by dropping metadata, optimizing Huffman table/progressive scan parameters etc.) or lossy: because they have very different use cases (sometimes you need the image to be pixel-wise identical). Even better, if lossy, "how lossy" it is. I'm aware it's using mozjpeg [1] whi…
Absolutely. Until now I had no idea what a JPEG optimizer is, and even the About page of jpeg.rocks said exactly nothing about what it does.
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#8IMHO these JPEG optimizers need to explain what optimization they actually do. At the very least, it should mention if the optimization is lossless (by dropping metadata, optimizing Huffman table/progressive scan parameters etc.) or lossy: because they have very different use cases (sometimes you need the image to be pixel-wise identical). Even better, if lossy, "how lossy" it is. I'm aware it's using mozjpeg [1] whi…
That's a very good point, thank you.
I could add some explanation on github and offer two kinds of optimization (lossless and lossy) and add a quality slider for the lossy one
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#9IMHO these JPEG optimizers need to explain what optimization they actually do. At the very least, it should mention if the optimization is lossless (by dropping metadata, optimizing Huffman table/progressive scan parameters etc.) or lossy: because they have very different use cases (sometimes you need the image to be pixel-wise identical). Even better, if lossy, "how lossy" it is. I'm aware it's using mozjpeg [1] whi…
That's a very good point, thank you. I could add some explanation on github and offer two kinds of optimization (lossless and lossy) and add a quality slider for the lossy one
is there a standard of proof these sites can provide about not sending data back to the servers? besides checking the network data, which it could delay to another visit or obfuscate easily
Re: Show HN: JPEG.rocks – Privacy-aware JPEG optimizer built with WebAssembly
#10Earlier quoted context omitted.
That's a very good point, thank you. I could add some explanation on github and offer two kinds of optimization (lossless and lossy) and add a quality slider for the lossy one
is there a standard of proof these sites can provide about not sending data back to the servers? besides checking the network data, which it could delay to another visit or obfuscate easily
I don't know, sorry.
I mean, you can be completely sure that the website works offline by unplugging the cable/turning off your wifi connection after it's completely loaded. But that's just a functional test, not something you can expect users to do during a normal browsing session