I often seem to have trouble with async verification at pubsubhubbub.appspot.com. I don't know if async verification is broken or just very slow, but it's slow enough that it's not useful for testing (e.g. 10 minutes later, the hub still hasn't called back to verify the subscription).
To get reliable subscriptions, I either use sync subscriptions or run my own hub. (When I run a separate hub using the PSHB source code, unchanged, async subscriptions are verified immediately.) —Ping On Sat, Jan 1, 2011 at 23:17, Ravi Pinjala <[email protected]> wrote: > It could be async verification - my subscriber client always uses > sync, but other clients probably default to async. Using async means > that there could be a delay before the subscription is verified, and > it might be the case that adding a sync subscription to the mix forces > the pending async requests through. (Honestly, though, this is mostly > wild speculation.) > > --Ravi > > On Sat, Jan 1, 2011 at 10:23 PM, Noah McIlraith > <[email protected]> wrote: > > I've got a GAE app running just to test this out. > > An example feed would be http://pushfeedtest.appspot.com/feed/blah > > 'blah' can be any string (different feeds). > > The hub is told that there are changes every 1 minute > > (alternatively, http://pushfeedtest.appspot.com/pump to force it). > > For some reason the subscriber I found > > at http://bitbucket.org/pstatic/pubsubhubbub/wiki/Home works fine, but > my > > own, push-bot.appspot.com and even Google Reader don't work until the > > bitbucket one subscribes, and then they all start working. >
