Feature Request: Better handling of RSS feeds
burrhole opened this issue · comments
Fist off, apologies if this is a bit outside of scope for this project.
As it currently functions, pointing an RSS reader to twiiit.com/(user)/rss will find an instance and download the RSS feed for a given profile from that instance, and then on the next request may pull the feed from a separate instance. This causes a bit of an issue with RSS readers such as tt-rss / liferea, where every time the feed is refreshed, a completely new, duplicate feed is pulled in to the reader, causing many duplicate "new" entries for the same feed where one would expect it to only pull in new tweets.
I'm not exactly sure what a good fix for this would look like; possibly have an "internal" rss feed/nitter instance that then proxies to posts on other nitter instances?
This is an illustration of the current behavior I'm referring to for https://twiiit.com/SoloKeysSec/rss in liferea: https://imgur.com/0XD6DCp
Thank you for your work and your time!
@burrhole understood. At the moment the proxy can take a lot of traffic because it simply returns HTTP redirects. If it is modified to actually proxy the requests it would be more like Nitter itself and would start to suffer from the same outages. Not sure how to solve the problem you are facing without introducing outage risk.
can nitter make a guid for items based on canonical twitter url? that may help with most aggregators, and twiiit stays stateless
thanks for trying that out
@hdhoang if you want to implement this you should submit a PR to Nitter itself.
For anyone else who happens upon here, there's an issue for this concept with nitter already zedeus/nitter#447