Could someone quickly summarize the technical differences between RSS vs. PubSubHubBub?
[Yes, I could google it myself :) -- but am also interested in various 2nd order issues (e.g. which is trending up/down, why does Winer not like PubSubHubBub) which would take more searching to learn.]
The latter is an attempt to remove polling from the architecture and thereby make the updates more realtime. A client would actually run a small server (in the "listener" sense of the word "server") that a "hub" would hit when there's a resource update.
Dave made significant contributions to RSS, and I suspect that he's experiencing the motherly instinct to protect his baby. Note the phrasing of point #2, and how he refers back to it from point #15. He's underscoring how he's not in "competition" with Google. But that doesn't mean that his ego is completely decoupled from the success of RSS.
On the one hand, I abhor polling and usually love to see it removed where possible. On the other hand, I've never thought RSS was insufficiently realtime. I tend to flood myself with too many feeds, and then it becomes an issue of self-discipline to trim or ignore it.
[Yes, I could google it myself :) -- but am also interested in various 2nd order issues (e.g. which is trending up/down, why does Winer not like PubSubHubBub) which would take more searching to learn.]