Thank you for the support that I've received during the launch of MAZANOKE—a self-hosted local image optimizer that runs in your browser! It can run offline and is installable as a web app too.
This week, I've been addressing the feature that has been a bottleneck for the usability of an image optimizer, namely: batch upload and download.
Project page: https://github.com/civilblur/mazanoke
Highlights v1.0.1 (view release note)
- Upload multiple files simultaneously
- Images are processed one at a time to prevent excessive browser resource usage.
- Download all optimized images as a zip file.
- Files over 1GB are split into multiple zip files.
- Large downloads may take time, depending on hardware and browser.
- Option to clear optimized images from the "Images" section.
- Convert GIF and SVG to PNG.
- GIF-to-GIF optimization is not supported.
- SVG optimization is not planned.
That's a valid question! The app is intended for less tech-savvy people, as such, the terminologies used are to accommodate those users. "Upload" would rather be "Import", while "Download" would be "Export".
I've shared the use case in a previous Lemmy post:
While I appreciate the sentiment, I do think that despite being well-intentioned this could just contribute to today's digital illiteracy. It also downplays the app's privacy, I almost dismissed it as a cloud service the moment I saw that.
Perhaps you could use "open" and "save", which is widely understood and probably more appropriate.
That said, the app is a great initiative, and I'll certainly give it a look once I get in front of a computer, and probably recommend it to students.
Just because its run locally, doesnt mean it still isnt a web server. The software could run anywhere and be accessed over the network. The image optimization happens at the server, so download and upload are more accurate.
Wait, the optimization does not leave the browser. There isn't any need for a web server.
If this can be used as an offline PWA, it doesn't even need to be 'self-hosted', except for keeping it up to date.
Edited: removed reference to "device", to avoid confusion.
Yeah, you're totally right.
And then it mentions that you can just open the index.html directly, which means it uses clientside javascript or wasm and runs on the browser. You are correct!
On the topic of word choice, you might be right. Save or open might be better.
Fair enough!