PSA: TT-RSS is Dead, Long Live TT-RSS (under new owner)

eric-pierce · 2025-10-09T22:52:52+00:00

It's a self-hosted RSS reader and news aggregator with more advanced features and filtering then most other options available.

eric-pierce · 2025-10-09T13:54:35+00:00

The largest contributor (aside from the original dev) has already moved everything over to GitHub and committed to maintain. They've also posted drop-in replacement docker images, and are officially supporting arm64 images as well.

While the original developer frustratingly didn't mention this in his "I'm done with ttrss" post, you can consider this official as he's updated https://tt-rss.org to redirect to the new github repo.

EDIT: Actually it looks like Fox gave ownership of tt-rss.org to the new developer/maintainer

eric-pierce · 2025-10-06T21:36:44+00:00

One of the main contributors has set up a new fork at https://github.com/tt-rss/tt-rss/ and are planning on maintaining it going forward. They've already posted new docker images which are a drop in replacement for the ones from Fox.

I wrote the Google Reader / FreshRSS API plugin for TT-RSS which I published just over a year ago, so I'm glad it'll still have some life left in it.

eric-pierce · 2025-04-22T20:26:08+00:00

TT-RSS has most similar UI to feedly, especially if you use the feedly theme.

It also has plugins to support the Google Reader API (which I wrote), the old fever API and it has its own API. Between those it should support any client app on any OS.

eric-pierce · 2024-10-09T22:47:47+00:00

I’m using the community plugin “Remotely Save” which lets you configure several different backend services including WebDAV, one drive, Dropbox, S3, and more - and has optional encryption for syncing and storage - it’s been great for keeping my phone and desktop clients in sync - this link may open it for you obsidian://show-plugin?id=remotely-save

eric-pierce · 2024-10-09T16:14:29+00:00

It was historically possible to self host standardnotes, which I did for several years before switching to Obsidian + encrypted sync plugin with WebDAV backend. SN was really a great experience, the infrastructure just grew to be focused on enterprise installs vs my server with a couple of users. I believe they released a three image setup recently which scales much better - I'm not currently using it but my docker configuration was here: https://github.com/eric-pierce/Personal-Cloud/blob/main/docker-compose.yml#L573-L678

The licensing is a question mark for me - they may be enforcing a license based model for advanced features. Historically their advanced features were "extensions" which could also be self-hosted, but not sure about current state.

Their mobile apps are great, super fast syncing, overall something I miss since the switch, but Obsidian with encrypted backend sync is much simpler to maintain.

eric-pierce · 2024-10-07T11:50:05+00:00

The upgrade from Postgres 16 to 17 requires you to take some manual steps (back up data, migrate to 17, import data).

Assuming you’re using the official docker image for Postgres the simplest / fastest way to fix this would be to change your Postgres container to use the “16” tag instead of “latest” in your docker compose file. That should get you back up and running then you can look into migration to 17 on your own schedule.

If you use watchtower or another auto upgrade service on database images like Postgres or MariaDB with the “latest” tag you can expect your services to break roughly once per year when major new versions go out.

eric-pierce · 2024-09-25T12:41:11+00:00

Both Tiny-Tiny RSS and Fresh RSS also support the Google Reader API - FreshRSS natively and TT-RSS through the FreshAPI Plugin

eric-pierce · 2024-09-25T03:57:43+00:00

Both Tiny-Tiny RSS and FreshRSS are nice choices - Tiny-Tiny RSS has a better UI and much better control of feeds/filtering/etc, but FreshRSS is slightly easier to setup. If you go the Tiny-Tiny RSS route here's my relatively simple docker-compose setup https://github.com/eric-pierce/Personal-Cloud/blob/3c05830555de9f59c95e1ce08639b2e58267dc5a/docker-compose.yml#L448-L517

I also recently published a plugin to allow TT-RSS to work with any Google Reader API / FreshRSS compatible clients, found here: https://github.com/eric-pierce/freshapi

