On 3/14/2010 10:38 PM, Eric Mill wrote:
>>     I'll know that I'll be adding a blacklist to my subscription client for
>> hubs that require authentication on public feeds.  It's simply not in my
>> workflow to go to every new hub trying to get an account for a service that
>> is designed to benefit the publisher.  If they go out of their way to make
>> using PuSH with their feeds difficult, I can only oblige them by not using
>> it. They and their readers lose out on the benefits they wanted to achieve.
> I think you'd be blacklisting the wrong entity.  If a publisher of a
> public feed chooses to use a "private hub" for PuSH delivery, instead
> of some public community hub, then it's the publisher who's made that
> decision.
>
> Since we can likely all agree that private hubs serve a valid purpose
> for private feeds, you'd end up unfairly demonizing private hubs that
> don't actively verify that the feeds that get submitted to them are
> private.
>
> -- Eric

    Maybe, maybe not - it depends on the hub and the publisher.  Superfeedr's
general hub (http://superfeedr.com/hubbub) requires authentication for all
subscriptions, period.  It's only usable by users of their service.  i.e. a
Superfeedr user can subscribe to ANY feed using Superfeedr's hub (even one
without hub tags, from my understanding), but a non-Superfeedr user can't
subscribe to ANY feeds, even though they notify users that this is the hub to 
use.

Take, for example, the Superfeedr blog feed:  
http://blog.superfeedr.com/atom.xml
It publishes

    <link href="http://blog.superfeedr.com/atom.xml 
<view-source:http://blog.superfeedr.com/atom.xml>" rel="self" 
type="application/atom+xml"/>
    <link rel="hub" href="http://superfeedr.com/hubbub 
<view-source:http://superfeedr.com/hubbub>" />

but you can't actually use that information without a login.

-- 
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>

Reply via email to