Group items tagged

Green is good, red is bad

criteria to consider for each protocol

Superfeedr is the only non-google PubSubHubbub

server-to-server

extension to Atom and RSS

web-hook-based

hub(s) can be run by the publisher

or can be a community hub

If the Atom file declares its hubs

avoid lame, repeated polling

decentralized

when you copy an entry from any feed document other than that feed document whose metadata is in the entry's atom:source

Atom spec didn't envision this use case

atom:source is almost, but not quite, what's needed

confusion is understandable

like atom:source

not aggregate at the PubSubHubbub level until you've proved that

(a) you have to

(b) multipart/related won't cut it

pretty much what FeedMesh was intended to provide

to show provenence, you need to add an extension element

skeptical about ease of subscriber implementation

Polling sucks

fundamental

missing layer in the Internet architecture

looking forward to decentralized social networking

Aggregated Content Distribution When a subscriber indicates the same callback URL is used for multiple subscriptions, hubs MAY choose to combine content delivery requests into a single payload containing an aggregated set of feeds.

Example aggregated feed

a fundamental design that looks like this: This picture leaves out multiple publishers and subscribers and the subscriber registration process, but you get the basic idea

fine for server subscribers (like, say Google Reader) but not for client subscribers (like, say TweetDeck).

In this approach, the client subscriber makes an outbound connection to some type of relay infrastructure

technically feasible

Yes, having to relay messages sucks. But the question is

Harry Pierson

using Atom

We love XMPP and we love REST

conversations that occur on downstream aggregation sites

parallel discussions on the originating Web site

pulling external discussions to the source

An Initial Presentation

multiple downstream destinations

fractured conversations

send the new comments to the site which is lacking the full conversation

implied (all data is public)

turn this brand-new protocol into a new standard

a serious challenge to services like JS-Kit Echo and Disqus

commentary in a virtuous cycle

user centric

presentation: Salmon Real Time Commenting FlowSalmon Real Time Commenting Flow