Private Webhooks. Private Feeds.
This post is for people who want to be able to subscribe to private feeds, or people who want to be able to communicate from one site to another using webhooks. I've talked a number of times on the subject at various conferences, but haven't posted publicly about the approach.
Thankfully, it's simple. You can see the whole thing here, in this nice set of slides:
Or, you can look at this diagram that illustrates the protocol flow. Note that all the curl commands needed to make a secure, private connection are included in the diagram.
The goal is to allow crypto-less communication across sites while retaining a familiar user experience. This approach achieves that, I think. What do you think?
posted by Blaine at
6:25 PM
4 Comments:
Awesome to see this resurface :)
Hi,
I have a question about the diagram. I'm interested in private subscriptions to feeds. Is this an example of a private subscribe? What will be returned when Alice GETs http://bobnews.com/atom.xml to find the 'rel=hub'? A full feed? Or just 'headers'? Otherwise this is not really private, right?
Peter
I expect the feed would contain only the public items (of which there may be none). Private feed content is pushed through PubSubHubbub only.
You might additionally show private entries the viewer is authorized to see if the client can authenticate in some other way, but that's not really particular to this technique for webhooks.
I have a question about the diagram. I'm interested in private subscriptions to feeds. Is this an example of a private subscribe? What will be returned when Alice GETs
Post a Comment
Subscribe to Post Comments [Atom]
Links to this post:
Create a Link
<< Home