> 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 > > -- > Jay Rossiter | Software Engineer/System Administrator > Pioneering RSS Advertising Solutions > > [email protected] | Phone: 503.896.6187 | Fax: 503.235.2216 > Website: www.pheedo.com | RSS: www.pheedo.info/index.xml >
