3 ms·

He mentions the lack of a notifications system. Isn't there room in this open system for a ping type notification service or group of services? The benefit for

He mentions the lack of a notifications system. Isn't there room in this open system for a ping type notification service or group of services? The benefit for such a service to be free would be that they could aggregate the data and mine it as twitter does. Then clients could fail back to polling should this service not be available.

icebraining 14y ago
pubsubhubbub A simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom and RSS. Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (feed URL) they're interested in is updated. The protocol in a nutshell is as follows: - An feed URL (a "topic") declares its Hub server(s) in its Atom or RSS XML file, via <link rel="hub" ...>. The hub(s) can be run by the publisher of the feed, or can be a community hub that anybody can use. (Atom and RssFeeds are supported) - A subscriber (a server that's interested in a topic), initially fetches the Atom URL as normal. If the Atom file declares its hubs, the subscriber can then avoid lame, repeated polling of the URL and can instead register with the feed's hub(s) and subscribe to updates. - The subscriber subscribes to the Topic URL from the Topic URL's declared Hub(s). - When the Publisher next updates the Topic URL, the publisher software pings the Hub(s) saying that there's an update. - The hub efficiently fetches the published feed and multicasts the new/changed content out to all registered subscribers. The protocol is decentralized and free. No company is at the center of this controlling it. Anybody can run a hub, or anybody can ping (publish) or subscribe using open hubs. To bootstrap this, we've provided an open source reference implementation of the hub (the hard part of the protocol) that runs on Google App Engine, and is open for anybody to use. https://code.google.com/p/pubsubhubbub/ https://code.google.com/p/pubsubhubbub/
- aaron-lebo 14y ago
  I've run across pubsubhubhub before (geez that's hard to write), and it seems like a really useful implementation. What I wasn't sure of is when he mentions polling is that instead of pshh or would that work with it?
  - icebraining 14y ago
    Polling always works, but if the feed and the client are PSHB-enabled, then they can use it.
  - smacktoward 14y ago
    Re the "hard to write" thing, PubSubHubbub's developers sometimes referred to it as "PuSH" for short. Which is easier.
- smacktoward 14y ago
  Dave also has a proposed notification standard of his own, called RSSCloud: http://rsscloud.org/ http://rsscloud.org/ There's been some drama between the developers of the two systems in the past: * http://scripting.com/stories/2009/07/22/snappyRetardedAnswers.html http://scripting.com/stories/2009/07/22/snappyRetardedAnswer... * http://brad.livejournal.com/2405147.html http://brad.livejournal.com/2405147.html * https://twitter.com/davewiner/status/23404535816912896 https://twitter.com/davewiner/status/23404535816912896 (Drama being nothing new to the RSS world, alas. Sigh)
- leephillips 14y ago
  I use this with my atom feed, and updates show up within seconds on Google Reader. Therefore I don't know why he says an open system can't be as fast as Twitter. Unless the technology he's committed too, RSScloud, doesn't work as well.

icebraining 14y ago

pubsubhubbub A simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom and RSS. Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (feed URL) they're interested in is updated. The protocol in a nutshell is as follows: - An feed URL (a "topic") declares its Hub server(s) in its Atom or RSS XML file, via <link rel="hub" ...>. The hub(s) can be run by the publisher of the feed, or can be a community hub that anybody can use. (Atom and RssFeeds are supported) - A subscriber (a server that's interested in a topic), initially fetches the Atom URL as normal. If the Atom file declares its hubs, the subscriber can then avoid lame, repeated polling of the URL and can instead register with the feed's hub(s) and subscribe to updates. - The subscriber subscribes to the Topic URL from the Topic URL's declared Hub(s). - When the Publisher next updates the Topic URL, the publisher software pings the Hub(s) saying that there's an update. - The hub efficiently fetches the published feed and multicasts the new/changed content out to all registered subscribers. The protocol is decentralized and free. No company is at the center of this controlling it. Anybody can run a hub, or anybody can ping (publish) or subscribe using open hubs. To bootstrap this, we've provided an open source reference implementation of the hub (the hard part of the protocol) that runs on Google App Engine, and is open for anybody to use. https://code.google.com/p/pubsubhubbub/ https://code.google.com/p/pubsubhubbub/

aaron-lebo 14y ago
I've run across pubsubhubhub before (geez that's hard to write), and it seems like a really useful implementation. What I wasn't sure of is when he mentions polling is that instead of pshh or would that work with it?
- icebraining 14y ago
  Polling always works, but if the feed and the client are PSHB-enabled, then they can use it.
- smacktoward 14y ago
  Re the "hard to write" thing, PubSubHubbub's developers sometimes referred to it as "PuSH" for short. Which is easier.
smacktoward 14y ago
Dave also has a proposed notification standard of his own, called RSSCloud: http://rsscloud.org/ http://rsscloud.org/ There's been some drama between the developers of the two systems in the past: * http://scripting.com/stories/2009/07/22/snappyRetardedAnswers.html http://scripting.com/stories/2009/07/22/snappyRetardedAnswer... * http://brad.livejournal.com/2405147.html http://brad.livejournal.com/2405147.html * https://twitter.com/davewiner/status/23404535816912896 https://twitter.com/davewiner/status/23404535816912896 (Drama being nothing new to the RSS world, alas. Sigh)
leephillips 14y ago
I use this with my atom feed, and updates show up within seconds on Google Reader. Therefore I don't know why he says an open system can't be as fast as Twitter. Unless the technology he's committed too, RSScloud, doesn't work as well.