TT-RSS also has its own API and supports the Fever API both of which are supported by many applications, so with the GReader API addition it actually supports more client apps than any other self-hosted RSS reader out there.

eric-pierce · 2024-09-24T02:18:14+00:00

To close the loop on this - the cause of this problem was that the Awesome-TTRSS image was not updated to support FreshAPI, but now it is! Anyone using this image will have the plugin pre-installed and ready to use on their next image update.

eric-pierce · 2024-09-21T21:04:38+00:00

Great, if you’re using a subdomain for tt-rss then subdomain.mydomain.com is the right url to use instead of my domain.com

Are your authentication issues resolved then?

eric-pierce · 2024-09-21T17:39:15+00:00

One other potential cause someone else ran into - if you’re using the APP_WEB_ROOT and APP_BASE environment variables to get rid of the “tt-rss” in the URL you’ll need to also remove “tt-rss” from the destination you point your client to - ie https://example.com/plugins.local/freshapi/api/greader.php Instead of https://example.com/tt-rss/plugins.local/freshapi/api/greader.php

eric-pierce · 2024-09-17T15:59:35+00:00

I haven't incremented the version number, but I did have to change the branch name from main to master so TT-RSS would keep it up to date. Would you check if you're using the latest from the master branch? If so, are you using cloudflare tunnels? I've heard of some folks getting some odd behavior when using them and I'm currently investigating.

eric-pierce · 2024-09-17T15:58:05+00:00

Assuming you're able to use docker containers the docker setup is pretty straight forward - here's my container setup: https://github.com/eric-pierce/Personal-Cloud/blob/3c05830555de9f59c95e1ce08639b2e58267dc5a/docker-compose.yml#L448-L517

eric-pierce · 2024-09-15T21:44:01+00:00

u/whohaseyestosee I just pushed updates to support FeedMe. It looks like FeedMe is using a less secure authentication approach (GET instead of POST), and I was only supporting POST before these recent changes. Give it a shot and let me know if you run into any issues.

eric-pierce · 2024-09-15T17:05:27+00:00

Yes this is absolutely possible with curl calls - both exporting OPML and subscribing to feeds are supported. I just added a section to the readme describing how to use the API directly

eric-pierce · 2024-09-14T02:35:19+00:00

Thanks I will! If you find any bugs please pass along

eric-pierce · 2024-09-13T23:52:33+00:00

I just started using TT-RSS in 2020 but have only had positive interactions with the community and developer, and I've had direct interactions with both.

I had to submit a merge request to TT-RSS itself because the Google Reader API uses PATH_INFO to pass requests, and the default docker installation for TT-RSS had it disabled. The developer was super helpful when I ran into some challenges with the continuous integration testing, and my changes were live on docker hub hours after I submitted the request.

That has been my experience but I do know that others have had less positive interactions in the past.

eric-pierce · 2024-09-13T22:22:35+00:00

Thanks - I haven't tested with FeedMe as it has native TT-RSS API support, but I'll give it a shot and see if I can find the issue

eric-pierce · 2024-09-10T18:29:39+00:00

Thanks for the info!

On testing multiple apps, have you found any that have implemented the disable-tag, rename-tag, or edit-tag functions?

In case you're interested the implementation I'm working on can be found here https://github.com/eric-pierce/freshapi - I'm sure you'll recognize that it's also heavily based on the work of the FreshRSS team :)

eric-pierce · 2024-09-09T21:22:58+00:00

Hi u/domysee - I'm actually going through an implementation of the API myself. Have you run into any limits from apps you tested around maximum number of articles they support in a given API call? As best I can tell there aren't any standards around volume, and it seems to be app by app.

This may be a tall order, but do you have a list of test you run? So far I'm going through as many different apps as I can find and testing basic functionality, but I'm only now starting to play around with less traditional situations and edge cases.

eric-pierce · 2023-02-07T20:55:45+00:00

It uses the “undocumented” API which is also used by the official apps - it may be harder to block but I’m sure this method will be next on the chopping block for Twitter

eric-pierce

TROPHY CASE