> For me, RSS is by far (still) the best way to access web content.
Same for me. I'm using Feedly atm. But the majority of users don't use RSS and they never did. Perhaps that is never going change.
I use a native application (QuiteRSS) as my reader but for twitter I use a modified version of the twitter_search_to_rss.pl and twitter_user_to_rss.pl + TwitRSS.pm from TwitRSS.me (https://github.com/ciderpunx/twitrssme/tree/master/fcgi). The resulting xml files are saved out into my ~/www/RSS/ directory and that URL path is used in my various readers.
+1 for everything you wrote. I'm still using quiterss and heavily relying on the filter actions on a daily basis.
My only experience with an online self hosted client was tiny tiny, which I didn't like. Thanks for sharing the freshrss alternative, I guess I'll give it a try!
For me, RSS is by far (still) the best way to access web content.
I've tried some self hosted RSS readers over the years but I've stayed with FreshRSS[1] for the last year. It has been a marvelous experience. Zero trouble, zero administrative burden. Self-hosted bliss. Best of all is the fact that it uses a flat file DB so it can easily be backed up, moved around and migrated. Can not recommend it enough. Also, it's PHP, so works on any cheap shared hosting. That's how I use it.
One of the best things about it is escaping the algorithmically curated feeds.
Every site and service that I wish to follow has an RSS feed, except for Twitter. I use RSS-Bridge[2] (self hosted too) to follow users. RSS-Bridge[2] will give you feeds for just about every service you can think of.
If you don't find a feed for a site, sometimes you just have to dig a little. You learn at which URIs the most commons CMSes presents their Atom/RSS feeds (hello /feed/).
[1] https://freshrss.org/
[2] https://github.com/RSS-Bridge/rss-bridge