Live data from Hacker News

Twitter and Facebook Both Quietly Kill RSS

staynalive.com

11–20 of 50 posts

Re: Twitter and Facebook Both Quietly Kill RSS

#11
99.99% of users will not notice or care.

I can see a use case where devs who don’t feel like building for Twitter’s API will want to use RSS to quickly get a user’s recent tweets. But I don’t think this will significantly impact anybody’s anything, and it feels like the author is exaggerating the consequences.

Re: Twitter and Facebook Both Quietly Kill RSS

#12
post #8
post #7

I have no interest in ever directly using Twitter and there's not enough content on there for me to bother with any workarounds. I currently use RSS for the one Twitter feed I bother to follow and if they ever really do get rid of RSS for their site, I'll just stop using even that. Not that much of a loss. My habits are such that if you don't offer RSS feeds of information I want, I probably won't ever get your infor…

I don't think getting you to visit their site is the point of the switch. Twitter and FB are in a position where they have enough addicted users that they can get away with messing with standards. RSS is outdated and slow, and FB and Twitter want people to use their data in a more sensible way, via their flexible APIs. It's trivial to build an APP that generates an RSS stream for an arbitrary twitter account with the…

> Of course, for now at least, there's no standard to this kind of API, but I think that people will eventually figure out what works and converge to it (as is the case with OAuth).

Actually there is but twitter is not interested (for obvious reasons): http://ostatus.org/sites/default/files/ostatus-1.0-draft-2-s...

Re: Twitter and Facebook Both Quietly Kill RSS

#13
post #10
post #8

Earlier quoted context omitted.

I don't think getting you to visit their site is the point of the switch. Twitter and FB are in a position where they have enough addicted users that they can get away with messing with standards. RSS is outdated and slow, and FB and Twitter want people to use their data in a more sensible way, via their flexible APIs. It's trivial to build an APP that generates an RSS stream for an arbitrary twitter account with the…

I hear people talk about how "RSS is so slow" all the time, but I still don't understand it. I see no failings or complaints about RSS. I get a headline and then I get an article. Are we talking speed between when content was generated and when it appears in an RSS feed? Honestly, I couldn't care less about that. I'll live if it takes fifteen minutes for an update to reach me. It's not like I'm getting a patient's li…

If you read about FriendFeed's Simple Update Protocol (http://blog.friendfeed.com/2008/08/simple-update-protocol-fe...), you'll find some good arguments about why RSS slow. The crux of the problem is that to get any updates on a feed, you have to request and download the entire RSS feed (which is filled with summary text and is of nontrivial size).

Consider the case of a real-time news aggregator. A news source doesn't update very frequently (say once every 5 minutes), but you want to provide updates super fast (say within 30 seconds). That means on average you have to scrape the entire RSS feed 10 times for a single update. On the other hand, FB/Twitter APIs give you the flexibility to do things like "download items after this id," which hog much less bandwidth.

Re: Twitter and Facebook Both Quietly Kill RSS

#14

The title is a bit of a double entendre. At first reading, I thought the claim was that (once again), Organization X had killed RSS (figuratively). As it turns out, Facebook and Twitter have, quite literally, killed RSS within the scope of their own systems by removing it from key locations. In my view, RSS was never the right tool for this application anyway. Social networks are naturally conversational in nature, b…

A common "general" application of RSS is news, but this will hopefully be slowly phased out as well. The New York Times offers an awesome API (http://developer.nytimes.com/) which gives you a much better view of their data than their RSS feeds (which they still provide).

Re: Twitter and Facebook Both Quietly Kill RSS

#15
^__^: hello, Welcome to the online store

^__^hello:________( http://bloq.in/577 )________

Christan Audigier bikini $23

Ed Hardy Bikini $23

Smful short_t-shirt_woman $15

ed hardy short_tank_woman $16

Sandal $32

christian louboutin $80

Sunglass $15

COACH_Necklace $27

handbag $33

AF tank woman $17

puma slipper woman $30

^__^hello:________( http://bloq.in/577 )________

  ~ ¤ ╭⌒╮ ╭⌒╮
╭⌒╭⌒╮╭⌒╮~╭⌒╮ ,)))),'')~~ ,''~) ╱◥█◣ ╱◥█◣ |田|田||田|田| ╬╬╬╬╬╬╬╬╬╬╬╬╬╬

