Dan, Sorry for the late reply. First, I'd like to thank you and the Feedburner for the efforts. A few comments:
- *When a hub crawls a proxied feed, the proxy should treat it as a ping.* I need to think about this a bit. Superfeedr acts as a "default" hub, which means that we work for any feed, by polling on behalf of the subscriber(s). This may cause issues, as we guarantee our susbrcibers that we will poll the feed at least once a day, to tell them about the status of the feed. I understand is goes a little bit beyond the regular PubSubHubbub approach, but we may need to implement something specific on our end so we don't identify our pollers as the hub when we're not the designated hub. Another solution would be that when the proxy gets a request from a hub, it should check that the hub is (or not) the designated hub. *When hub links appear in the source feed, proxies should subscribe to them. * As I agree with this, your comments about the proxy which may consider the fat ping as a light ping is worrysome, as there are cases where the source feed isn't updated yet (caches... ), and polling this (by not trusting the hub) could result in an inaccurate content and a delay as long as the proxy didn't poll the source feed while it hasn't been updated. [This is the behavior that Superfeedr (and I believe other subscribers) has had a for a long time, which caused us a lot of issues with Feedburner specifically]. Apart from this, it would be very interesting that proxies, when they subscribed to the source feed's designated hub, that they mention the number of susbcribers that they have themselves for the proxied feed. this way the original hub can report that number to the publisher. I understand there may be some dupes, but at least, there will be data. However, this is certainly a secondary issue. Thanks again for the hard work on this. Cheers, Julien On Wed, Jul 14, 2010 at 10:48 PM, Dan <[email protected]> wrote: > Hi all, > > I wrote up a doc on the Pubsubhubbub wiki describing some problems > that arise getting hubs and feed proxies to work together nicely, and > an approach for solving those problems: > > http://code.google.com/p/pubsubhubbub/wiki/HubsAndFeedProxies > > The approach described is (roughly speaking) the approach taken by > FeedBurner and the reference hub. > > Any comments you could provide would be great. One thing in particular > we need to figure out: what convention we should adopt for the HTTP > headers used when hubs crawl feeds. Some possible conventions are > described in the "Identifying hubs" section... please let me know what > you think a good convention would be. > > Thanks! > > Dan Rodney > FeedBurner
