When we built twitter we had also hacked up various forms of RSS readers. At the time nobody on the team really thought they were going after rss, news reading, or discovery. But it turns out that trying to solve that problem in parallel to the status update system. Twitter was for a long time very much built upon the RSS stack of technologies. It was a semi-open platform which worked better, unfortunately, than the fully open world of RSS & ATOM.
In the end, now 8 years later, it's clear that twitter DID kill rss as a dominate category of apps & services. We went from being overwhelmed by unread counts on the 'readers' to having flow. I'm not sure it's better, but it did solve the problem of feeling like you needed to keep up.
I think there's still more interesting work to be done in this space. Open social networks (that's what blogs are folks) plus users being able to control visibility of posts and frequency and open api's could do something which could unseat twitter/facebooks.
They are totally dissonant channels that have some overlap. Expecting Twitter to replace controlled curation is a recipe for noise. The value in RSS is some process or person is curating a defined set of data - the reliability of even organizational Twitter accounts doing that is such that doesn't work.
Further, the buy-in on using Twitter as a transmission medium hasn't really reached the saturation point that RSS did at its peak.
And finally, relying on a third-party - especially one with as dubious a history as Twitter - to maintain your data in foreseeable perpetuity is a bad plan in general. The benefit of RSS was that it was a standard, not a service itself.
Expecting Twitter to replace controlled curation is a recipe for noise. The value in RSS is some process or person is curating a defined set of data
To a certain extent, this is why email newsletters have had a resurgence in recent years. They allow curation while using a delivery mechanism almost every Internet user uses and understands (email, instead of an RSS client/service).
Let's say Twitter created a "standard" based on their platform, that could be adopted for free by any organization - then, we might talk about it replacing RSS.
Twitter can serve as a replacement for a subset of RSS functionality, but even allowing for Twitter to grow that subset, the biggest difference is architectural:
Tweets all run through twitter.com and your ability to retrieve the tweets you want or for the content owners to provide the information they wish depends on Twitter's continued willingness to provide the tools and/or API to do so and to allow you both to keep your accounts. Even assuming they will always want to facilitate this sort of thing and that neither you nor the content owners will do something to get kicked off Twitter, you can be sure that the tools and API will change relatively rapidly over the years ahead.
Meanwhile RSS is (usually) hosted on the content owner's server. The format has been stable for 15+ years at this point. Tools that worked for aggregating and dealing with RSS in 2000 still work today. And only your ISP could potentially stop you from retrieving the content you wish, when you want it, how you want to.
Trying to pit the two against each other misses the underlying issue that none of them really solve.
They are both nothing but feeds and I still can only read one feed item at the time. The actual curation done by others still don't satisfy me deep underlying need to have done the curation myself.
In the end we don't know what we don't know but we know there are things we don't know. Thats what keeps us going and keeps us plowing through the various feeds, curated or not.
Think about it like a bottleneck problem where I am the bottleneck because I am the slow interpreter:
Thanks for including this article, it was a really good read. We're working to address aspects of this problem with www.discovle.com, would love to hear your thoughts.
It's how you use Twitter though. Many people forget about Lists. I have a list dedicated to News tweets, such as the BBC, and Reuters, and NY Times...things like that.
Then I have another list for Tech news, and put several different tech websites feeds on it. Then one just for tech journalists (where yes, sometimes you see off-subject tweets, but I _know_ that I may see that sometimes, but you can have a quick interaction on what they say.
I open up a multi-pane client like TweetBot or TweetDeck, then have different lists per pane. I can go through a lot of information in a short amount of time this way.
"Even when you follow great people, you still have to wade through tweets that have little or nothing to do with news."
Kottke is not a great example of this. He has separate personal and professional accounts. His professional account is essentially just an RSS feed of his blog. Complaining about personal tweets junking up the personal account is silly in this case.
The v1.0 API used to allow you to fetch tweets without authentication, which allowed you to effectively use it as an RSS feed, convert it to a feed in whatever format you wanted, or build converters and visualization methods for other people.
I guess they want to control the ecosystem of what people do with Twitter data, which is completely contrary to the notion of RSS which is precisely to NOT control the ecosystem.
Twitter has replaced RSS for me. For me, the value of Twitter is learning new things, similar to the value I place on HN. I am pretty good at filtering out the noise because I usually look for links in posts. I rarely read a series of tweets in a conversation, and usually scroll right by link-less posts without reading.
then you've made the point. one needs to figure out what account to follow by discovering, while rss is usually marked with a predefined topic and way more intuitive for subscribing.
In the end, now 8 years later, it's clear that twitter DID kill rss as a dominate category of apps & services. We went from being overwhelmed by unread counts on the 'readers' to having flow. I'm not sure it's better, but it did solve the problem of feeling like you needed to keep up.
I think there's still more interesting work to be done in this space. Open social networks (that's what blogs are folks) plus users being able to control visibility of posts and frequency and open api's could do something which could unseat twitter/facebooks.