On Oct 27, 11:03 am, Jeff Lindsay <[email protected]> wrote: > 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?
Yeah. I think I could branch the reference hub and run it with my OAuth changes on appengine. It needs some work still however. There are some feed providers that offer OAuth support. Twitter and Brightkite are the ones I've been using. But like I mentioned, it's a bit problematic since neither of those services put OAuth in the Www- Authenticate header so the hub could automatically detect it. > It seems convention to be compatible with most readers is to use HTTP auth. True. All HTTP authentication methods should be supported. OAuth just seems like a perfect fit since it is made for the purpose of authorizing others (the hub) to access your private content. > 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. That sounds like a cool idea. :) - Teemu
