You must log in or register to comment.
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.
Is freshrss the best alternative at this point?
It always has been.
I use and like it.
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).
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 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…
You could want to have multiple clients in sync.
Also a web service could be fetching 24/7 and perform classification algorithms before serving to the client that will only connect a few times a day.
Try a good one such as Inoreader or NewsBlur, you’ll never look back
While not the same I use an rss-to-email service that hits the minimal sweet spot for me
I no longer find it fun to maintain public-facing anything
I think the kids would say: “Mood.”
For the record, it seems the project moved on, just without its previous maintainer, to github: https://github.com/tt-rss/tt-rss
The post is a bit low on details, but I strongly suspect this is a victim of AI scraping.
It really doesn’t seem like that’s the case. It doesn’t even makes much sense. What do tou think was being AI scrapped? The source code?
It makes a lot of sense. Both the git repos that they hosted and things like a RSS feed-reader are things that are the prime target for AI scrapers and the same time quite database query heavy on the backend so that the scraping really has a big impact on the costs of running these services.
And yes source-code is among what is the most targeted data to ingest by AI scrapers, mainly to train coding assistants but apparently it also helps LLMs to understand logic better.
First, source code is on github.
Second, RSS aggregators are self hostable, not a service provided by the dev. The dev would have not issues of a public instance of ttrss hosted by someone gets scrapped.
Third, RSS aggregators doesn’t really tend to be public facing. Due to their personal nature they don’t tend to be open. They are more account based.
Sorry, I really don’t see the case here.
What? They explicitly talk about shutting down their self-hosted infrastructure which includes two git services and other targets of AI scraping. Did you even read the post?
They are closing the whole project.
Specifically they say that they are tired of pushing fixes and that they don’t find excitement in maintaining the project. With zero mentions at all to being scrapped or having any kind of AI related issue.
I don’t know if you knew the project before seeing this post. I did, I was considering between this and freshrss and chose freshrss specifically because I knew that the end of ttrss was close (this was like 2 years ago). There were a lot of signs that the development was ending and the project was on route to be abandoned.
No, they are shutting down their publicly hosted infrastructure and say that their project is “finished” anyways, so it doesn’t matter that much as a justification. But the main point about the post is the public facing infrastructure and how they lost motivation to run it.
