Thanks Ilya for the response. You're perfectly right, Superfeedr has a lot of work to do on the communication side.
Technically, I would expect subscribers like you to just perform the discovery and see that a given feed uses and hub and then subscribe to said hub, without really caring whether it's the google owned, a wordpress or a superfeedr one! Please, feel free to subscribe to the superfeedr hubs, the more subscribers, the more publishers! I kind of wish the Twitter folks would join this chat, so they can explain why they think PubSubHubbub isn't good enough for their requirements *... but I guess that's wishful thinking. Cheers, Julien * as XMPP was... On Thu, Nov 18, 2010 at 5:53 PM, igrigorik <[email protected]> wrote: > Julien, thanks for the quick reply! :) > > > > > > Take Buzz as an example.. At PostRank we had the "firehose" even prior > > > to the "real firehose" by actively crawling Google's sitemap (public), > > > identifying users with Buzz feeds, and subscribing to their individual > > > PSHB feeds. It was painful, and not very efficient, but it worked and > > > did not violate any TOS. In effect, it was an artificial barrier - > > > granted, there may be a reason why you might want to make it hard to > > > get at this data, but the point is, outsiders are still able to do it. > > > > And publishers can still block them! In the superfeedr approach, we use > the > > publisher callback for each and _every_ subscription made to the hub. The > > rules are up to the publishers. Some of them will accept blindly any > > subscription, some others will limit the number of subscriptions to a > given > > host/domain... etc. > > Yes, of course, and that's fine. > > > In the case of Posterous, same logic applies. I could run a crawler, > > > > > go gather all the RSS feeds, and call it a day. I'm not violating any > > > TOS, as much as I'm jumping over a technical barrier. If anything, > > > this is flawed thinking on the part of the distributor of those RSS > > > feeds. > > > > Yes you could. I'm not sure about the TOS part though. And no matter > what, > > it's likely that they will block you when they start seeing a massive > amount > > of subscriptions if they're not confident that you're doing a "fair-use" > of > > their data. > > The same will apply if you start polling them too aggressively. > > Technically, it's their users data, but we won't go down that rabbit > hole. ;-) > > > > THIS IS WRONG! I'm writing this in bold because I can't accept that > anyone > > would miss it. You can obviously get the content from Tumblr, Posterous, > > Gowalla, Typepad or any hub we host for free, and without a superfeedr > > account, exactly like you do for the Google hub! > > I know you and I know that you can't be ill-intentioned, so I think we > have > > communication work to do. Just to be sure : > > > > THERE IS NO DIFFERENCE FOR SUBSCRIBERS BETWEEN A SUPERFEEDR HOSTED HUB > AND > > THE GOOGLE HUB. > > Awesome! Thanks for clarifying this. I was under the impression that > as a consumer of your Hub, I actually needed some "superfeedr > credits". To be honest, that part was always a bit vague in my mind, > because I didn't really understand how you would monitor that if > someone just came in and subscribed to any PSHB enabled feed on > posterous. I maybe the odd lame duck in this case, but perhaps > something you could/should make more clear on your homepage. > > cheers, > > ig > > > > > > On Nov 17, 6:13 pm, Julien Genestoux <[email protected]> > > > wrote: > > > > Hello everybody, > > > > > > Today, twice I've had talks with people who assumed that by default > all > > > the > > > > data available via PubSubHubbub was expected to be free and > accessible by > > > > any one for any purpose. > > > > I think this is a 'wrong' idea and it doesn't serve us very well, so > I > > > wrote > > > > a blog post about it :http://blog.superfeedr.com/not-a-license/ > > > > > > I think it's awesome that so many services, like Buzz grant an almost > > > > unlimited and full access to all their data, but I think we (and > maybe > > > > anyone advocating) should make sure that we do not give the idea that > by > > > > implementing PubSubHubbub people give away their data and any rights > > > around > > > > it. > > > > > > Any feedback is much appreciated! Has anyone bumped into the same > > > > mis-understanding? or worse, had them? > > > > > > Julien >
