I'm glad to hear it's being used frequently! I've heard a similar, but not exactly the same use case, so I recommend submitting a feature request on GitHub. That way, I can review it later to assess if the feature could be included when I plan ahead for new releases.
lent9004
If I understand it correctly, then yes, that's the case! I've utitlized several libraries such as "Browser Image Compression", "heic-to", and more, to wrap it in a web interface.
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?
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:
This app is designed to compress smaller batches of images, aimed at casual users who need to compress and convert a few images at a time.
I created it primarily for friends and family who are less tech-savvy, to help them compress and convert images in a simple, safe, and private way.
As a Lemmy user myself, I totally get the sentiment. GitHub isn’t ideal, and I had also considered Codeberg in the past (not for this project, but way back for others). Unfortunately, the simple reason is that the community is already on there, which makes getting contributions and engagement much easier. Managing and tracking issues across two platforms would be quite (mentally) taxing, which is on top of the effort already going into developing the app.