For the last couple of months my interface with Twitter has been through an instance of TwitRSS.me running in a Docker container on my laptop. It has been working remarkably well… given that it hasn’t updated for months. Also it hadn’t kept up with the way that Twitter embedded image data in tweets, this in turn meant clicking on a lot of entries, and opening them in Twitter – which was what i was trying to avoid.
There are a couple of new / actively maintained projects that provide alternative methods of interacting with Twitter. Two of them, RSS-Bridge and Nitter, also provide RSS feeds of accounts / searches / hashtags.
Nitter is very cool. It uses the twitter api to return tweets, returning them in chronological order, in the form of website. For example, here is a random BBC stream, from which it’s possible to get an RSS feed. This is cool as it also converts all links in twitter into links into the instance of Nitter. There are people hosting Nitter instances, and it should be possible to host your own in Docker locally.
RSS-Bridge is more of the same, but instead of providing an alternative front-ends it provides plugable modules to scrape or generate RSS feeds directly. It has plugins for a bunch of sites that don’t provide RSS feeds, and while i’m not currently using any of them it’s cool that they are there.
Both Nitter and RSS-Bridge produce nice RSS feeds with options to include images, replies, user avatars, etc.
Currently i’m trying out RSS-Bridge and it seems to be working well. If Nitter continues to be worked on, and there are no issues (thinking TLS / certificate hassles) then perhaps that is the future answer. The downside of RSS-Bridge is that it’s written in PHP which always gives me the heebie-jeebies. Nitter, on the other hand, is written in something that feels entirely new called Nim… which looks cool, but it likely niche.
Oh, and the Nitter project has spawned browser plugins that redirect Twitter into Nitter. I’m using ‘twitter-to-nitter-redirect‘. Nice!