I’m glad to have some competition for the Frost Oven Squoosh, which is being lightly maintained. I opened some issues in the Mazanoke issue tracker for some features to consider.

One feature I started on for that project but got stuck on was implementing a STDIN / STDOUT CLI workflow.

https://github.com/frostoven/Squoosh-with-CLI/issues/10

As I said there, the goal was a workflow where I take a screenshot, annotate it, optimize it, copy it and paste it into my blog… without creating any intermediate temp files.

At least on Linux, all the the steps of the pipeline are solved, except for a CLI image compressor that could accept an image STDIN and produce a compressed image on STDOUT.

Sounds like an oversight. Consider filing a bug with them.

https://github.com/frostoven/Squoosh-with-CLI

Nice. I use Squoosh for this, which is also free and runs in the browser.

https://squoosh.frostoven.com/

Https give you encryption in transit. The files you view will be accesible to the host.

Same idea with email.

Not true that most incoming email will plaintext. It’s the opposite:

“Most of today’s email services, including Gmail, employ transport layer security (TLS) to protect emails in transit”

Ref: https://umatechnology.org/gmails-new-encryption-can-make-email-safer-heres-why-you-should-use-it/

nobody should have to deal with kubernetes when it comes to vehicle maintenance.

Tried it a couple times. Went back to the CLI.

If you know the CLI or are willing to learn, the GUI is yet-another layer for bugs to exist.