This wasn't the only blow to RSS usage, a lesser blow was struck when Twitter announced permanently retiring the Twitter API v1.0 which allowed Atom and RSS feeds output. The current Twitter API 1.1 only allows JSON format and requires authentication to access. This took effect, June 12.
For most people, this did not make a difference. But for me it was a blow, because I was pairing RSS output from Twitter feeds with IFTTT to filter and alert me only if a certain keyword appeared in the feed.
To backtrack a little, I've written many times on this blog about techniques on how to proactively scan for tweets about your library.
There are 3 ways to figure out if a tweet is about your library even though the person tweeting does not @mention your library.
1. If the tweet contains the keyword (e.g NUS Library)
2. If the tweet contains keyword (e.g. Library) and is within say 1 km of your library
3. If the tweet contains keyword (e.g. Library) and is from people you can identify as your user
I soon realised the basic options just scratches the surface, Zapier is apparently capable of filtering on pretty much every piece of metadata available from a Tweet, and it is a very long and complicated list.
This is a somewhat geeky post, though I have been using such techniques since 2010 and have found them invaluable in keeping on top of news I am interested in.