What does that mean? Any web resource that is self-describing can now be pushed via PubSubHubbub using the demo hub. For example, if you publish an ActivityStreams JSON resource you can now make it real-time with PubSubHubbub.
We've been working towards this for a while. Monica fleshed out most of the proposal, with helpful contributions from Martin. The "turduckin" problem still exists for resource types that rely on headers for correctness, but luckily the most useful formats thus far (RSS, Atom, ActivityStreams JSON, hAtom) are self-describing, so this is not a show-stopper. The next step is to codify this behavior (and Superfeedr's functionality) into a spec that builds on the PubSubHubbub core.
Some other fun side-effects:
- The reference hub will pass through non-RSS/Atom content without any modification, including data like JPEGs and binary content
- People who have subscribed to an HTML resource will now get an HTML payload delivered to them; that means people like Tantek who want to use hAtom in their HTML can make their hAtom real-time
- Feeds with charsets like EUR-JP will now get pushed to subscribers, though the hub codebase makes no attempt to do feed-entry diffing, since it cannot parse the XML
- Facebook's real-time API is one step closer to being another implementor of the PubSubHubbub spec