To preface a bit. I occasionally run my images through Sharp over CLI, and I am also a daily user of the Caesium desktop app. However, I haven’t explored the details of how Caesium is implemented.

The biggest difference is that MAZANOKE targets a different user group, essentilly those who would use online tools over installing applications, which is something you see more of these days. I wanted my family and friends to have a safe drop-in replacement for those shady websites. For those who want to use a “native app”, installing MAZANOKE as a PWA is also a great option.

In terms of core functionality, they are very similar and support the same output image formats. But at the end of the day, MAZANOKE is privacy-focused too, and have plans to add a simple image editor for obfuscation, cropping, and related features. You can also access MAZANOKE anywhere, whether it is self-hosted or on the official instance.

Fundamentally, MAZANOKE relies heavily on the device, and the browser’s Canvas API. This means that the speed and quality could slightly differ depending on which device/browser you use. I believe Caesium’s performance would be more consistent.

(I didn’t know where to put this, but my favorite feature is being able to paste to compress an image right away using MAZANOKE.)

Edit: typo

The unofficial unraid template was graciouslly provided by ctrlaltd1337ed, but I appreciate the sentiment.

About the name, It is an amalgamation of two words, I’ll leave the rest to your imagination!

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.

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.

If you get around to it, I’d love to know about it and add that as a feature.

The conversion option “Default” is meant to retain the file format when possible, but you can actively select the other options like jpg or webp if that fits your use case better.

Currently, only SVG to PNG is supported. SVGOMG is a great tool I’ve used many times as a user, but since it runs as a Node.js app, it would require server-side processing, unlike the local browser-based approach of this app.

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.

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.

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?

Haha, very interesting scenario, glad it worked out well!

At the moment, I haven’t integrate Youlag with FreshRSS as a full fledge extension, but once that is in place, it would be possible to store user preferences. While it requires time and effort, I believe it shouldn’t be too hard to implment this feature.

Addressing the subscribing part; I had similar requirements, so I started subscribing via FreshRSS while using a custom theme to give it a YouTube-like experience.

I shared the setup a few month ago here: https://lemmy.world/post/21381606

Edit: One of the benefits of using selfhosted RSS with a web interface is that it is platform agnostic.

Looking forward to it, feel free and share it once it’s ready, or if you need any feedback.

Hopefully this will spark some interest in that!

I have limited knowledge of what limitations extensions have at the moment, but considering FreshRSS is server side rendered, integrating DeArrow on a deeper level would be ideal (if possible). It would mean that the thumbnail and title you get when you load the page would immediately be the non-clickbait ones, and it would only need to run it once for each video (if cached).

I did however test DeArrow’s API and it was very straightforward. However, running it as a client-side script would essentially mean that every video would have to be checked and “DeArrowed” on the fly, and it would do that for every page refresh. That might not be very performant for you, nor DeArrow’s free API service.

In short, it should be possible, but not ideal. I’m personally interested in the idea as well, but I’m not sure if I’ll have time to tackle this.