Skip to main content

Authenticated RSS Feeds: Drosophilia of Delegation?

Jon Udell has noticed that authenticatedRSS feeds don't work very well.  It's a chicken and egg situation: There are few authenticated RSS/Atom feeds because there are few feedreaders that deal with them, and vice versa.  But beyond thatbootstrapping problem there's a larger one.

A lot of popular feed reader services such as My Yahoo or Bloglines arehost based.  With current feed authentication mechanisms, this meansthat you have to hand your user name(s) and password(s) to your feedreader service and let it impersonate you to do anything useful.  Notgreat.  Recently, Kim Cameron has been blazing away at theconcept of impersonation, not just the problem of handing your passwordout.  I'd like to suggest that authenticated feeds provide an idealplace to experiment with better approaches:  They're read only, the baris currently very low, and there's a whole host of immediatepossibilities that would become possible once you can cleanly authorizea feed reader to read feeds on your behalf.  I think the right way todo this is through a lightweight assertion mechanism that lets you say"I authorize service X to asynchronously read feed Y on my (Z's)behalf".

I'm still trying to digest all of the twists and turns of the threadbelow.  I am pretty sure that whatever solution is adopted, it has tocleanly allow for the "allow a service to read a feed" to be at alluseful.

The Impersonation/Delegation Discussion
Presented in backwards chronological order
Dramatis Personae: Eve Mahler, Kim Cameron, Conor Cahill, Pete Rowley,Phil Windley

PhilWindley: On Impersonation and Delegation
ConorCahill:  Delegation, Impersonation, and downright access
PeteRowley: The umpire delegates back
ConorCahill: SAML, Liberty, and user presence
Kim Cameron: Drillingfurther into delegation
Kim Cameron: Wrong-headedimpersonation

Tags: , , , , , ,

Popular posts from this blog

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

XAuth is a Lot Like Democracy

XAuth is a lot like democracy:  The worst form of user identity prefs, except for all those others that have been tried (apologies to Churchill).  I've just read Eran's rather overblown "XAuth - a Terrible, Horrible, No Good, Very Bad Idea", and I see that the same objections are being tossed around; I'm going to rebut them here to save time in the future.

Let's take this from the top.  XAuth is a proposal to let browsers remember that sites have registered themselves as a user's identity provider and let other sites know if the user has a session at that site.  In other words, it has the same information as proprietary solutions that already exist, except that it works across multiple identity providers.  It means that when you go to a new website, it doesn't have to ask you what your preferred services are, it can just look them up.  Note that this only tells the site that you have an account with Google or Yahoo or Facebook or Twitter, not what the…
Twister is interesting.  It's a decentralized "microblogging" system based on putting together existing protocols:  Bitcoin, distributed hash tables, and Bittorrent.  The most interesting part for me is using Bitcoin for user registration and spam control.  Federated systems handle this with federated trust, which is at least conceptually simple.  The Twister/Bitcoin mechanism looks intriguing though I don't know enough about Bitcoin to really comment.  Need to read further.