4 ms·
I've been self-hosting miniflux [0] for a couple years. Rock solid performance, deployment is easy, upgrades are small but meaningful, and doesn't use anything
by gen220 4y ago
I've been self-hosting miniflux [0] for a couple years. Rock solid performance, deployment is easy, upgrades are small but meaningful, and doesn't use anything exotic in the tech stack (mainly Go, some vanilla JS, persists data in PostgreSQL).
I mainly browse on my laptop, but it's pretty decent on mobile.
[0]: https://github.com/miniflux/v2 https://github.com/miniflux/v2
- jhot 4y agoAlso a happy miniflux holster. On Android I use Miniflutt [0] as a client, mainly for the mark as read on scroll feature. Any fever API compatible app will work, though. 0 https://github.com/DocMarty84/miniflutt https://github.com/DocMarty84/miniflutt
- ekovarski 4y agoSelf hosted miniflux as well but kept running into 403/429 errors when using reddit rss feeds, went back to freshrss. The biggest issue is that once you invest in a reader, your data aside from the feed opml, is stuck in that reader so your favourites, labels, and content can't migrate.
- gen220 4y agoInteresting feedback on reddit RSS feeds. I'm only subscribed to a single reddit feed, but it's totally possible that miniflux was spamming requests and that led to a rate limit. It isn't super customizable in terms of how frequently it pings to see if new items have been added, it's a fair criticism. I'd gently push back on the migration issue. As long as you're going the self-hosted route, all of this data exists on your machine. A tool for painless migration from X reader to Y reader might not exist, but at least it's feasible to build. If your data is in some hosted solution, you're at the mercy of the provider to implement data exports.