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.
8/2/11: Who I Am.
My 40 most-recent links, ranked by number of clicks.
FYI: You're soaking in it. :-)
I was writing this post when news of their API came in.
Postscript to yesterday's piece about Verizon and my Droid. I bit the bullet and ported the number to Google Voice. A little less than 24 hours later the porting is done, the Verizon account is closed, and the number maps to Google Voice, and through that to a contractless account with T-Mobile that's running on my Samsung Nexus S that I bought in April for my trip to Amsterdam. Whew!
It worked and I still have the old number. So everyone is happy, except maybe Ma Bell's nasty bitch of a grand-daughter, Verizon. Yeah, actually I think they like it when customers walk. Anyway...
I usually don't say this about people or companies, aware that I am that it's often the other way around. The one saying they don't get it is the one that don't. In this case I am absolutely sure that Google is the one.
They need an API with one call, one that posts a tweet to their service. So people can hook up Twitter clients to Google-Plus, so the hundred million active Twitter users can post to Google-Plus from the comfort of whatever tools they depend on.
Of course it isn't the hundred million that they need, it's the hundred thousand who do all the work on Twitter. The ones that can't be bothered with a service that doesn't have basic rudimentary API support.
Big companies like Google think they're doing us a favor by adding an API. That's because they think not so much like big companies, but like employees who work at big companies. If they really had the ego of a big company they would think like this. You, developer, your job is to make me rich. So get off your ass and write some apps that drive people to my service. Not just any people but the ones who make Twitter sing.
Anyway, when I saw they had an API I was clearing my schedule to hook my tools up to Google-Plus and finally start getting to work making them a success. Instead, I'll get back the work I'm supposed to be doing.
One more comment: They should just support RSS, and forget APIs to read publicly available content. All that's going to happen now is people are going to write apps that produce feeds from their API so they can hook into the reading tools that were written a hundred years ago, like the one Google itself has. What is it about BigCo's that keep them from paying any attention to things they didn't invent? Larry Page: they're wasting your money and your time.
I feel like Paul Krugman writing about economists. When will these supposed software people learn how software works.