11–20 of 20 posts
I think a more fundamental reason is that RSSCloud solves the problem "I used to use RSS to read articles, but the 15 minute delay between the article being posted and me being able to skim it in my RSS reader was unacceptable" and that this is a problem real people do not have .
RSSCloud is useless, for increasingly ridiculous reasons: 10e2 It's idiotically-designed (he thinks traditional SOAP posted to a resourcey URL is REST!) 10e4 It doesn't help centralized aggregators scale at all 10e8 It doesn't work with NATed clients 10e16 It was specced/never-implemented/forgotten by Dave Winer 8 years ago
I think a more fundamental reason is that RSSCloud solves the problem "I used to use RSS to read articles, but the 15 minute delay between the article being posted and me being able to skim it in my RSS reader was unacceptable" and that this is a problem real people do not have .
RSSCloud is useless, for increasingly ridiculous reasons: 10e2 It's idiotically-designed (he thinks traditional SOAP posted to a resourcey URL is REST!) 10e4 It doesn't help centralized aggregators scale at all 10e8 It doesn't work with NATed clients 10e16 It was specced/never-implemented/forgotten by Dave Winer 8 years ago
You seem to like that word "idiot", arent't you? In two days you used it for Dave Winer and Matt Mullenweg ( http://news.ycombinator.com/item?id=810288 ). Who's next?
b) Dave isn't an idiot -- he's a poisonous egomaniac asshole that successfully weedles his way into anything tangentially related to any of his pet projects, and proceeds to do whatever he can to be credited for other people's work, impede progress, and fuck people over. It's his designs that are idiotic.
RSSCloud or not -- I do happen to think that we need a push RSS solution -- what really bugs me is the fact that once again, we're inventing different standards to do the exact same thing. As if ATOM vs RSS wasn't enough, now we have RSSCloud + PubsubHubbub to worry about. PSHB already has Google behind it (all of Feedburner feeds support it), so I really fail to see what wordpress won by adopting RSSCloud. Besides,…
Dave will never stand by and let a perfect solution replace an old poorly-specified ill-used mediocre one that he somewhat-falsely claimed to have invented. Instead he'll repeatedly change the canonical version of the spec live, without changing the version number or telling anyone (much less preserving the previous versions). It's super effective, at least for creating drama.
Here's my understanding of the potential for a scalability problem. EXAMPLE: twitter.com has 24,650 twitter followers. If Dave gets 24,650 followers on an RSSCloud architecture then this is what happens when he posts. 1. Dave creates a 140 char post. Hs blogging software sends a notice to the cloud server that he has an updated RSS feed. 2. the cloud server sends update notices to the 24,650 subscribed "listeners" to…
You are concerned about the inefficiency of fetching all the items in a feed when just one item changes. Is that a real issue? Consider your use case. How much data is really being requested? If it is a real issue, the server might want to limit the # of entries returned based on the if-modified-since header. As for the load of all that traffic hitting the server in the space of a few seconds, ngnix can push a lot of requests on modest hardware and the load on whatever application logic is involved in generating the feed can be knocked way down by having it cache all feed requests for a second or two.
If you really wanted your desktop RSS reader to be just as awesome and real-time as Twhirl then just set all the feed refresh intervals to 5 minutes, no RSSCloud needed.
The thing that really gets me with all this real-time hype is people attribute the rise of Twitter to all the awesome desktop clients built for it so you can receive your tweets in real-time, the problem is they aren't actually real-time, all those desktop clients use polling, just with a really short interval. If you really wanted your desktop RSS reader to be just as awesome and real-time as Twhirl then just set al…
I always thought that it was somewhat ironic that nobody had a problem with me refreshing slashdot.org every 10 seconds trying to get a first post, but that they had a very large problem when my rss poll hit them more than once an hour (is at least what their recommended interval used to be.)
The thing that really gets me with all this real-time hype is people attribute the rise of Twitter to all the awesome desktop clients built for it so you can receive your tweets in real-time, the problem is they aren't actually real-time, all those desktop clients use polling, just with a really short interval. If you really wanted your desktop RSS reader to be just as awesome and real-time as Twhirl then just set al…
Having done almost this exact thing, the issue is that 4 out of 5 large websites will have blocked you buy your fifth poll for abusing their service. I always thought that it was somewhat ironic that nobody had a problem with me refreshing slashdot.org every 10 seconds trying to get a first post, but that they had a very large problem when my rss poll hit them more than once an hour (is at least what their recommende…
But I agree that most places will throttle you if you request their feed too often, so how are they going to feel when every one of their subscribers requests their feed within the same minute every time they make an update? I guess that's the big question.
The proposal never made sense. Most people don't use desktop feed readers and even if they did this solution wouldn't be scalable (as Cadenhead mentioned). Google Reader knows when you update your feed because you already ping Google. In my experience they are grabbing the feed in a few seconds anyway--it's up to them to show this to users in real time if they want to but there is nothing stopping them. It seems like…
If I am worried that nothing has come in for 5 minutes I can always hit refresh.