Re: Twitter and Facebook Both Quietly Kill RSS

#16

The title is a bit of a double entendre. At first reading, I thought the claim was that (once again), Organization X had killed RSS (figuratively). As it turns out, Facebook and Twitter have, quite literally, killed RSS within the scope of their own systems by removing it from key locations. In my view, RSS was never the right tool for this application anyway. Social networks are naturally conversational in nature, b…

It's precisely because there's so much crud on Facebook that I consume it via an RSS feed rather than by visiting the site; that way, I can skim through a day's worth of friend updates in less than a minute. In any case, I have facebook.com ad-blocked in my primary browser, and use a secondary browser whenever I need to visit it. I don't visit Facebook much more often than once a week, and I only do if there's a particular update etc. worthy of attention.

I use jwz's RSS workarounds for my Facebook feeds: http://www.jwz.org/blog/2009/12/how-to-use-facebook-with-a-f...

Unfortunately, in the past week, Facebook's RSS feeds have been behaving very erratically. As seen in Google Reader, the update feeds show up as entirely refreshed - all new items - even though only a handful of items are actually new. The links on the RSS items have changed from the proper status update link to flat links to facebook.com. So rather than killing RSS, this move by Facebook is killing Facebook for me.

Re: Twitter and Facebook Both Quietly Kill RSS

#17
post #13
post #10

Earlier quoted context omitted.

I hear people talk about how "RSS is so slow" all the time, but I still don't understand it. I see no failings or complaints about RSS. I get a headline and then I get an article. Are we talking speed between when content was generated and when it appears in an RSS feed? Honestly, I couldn't care less about that. I'll live if it takes fifteen minutes for an update to reach me. It's not like I'm getting a patient's li…

If you read about FriendFeed's Simple Update Protocol ( http://blog.friendfeed.com/2008/08/simple-update-protocol-fe... ), you'll find some good arguments about why RSS slow. The crux of the problem is that to get any updates on a feed, you have to request and download the entire RSS feed (which is filled with summary text and is of nontrivial size). Consider the case of a real-time news aggregator. A news source doe…

Looking at that article, the slowness doesn't come from having to download the entire RSS feed. As commenters there note, If-Modified-Since means you only need to download the feed when there are changes. So in your second paragraph, you have to ping the RSS feed 10 times, but you'd only need to download it once.

Rather, the slowness seems to come from the lack of an aggregation mechanism. If I want to follow 100 feeds (e.g. 100 Twitter users), I have to query each of those 100 feeds. Even though I can query them efficiently using If-Modified-Since, that's still slower than firing off one query to find out which of those 100 feeds have updates, and then querying only those which do.

Re: Twitter and Facebook Both Quietly Kill RSS

#19

99.99% of users will not notice or care. I can see a use case where devs who don’t feel like building for Twitter’s API will want to use RSS to quickly get a user’s recent tweets. But I don’t think this will significantly impact anybody’s anything, and it feels like the author is exaggerating the consequences.

Most users of anything don't care about RSS. Most users also don't explicitly care about the API, either — those are both at a lower level than what users notice. That doesn't mean they're worthless.

Re: Twitter and Facebook Both Quietly Kill RSS

#20
post #17
post #13

Earlier quoted context omitted.

If you read about FriendFeed's Simple Update Protocol ( http://blog.friendfeed.com/2008/08/simple-update-protocol-fe... ), you'll find some good arguments about why RSS slow. The crux of the problem is that to get any updates on a feed, you have to request and download the entire RSS feed (which is filled with summary text and is of nontrivial size). Consider the case of a real-time news aggregator. A news source doe…

Looking at that article, the slowness doesn't come from having to download the entire RSS feed. As commenters there note, If-Modified-Since means you only need to download the feed when there are changes. So in your second paragraph, you have to ping the RSS feed 10 times, but you'd only need to download it once. Rather, the slowness seems to come from the lack of an aggregation mechanism. If I want to follow 100 fee…

Good point. The reason I didn't bring that up is that the comments suggest that if-modified-since isn't universally adopted by RSS publishers.
Post reply on HN