Ryan, In defense of PubSubHubbub, I want to say that it's not a protocol issue, but rather an implementation/management issue. I do not work for Google, but from the outside, it seems that Google is probably not investing a lot in Feedburner at this point.
Anyway, as you've noted, Superfeedr is always happy to help and we are working hard to make things better (and cheaper too!) on our end, despite the inherent complexity of the open web. Julien 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 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? > > > > > On Tuesday, August 14, 2012 9:53:06 AM UTC-7, Roman Perepelitsa wrote: > >> Hi Ryan, >> >> http://rss.cnn.com/rss/si_**topstories.rss<http://rss.cnn.com/rss/si_topstories.rss>is >> also a feedburner feed ( >> rss.cnn.com is CNAMEd to cnn.feedproxy.ghs.google.com). The feedburner >> team has been notified. >> >> Roman. >> >> On Fri, Aug 10, 2012 at 9:58 PM, Roman <[email protected]> wrote: >> >>> Hi Ryan, >>> >>> There are no known problems that could cause this. I'm out of town till >>> the end of the week but I'll take a look what's going on as I'm back. >>> On Aug 10, 2012 12:37 PM, "Ryan Williams" <[email protected]> wrote: >>> >>>> I don't appear to be receiving notifications for some feeds that I >>>> subscribed to this morning, such as TechCrunch ( >>>> http://feeds.feedburner.com/**techcrunch<http://feeds.feedburner.com/techcrunch>), >>>> ReadWriteWeb >>>> (http://feeds.feedburner.com/**readwriteweb<http://feeds.feedburner.com/readwriteweb>), >>>> SI Top stories >>>> (http://rss.cnn.com/rss/si_**topstories.rss<http://rss.cnn.com/rss/si_topstories.rss>) >>>> to name a few. There may be more, but I just started looking having >>>> subscribed to a couple hundred earlier today. I am getting notifications >>>> from other popular feeds, like BoingBoing (http://feeds.boingboing.net/ >>>> **boingboing/iBag <http://feeds.boingboing.net/boingboing/iBag>) and >>>> Ars Technica >>>> (http://feeds.arstechnica.com/**arstechnica/everything<http://feeds.arstechnica.com/arstechnica/everything>) >>>> as well as many other less popular or less frequent feeds, and have >>>> confirmed with the hub that I do have a subscription for the feeds in >>>> question, so things appear to be in order with my client code. It doesn't >>>> seem to be a feedburner issue if some are working and some are not. >>>> >>>> I just checked the spec about feeds with multiple hubs and will go >>>> ahead and subscribe to each hub a feed specifies to see if that helps. So >>>> far, I'm just using the first hub listed. >>>> >>>> But, is there any known issue to watch out with certain feeds or are >>>> others seeing this? >>>> >>> >>
