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. :-)
Tweetdeck has announced something called deck.ly, which promises to let you tweet in more than 140 characters, something I welcome.
Beyond that the website is pure confusion.
1. Do I need to use Chrome to access this service, or can I get there from Firefox (the browser that I use all day every day)?
2. Is this a proprietary thing, i.e. what if one of their competitors would like to offer the same service. Do they have to create something completely incompatible, or can they interoperate in some way. In other words have they created yet-another silo (boo). Is this just an attempt to break out of the grip of Twitter, Inc or is it something bigger with a future beyond one vendor?
3. What if, god forbid, Twitter wanted to support this? What would Tweetdeck say to that?
I guess that's enough to begin with. Once we know the answers others may come to the surface.
One thing that it definitely is -- an awful name. Sickly pops to mind. Dickly. Deadly. For a short URL (presumably why they chose this name), "deck" seems pretty long. And the fact that it's the end of their product name pretty much nails the answer to #2. Even if they offer an API, it's hard to imagine their competitors signing up for a service that's named after another vendor's product.
PS: A personal note -- white text on a black background is really hard on my poor eyes. Have some pity!