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. :-)
Trying an experiment overnight when the traffic is low.
I'm redirecting from scripting.com to s3.scripting.com.
I'm using a code 302, non-permanent redirect, so if things break badly I can easily go back.
I'm wondering if I can switch over to S3 for static hosting. The only way to find out for sure is to try it and see what happens.
Update: The experiment didn't work. Too many redirects. I don't think Apache sites, even static ones, can be moved into S3 space. Not unless they never did any kind of redirecting to hold it together. This site has been around since the mid-90s. Too much history I'm afraid. :-(
I spent the last couple of days creating an installable scripting2.root, with a howto. That's the software I use to edit this weblog and produce all the feeds.
The sites are fully baked, meaning they can be hosted anywhere. It's set up to, by default, host sites on Amazon S3.
One of the things I tripped over while testing the release is some code I forgot I had written. It manages a file that's what I think of as JSONified RSS. It's the feed for Scripting News rendered as JSON.
My dream would be to have the Readability guys take a shot at this. Or Flipboard. Hmmm.
PS: The server you get with EC2-for-Poets will run scripting2.root just fine. The pieces are starting to fit together real nice.
Not sure what's new, I don't pay close attention. But the focus seems to be on Section I, paragraph 5, sub-E.
"You may not use Twitter Content or other data collected from end users of your Client to create or maintain a separate status update or social network database or service."
What this seems to mean is:
1. If your client touches the Twitter API, then any text or data the user enters into that app becomes Twitter Content.
2. You cannot use that data to form a new service. So there goes the idea of Twitter clients sharing info between each other using RSS. They should have done it a long time ago, now they would be able to fall back on that net (and that's why Twitter wouldn't be able to pull this string now).
3. You can't be half in and half out. Either you connect to Twitter, and they own you and your users, or you don't connect to Twitter.
I don't think there's really anything here that wasn't obviously coming before. I've said it many times, but I guess people don't read my posts, otherwise why are they surprised. This has been a long time coming.