Earlier this month, entrepreneur and blogger Jesse Stay noticed that
Facebook and Twitter completely removed RSS support from their sites. After many protests in the technical community, Facebook changed its mind and again added links to RSS to Facebook pages. Twitter didn’t respond.
But now one developer has created a tool that uses the Twitter API to create RSS feeds. A project code called “Twitter API 2 RSS” is available on GitHub
here .
Twitter killed RSS
According to Stey, Twitter has gradually removed RSS support for some time. Last year, Twitter developer Isaac Hepworth told Steu that links to RSS feeds were removed only from profile pages, and the links in the metadata will remain. Hepworth said that their temporary removal was “accidental” and they will be returned soon.
')
But, as Stay writes, the links were never returned, and he could not find any traces of RSS in the HTML source. This led him to conclude that Twitter really killed all the technology support. Twitter’s help
confirms this: “Twitter no longer directly supports RSS feeds.”
Stay noted that developers can access RSS via the Twitter API, which can be the latest tool for getting an RSS feed from the Twitter site outside of third-party services.
Twitter API 2 RSS
Now another developer, Sean McCollom, did just that. Twitter API 2 RSS, available as a code fragment (gist), is ready for testing. The code was written for personal use when he wanted to create his own RSS feeds for Twitter profiles, better quality and more functional.
When McCollom found out that Twitter was removing RSS support, he realized that his code could be rewritten for use by others. The only problem now is that he does not know how to overcome the API limit for 150 requests per hour from a single IP address. He is looking for ideas to help solve this.
Now tech-savvy users can run Twitter API 2 RSS code and subscribe to feeds in Google Reader or any other RSS reader. For end users, the code is not yet available as a service. Details on how to use the code are available
here on the McCollam blog.
Here’s what it looks like in action: