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.
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
True, the UI is optimized a bit too much :)
By looking very carefully at some test image I see that it is not lossless, there are more compression artifacts. Well, lossless would have been a miracle, it reduced the size of my photo from nearly 600 KB to just a bit over 180 KB.
Anyway - looks nice and something I'll use from time to time, thanks!
I see what irks you, calling it "privacy-aware" and not something more technical like "installation-free client side", but it can be a pretty cool approach to many rarely-encountered problems.
I'm not much into "JPEG optimization" (whatever that is, I just bite the bullet and wait those ten seconds GIMP takes for startup on my otherwise comically fast Ryzen 9 Windows box whenever I feel like tweaking JPEG compression), but https://hexed.it/ has been a friend for many years: i rarely need a hex editor, but even if I happen to run into a "guess it's time for a hex editor!"-situation twice on the same OS installation (unlikely), the last time would be so long ago that I would have forgotten what I installed. hexed.it is a godsend. Jpeg optimziation is perhaps not quite the same level of problem/solution fit, but it doesn't have to be.
That's very roughly what Gemini is going for. Related reading:
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
Yesterday, I released https://goart.netlify.app It's an experiment at using WASM-compiled Go code to create complex generative art drawings in the browser. Sounds cool, but I have had quite a few unexpected issues while building it. Especially, the part about having to use Web Workers to do the communication to and from the WASM instance.
