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.
"The protoblogger." - NY Times.
"The father of modern-day content distribution." - PC World.
"Dave was in a hurry. He had big ideas." -- Harvard.
"Dave Winer is one of the most important figures in the evolution of online media." -- Nieman Journalism Lab.
10 inventors of Internet technologies you may not have heard of. -- Royal Pingdom.
One of BusinessWeek's 25 Most Influential People on the Web.
"Helped popularize blogging, podcasting and RSS." - Time.
"The father of blogging and RSS." - BBC.
"RSS was born in 1997 out of the confluence of Dave Winer's 'Really Simple Syndication' technology, used to push out blog updates, and Netscape's 'Rich Site Summary', which allowed users to create custom Netscape home pages with regularly updated data flows." - Tim O'Reilly.
8/2/11: Who I Am.
My 40 most-recent links, ranked by number of clicks.
FYI: You're soaking in it. :-)
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:
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.