Hi Ryan, I've made a couple of fixes. Could you check whether things have improved on your end?
Roman. On Thu, Aug 16, 2012 at 4:37 PM, Ryan Williams <[email protected]> wrote: > Thanks Roman, I appreciate your help and work on improving reliability. > > On Thursday, August 16, 2012 6:51:41 AM UTC-7, Roman Perepelitsa wrote: > >> On Wed, Aug 15, 2012 at 6:39 PM, Ryan Williams <[email protected]> wrote: >> >>> Ah, good catch. It does seem to be mostly an issue with FeedBurner >>> feeds. Thanks for looking into it. Radar is coming through now along with >>> ReadWriteWeb. Still no notifications for TechCrunch, TechDirt, and GigaOm, >>> among other FB feeds. >>> >>> This seems to indicate true/open PubSubHubbub is not reliable when >>> perhaps the largest publisher has these problems? Does FeedBurner care >>> about it working? I'm not trying to be dramatic, but rather just trying to >>> get a feel for the environment as its been over a year since I did my first >>> client implementation and now trying to do one again. >>> >>> Not to single FeedBurner out either, because pushpress is very >>> problematic too, at least with the subscription process. >>> >> >> I feel your pain, Ryan. >> >> We are actively working on improving reliability of the hub on >> pubsubhubbub.appspot.com. We are also looking at the issue affecting >> FeedBurner feeds. >> >> I know and like Superfeedr, and it protects me from most of these issues, >>> but in theory it's just a little bit more work to subscribe to a feed's hub >>> for which there is no cost, if all is working right. >>> >>> Is it advisable or best practice with PubSubHubbub to create clients >>> that fallback to polling and/or use services like Superfeedr? >>> >> >> We are committed to making the hub very reliable so that you won't have >> to resort to polling. >> >> Roman. >> >
