About the author
Dave Winer, 56, is a visiting scholar at NYU's Arthur L. Carter Journalism Institute and editor of the Scripting News weblog. He pioneered the development of weblogs, syndication (RSS), podcasting, outlining, and web content management software; former contributing editor at Wired Magazine, research fellow at Harvard Law School, entrepreneur, and investor in web media companies. A native New Yorker, he received a Master's in Computer Science from the University of Wisconsin, a Bachelor's in Mathematics from Tulane University and currently lives in New York City.
Contact meMy sitesRecent storiesRecent linksMy bike
CalendarWarning!
Using DNS as a thin ID system 
Just thinking out loud here.
Suppose a user had control of a name that can be looked up through DNS.
Something like: dave.me or dave.easy.com, for example.
The former would be done through a registrar, the latter by a web service.
Suppose in both cases the user could define a file whose name would only be known to him. That's the password. When you sign in you'd enter the domain and the name of the file where username and password are requested.
Then the site requesting a validated ID would make this request:
http://username/password
If what came back is a 404, you're not authorized.
If a 200 came back -- you're in.
The body of the request could be something like a feed or an OPML file with info about the person. Basic stuff that any authenticated site is allowed to have.
Seems that's about as thin as an ID system can get.
And there's nothing innovative about it. We just need something like this that's quick easy for users to set up, with a name they're likely to trust.
