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.
EXIF data is removed by default, at the moment, there’s no way to keep those data. I personally see that more as a feature than a bug though. The primary reason why there is no option to keep EXIF data is to maintain feature parity across different image formats.
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!
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.
Ah I see, I’m still on webcord to be honest (not for any particular specific reason).
Probably could be used with betterdiscord that supports js plugins.
Yes indeed, the library I used “Browser Image Compression” is quite easy to work with. I did this as a weekend project + a few more days to prepare for open sourcing.
This has analytics tracking and is made by Google though. I intentionally wanted to stray away from that.
Edit: typo
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.
Sorry about that, I’ve included the fix in the latest release, and instructions on how to bypass the loading screen in the release notes:
https://github.com/civilblur/youlag/releases/tag/v3.0.4
Here in an excerpt from the release note:
In case FreshRSS got stuck in a loading state with the
v3.0.2release:You can manually bypass the loading state by opening the inspect mode on your browser. Within the “Elements” tab, locate the
bodyelement and add the CSS classyoulag-loaded.Example:
- From
<body class="normal">- To
<body class="normal youlag-loaded">.The adjustment above will exit the loading state, allowing you to interact with the content and access the extension page.
For your convenience, below is the url path to the “User CSS” extension page:
https://yourfreshrssdomain.com/i/?c=extension&a=configure&e=User%2BCSSHead to this page and replace the old CSS with the one provided in this release.
Edit: Fixed typo on CSS class name
Since I don’t use a TV myself, I have not looked into this scenario unfortunately.
No worries! This setup ended up working better than I thought, and I’ve been using it as my primary way of interfacing with youtube.
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.
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.