Whoa, nice find. I have to think Google Reader uses async because I've still got no publisher diagnostics for my feedburner feeds. Even after changing the url and resubscribing to avoid caching. No real- time for http://pubsubhubbub.travisrss.x10.mx/?feed=rss2 either, but I can see the diagnostics from lam3r4370's subscriber.
It seems to me that where sync works, async should work just as well but not necessarily vice-verca if the host is limiting concurrent connections. Strange... On another note, I changed the hub at superfeedr.travisrss.x10.mx to see how quickly Google Reader would subscribe to the new hub (updates were working realtime before this change). I did this on Saturday and still have no real-time updates. A work around is to resubscribe, adding some useless parameters to the url. Google's caching seems to be getting in the way here. Julien, Does SuperFeedr throttle polling frequency based on how often it sees the feed change? I made a couple feeds that don't publish but just rely on SuperFeedr's polling. One gets new items more frequently than the other, and my logs show SuperFeedr polling them differently. On Dec 7, 1:07 pm, lam3r4370 <[email protected]> wrote: > If you change hub.verify to sync all works! > > On Dec 4, 5:23 pm, lam3r4370 <[email protected]> wrote: > > > Yeah ,it's the same with me. > > If you have a published feed , the new updates arrive. > > But if you try to add new feed ,even > > throughhttps://pubsubhubbub.appspot.com/publish > > but there isn't publisher diagnostics... > > > On Dec 4, 4:29 am, Travis Yaremco <[email protected]> wrote: > > > > Ah, OK. Thanks Julien. I'm curious if anyone knows anything about > > > the problems subscribing to App Engine reference hub. Seems to me > > > this is something Brett should know about... > > > > On Dec 3, 6:14 pm, Julien Genestoux <[email protected]> wrote: > > > > > Hey Travis, > > > > > Good set of tests. A few things. From what I can tell Netvibes is > > > > currently > > > > subscribing in batches, which means that they do not do it in a timely, > > > > regular manner. They haven't subscribed to anything in the past weeks > > > > though. > > > > > Ju > > > > > -- > > > > Julien Genestoux, > > > > >http://twitter.com/superfeedrhttp://superfeedr.com > > > > > +1 (415) 830 6574 > > > > > On Fri, Dec 3, 2010 at 5:04 PM, Travis Yaremco <[email protected]> > > > > wrote: > > > > > I could not figure out why updates to my Feedburner-Pingshot feed were > > > > > not appearing in Google Reader in real-time. So I decided to make an > > > > > easy way to test the hubs and made two Wordpress blogs that use the > > > > > pubsubhubbub plugin. Anyone can make a post, which will update the > > > > > feed and notify it's respective hub. > > > > > >http://superfeedr.travisrss.x10.mx/ > > > > >http://pubsubhubbub.travisrss.x10.mx/ > > > > > > I used PushBot (http://push-bot.appspot.com/) as a subscriber. This > > > > > web-based xmpp clienthttp://www.webxmpp.com/main.htmlgivesa > > > > > satisfying auditory cue when things are working. > > > > > > Results: > > > > > [superfeedr.travisrss.x10.mx] > > > > > PushBot reports successful subscription. Posts arrive real-time from > > > > > PushBot. Same results with Google Reader. However, posts are NOT > > > > > real-time for Netvibes > > > > > > [http://pubsubhubbub.travisrss.x10.mx/] > > > > > PushBot reports successful subscription (for some reason). Posts do > > > > > NOT arrive at all from PushBot. Posts only show in Google Reader and > > > > > Netvibes after polling. No publisher diagnostics at > > > > > pubsubhubbub.appspot.com. > > > > > > So I guess pubsubhubbub.appspot.com is not taking new subscribers? > > > > > This would explain my Feedburner problems. It seems that Netvibes is > > > > > either not requesting subscriptions or not accepting notifications. > > > > > Give it a shot, anyway. > >
