Polling sucks. We think a decentralized pubsub layer is a fundamental, missing layer in the Internet architecture today
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).
the only way to enable client subscribers to play in this async messaging world is via some type of relay service
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
looking
forward to decentralized social networking
Aggregated Content Distribution
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.