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.
    • lent9004@lemmy.worldOPEnglish
      1·
      15 days ago

      Even though this squoosh instance seems to be selfhosted, it has Google Analytics tracking (since Google made this app). MAZANOKE does not include any tracking nor require any internet connection at all if you install it as a PWA.

      Edit: Looked at the source code of the fork, and it is applying the same tracking ID (to the big G). As squoosh is apache2 licensed, from my understanding, they should be able to simply remove that off the fork?

  • markstos@lemmy.worldEnglish
    1·
    15 days ago

    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.

    • lent9004@lemmy.worldOPEnglish
      1·
      15 days ago

      Oh wow, thank you for taking the time creating the feature requests/issues. I just finishing replying to them.

      I’ll give the workflow another think and see if it fits within the project as a whole.

  • node815@lemmy.worldEnglish
    1·
    15 days ago

    Thanks for sharing this! I used it today to resize my Very large phone selfie I had to do for a profile image update at work and it did very nicely! Much faster for me to do that then load it in Gimp and scale it down since I was running late for work. : )