The recent policy changes to twitter's API have not gone unnoticed with developers of clients for the micro blogging service.
The writing is on the wall. The months, if not years of your hard work are slowly being subordinated by twitter's inherent need to control their environment to make money.
RSS pioneering developers Brent Simmons and Dave Winer both see the risk and the opportunity here, as do I
I've been hedging bets on my microbloging for years by maintaining a copy of my tweets in html and as an RSS feed by using free software. I also have a second feed that I don't feed into twitter, since I don't know what they do with my information, and I cocnsider that too risky
Use the 'source' element to enable in-app following of new feeds that users discover from other feeds they follow
Make use of OPML to maintain [portable] subscription lists
Use rssCloud to create a real-time experience
Implement the proposed RSS Re-Tweet standard
Have a look at the microblog namespace
The first Twitter client with RSS feed aggregation out of the gate will have a huge first mover advantage. Who wouldn't want to be able to have feeds [and even podcasts] inthe same UI as their tweets? I know I would.
Here's an example of what I would like to see in an app, running on my own server. See how This is also where I get my incoming twitter stream?