I have copied the latest git revision
c67b943aa894b90103c4752ac430958886b996b2from https://gitlab.tt-rss.org/tt-rss/tt-rss to my gitea instance which is mirrored to https://gitlab.com/nodiscc/tt-rss and https://github.com/nodiscc/tt-rss.I don’t intend to make changes or bugfixes (it’s working fine), but I will try to keep it compatible with the PHP version in Debian stable, since I’ve been using it for years and would really like to keep doing so.
The loss of Google Reader is basically what taught me not to get too attached to services I can’t host myself. I’m hosting an older version of TT-RSS (due to migration issues to newer versions), and will continue with that until it no longer works for me, and then I will probably move on to CommaFeed. I’ve already tested all the commonly self hosted RSS readers out there, and that’s the one that fits my needs best, other than TT-RSS.
Is freshrss the best alternative at this point?
Yeah, it’s great, fast, works with lots of local clients and has lots of plug ins for whatever esoteric need you might have. I can fly through the days articles very quickly with a handful of key presses.
I like FreshRSS - I also have some readers that connect to my instance, like FluentReader that provides a better full article view, but I mostly use FreshRSS directly these days.
Looks like it supports a wide range of readers with two different API .
FreshRSS supports access from mobile / native apps for Linux, Android, iOS, Windows and macOS, via two distinct APIs: Google Reader API (best), and Fever API (limited features, less efficient, less safe).
For the record, it seems the project moved on, just without its previous maintainer, to github: https://github.com/tt-rss/tt-rss
i don’t get why people use web services for rss, it can be done completely clientside, that’s… kind of the whole point of rss…
To keep it synchronized between devices
The gas chamber guys? Good riddance







