On 3/4/2010 11:39 AM, Brett Slatkin wrote: > Hey Jay, > > On Thu, Mar 4, 2010 at 11:33 AM, Jay Rossiter <[email protected]> wrote: >> Is there a way for Wordpress users to disable this? Since Wordpress has >> an internal hub, I'm seeing one potential side-effect. Some sites (e.g. >> techcrunch) use both Wordpress and FeedBurner. >> >> Since FeedBurner already uses the appspot hub, there are now two hub >> references in the feed. Depending on which one you subscribe to you're going >> to get completely different content. One which will come directly from >> Wordpress without any of FB's analytics added (since I can only assume that >> WP is handling feedcontent internally, and not HTTP-retrieving its own >> content), and one from Appspot, which has been modified by FeedBurner. >> >> This kind of issue is only going to get progressively worse as more and >> more services implement PuSH. > I'd say this is mainly a problem with FeedBurner, not WordPress. > > Feed proxy services should do it like this: 1) subscribe to the source > feed with URL X, 2) publish updates using the proxy's hub (or a > user-configured hub if desired) on URL Y, 3) have blog services > advertise URL Y as their feed URL for subscribers. Then subscribers > will only pick up the proxied feed and there will be no conflict. > > In the case of FeedBurner, I know the guys on that team are actively > working to fix this problem. Does that solution make sense to you, > Jay?
We've discussed this internally several times as well. My stance is that
any service which modifies and republishes the feed should be scrubbing any
hub references from previous sources. I think that's in agreement with what
you said -
Wordpress publishes feed with WP hub
Feedburner pulls feed from WP, modifies feed, removes WP hub, adds Appspot hub
with new 'self' href.
Users see only one option to subscribe to, which has the content containing
all modifications.
To make updates fastest, FB (etc.) /should /implement hub chaining so that
updates aren't poll-based, but this also has problems if a third-party hub is
inserted by the publisher (e.g. Superfeedr), because they're likely polling
content post modification. It leads to a chain-loop.
--
Jay Rossiter | Software Engineer/System Administrator
Pioneering RSS Advertising Solutions
[email protected] <mailto:[email protected]> | Phone: 503.896.6187 |
Fax: 503.235.2216
Website: www.pheedo.com <http://www.pheedo.com/> | RSS:
www.pheedo.info/index.xml <http://www.pheedo.info/index.xml>
<<inline: pheedo.gif>>
