On Sun, Mar 14, 2010 at 4:19 PM, Jay Rossiter <[email protected]> wrote:
>
>     I would definitely argue that any firehose definition belongs nowhere 
> near individual feeds.  It's far too generalized, and not likely to be used 
> by most subscribers.
>
> I think that this could very easily be an extension of how PuSH already 
> works, just by adding two new modes.
>
> When a subscriber discovers a feed with PuSH enabled, they have the option to 
> query the hub (e.g.)
>
> &hub.mode=listmodes  (or discovery, or query, or ...)
>
> The hub returns a newline separated list of modes that it supports:
>
> subscribe [<0/1> <URI/email>]
> unsubscribe
> firehose [<0/1> <URI/email>]
> unfirehose
> publish [<0/1> <URI/email>]
>
> The subscriber can then, if supported, subscribe to the firehose or just do a 
> simple subscribe.  The following parameters could indicate whether 
> authentication or authorization is required to access a specific method and a 
> contact method to request access, and the subscriber can be notified [OOB] 
> that manual steps are required.  (I certainly wouldn't want to just give full 
> firehose access to anyone that came along, just because they thought they 
> wanted it.)
>
> I think that the authorization indicator could stand to be used on all hub 
> modes, because there are hubs (i.e. Superfeedr) which are already requiring 
> authorization for simple public feed subscriptions. This gives subscribers an 
> easy way to know not to bother making a subscription request at all.  
> Unsubscribe-type method should never require authorization.

This is a proposal for a firehose feed. How would it work for track
and geo queries? Couldn't this be more generic?

> (IMO, requiring auth to subscribe to public feeds is harmful to the community 
> and contrary to the reasoning behind designing PuSH, but that's another 
> show.</AB>)

Not sure about this assertion. We're trying to separate ideology from
the PubSubHubbub spec, even though often the lines are blurred. The
goal is a useful conduit for pubsub data. I see valid use-cases (like
analytics) for requiring authentication for public feeds.

Reply via email to