On Sun, Mar 7, 2010 at 2:45 PM, Julien Genestoux <[email protected]> wrote: > We have a few publishers who want to use one of Superfeedr's hub instead of > the wp.com hub, so they can have a few stuff that we provide. I tell them to > add the discovery link, but I'd be interested to know about what happens > with your hub link?
Here's what I'd suggest if you only want to use a 3rd party hub and not a hub built into WP. Don't use the PuSHPress plugin. There are at least 2 other WordPress plugins that do nothing but at support for 3rd party hubs, one of those should work fine for these situations. > Do you leave it by default? or remove it? To get a bit more in depth, the PuSHPress plugin applies a WP filter (called 'pushpress_hubs' ) to the array of hubs that PuSHPress uses. By default it only has one hub in that array, itself. I did this to allow other plugins or themes to be able to alter the hub list if they really wanted to. > I'm asking because when there are 2 links (or more), it's not sur that > everybody will subscribe to both and then, we can provide the publisher with > stuff like analytics, or publisher-validation or even full export of the > subscriptions :( > Can you explain how you guys behave in this case? There's a thread on this list about what feed proxies should do (for things like Feed Burner for instance) and at this point I think ping chaining is probably the most reasonable approach. It doesn't exactly fit in with what SuperFeedr does because it only provides clients at the end of the chain with ping data, it's doesn't actually server feeds (in the way that Feed Burner does for example). -- Joseph Scott [email protected] http://josephscott.org/
