TT-RSS is abandoning Android development in https://github.com/tt-rss/tt-rss/discussions/29. Compounding the opening-article functionality being slightly broken in Windows at the moment, it might be time to look at a new reader.
TT-RSS is abandoning Android development in https://github.com/tt-rss/tt-rss/discussions/29. Compounding the opening-article functionality being slightly broken in Windows at the moment, it might be time to look at a new reader.
[Relevant old article about opening-article button](https://web.archive.org/web/20191122162451/https://srv.tt-rss.org/oldforum/viewtopic.php?t=2984)
Candidates:
* https://freshrss.github.io/FreshRSS/en/
* https://github.com/feedbin/feedbin
* http://readerself.com
* ... more to evaluate from
* feedbin is nonviable, as it requires extensive resources to operate. See https://github.com/feedbin/feedbin/blob/main/.env.example
* FreshRSS does not support LDAP per https://github.com/FreshRSS/FreshRSS/issues/1053.
Readerself has been forked to https://github.com/stephanediondev/feed but seems the most viable.
Just an option, if no one but me is using this, then perhaps creating an IRC #ticker channel would be an alternative, subscribing through the RSS module of bitbot into channels and removing the need for another tool.
Just an option, if no one but me is using this, then perhaps creating an IRC #ticker channel would be an alternative, subscribing through the RSS module of bitbot into channels and removing the need for another tool.
The feed project depends on MySQL specifically, with a few more requirements that I don't want to support at the moment.
I have restored TT-RSS & removed the problematic integrations. It's no longer connected to LDAP, which means it will act like an API token instead. Considering a compromise of a user's account is very low-risk (loss of feed subscriptions, etc., but minimal PII), this will be an acceptable compromise for the functionality.
The `feed` project depends on MySQL specifically, with a few more requirements that I don't want to support at the moment.
I have restored TT-RSS & removed the problematic integrations. It's no longer connected to LDAP, which means it will act like an API token instead. Considering a compromise of a user's account is very low-risk (loss of feed subscriptions, etc., but minimal PII), this will be an acceptable compromise for the functionality.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
TT-RSS is abandoning Android development in https://github.com/tt-rss/tt-rss/discussions/29. Compounding the opening-article functionality being slightly broken in Windows at the moment, it might be time to look at a new reader.
Relevant old article about opening-article button
Candidates:
Readerself has been forked to https://github.com/stephanediondev/feed but seems the most viable.
Just an option, if no one but me is using this, then perhaps creating an IRC #ticker channel would be an alternative, subscribing through the RSS module of bitbot into channels and removing the need for another tool.
Attempting that fails on reading atom feeds with
f.rss add https://api.axios.com/feed/, which is unfortunate. We will proceed withfeed.The
feedproject depends on MySQL specifically, with a few more requirements that I don't want to support at the moment.I have restored TT-RSS & removed the problematic integrations. It's no longer connected to LDAP, which means it will act like an API token instead. Considering a compromise of a user's account is very low-risk (loss of feed subscriptions, etc., but minimal PII), this will be an acceptable compromise for the functionality.