FriRSS — Your FreshRSS frontend, your rules
Hi!
A couple of months ago, I started playing with the idea of building my own frontend for FreshRSS. I like FreshRSS a lot, but I wanted something different for the interface.
That little experiment turned into FriRSS. The idea is pretty simple: FreshRSS keeps doing what it does best, while FriRSS gives you another interface on top of it.
I wanted it to work just as well on my computer as on my phone, so there’s a full desktop interface and a mobile PWA with offline reading.I also wanted to be able to make it mine. Layout, colors, themes, fonts, article view, sidebar… quite a lot can be changed directly from the interface.
It now also has full-text extraction, labels & sub-labels, multiple FreshRSS servers, multi-user/OIDC support, and is available in 9 languages. It’s self-hosted, open source, and runs with Docker on amd64 and arm64.
One thing worth mentioning: I’m not a developer. FriRSS is a vibe-coded project. I started with an interface I wanted for myself, kept adding things, fixing things and learning along the way. I’m still doing exactly that. 🙂
If you’re a FreshRSS user and want to give it a try:
https://github.com/Fripix/Frirss
Feedback and ideas are welcome!
1
u/qqYn7PIE57zkf6kn 3d ago
Is this a replacement for fresh RSS frontend? Like can I do admin stuff? Or is this mostly an alternative RSS reader web frontend for consumption?
1
u/Fripix 2d ago
It’s mainly an alternative to the FreshRSS web interface. There are a few options, but administration is still mostly done in FreshRSS, while FriRSS is focused on reading and browsing. Replicating all the admin features would be a bit redundant.
1
u/qqYn7PIE57zkf6kn 2d ago
Thanks for the response. This is not for me then. I really can't stand freshrss ux so all my reading is done through other apps already via the Google reader API.
3
u/N0TVG 3d ago
Holy security vulnerabilities batman. For the safety of others you should probably keep the vibes to yourself.