Oh oh oh, I get it. This is about private feeds behind OAuth, and having the subscriber allow the hub to access it. I was confused and thought it was about the hub getting access to the subscriber callback.
I think a proof of concept would be fun to play with. The private feed thing does need to be solved. But how many feeds are behind OAuth? It seems convention to be compatible with most readers is to use HTTP auth. By the way, I'm interested in building a proxy service that provides OAuth for resources protected by HTTP auth. The idea is to bootstrap OAuth usage this way by making almost any HTTP auth protected resource authenticatable with OAuth --- which is particularly useful in a situation such as if PubSubHubbub supported OAuth, because it would mean Hubs could access non-OAuth protected feeds if the user was willing to use the proxy. -- Jeff Lindsay http://webhooks.org -- Make the web more programmable http://shdh.org -- A party for hackers and thinkers http://tigdb.com -- Discover indie games http://progrium.com -- More interesting things
