Posts from Dave Winer

The AVC Network

Disqus (a portfolio company of USV) has rolled out a really sweet analytics service as part of its "add ons" that were released a few weeks ago. You get the analytics as part of every add on package, including the $19/month Plus service.

There are four main parts of the analytics service; snapshot, activity, people, and network. It's the network tab that has me the most interested. I'm always curious where the most active AVC community members hang out when they are not on AVC. Since Disqus is first and foremost a commenting system, "hanging out" means commenting for the purposes of this post.

Here's the answer:

Disqus network

I'd like to see more than the top six. Ideally I'd like to see the top 25 or more. But this is a good start. Happily I call each of these bloggers a friend, and one of them is my wife. If we had a dinner party with this group, it would be a blast. I'd sit Dave Winer next to Mark Suster and Howard Lindzon just to make things interesting.

This suggests a whole new set of features for Disqus. If they know the communities with the greatest overlap with this community, they can and should build network tools so that readers of this blog are aware of what is going on across the network. If there's a great post/conversation going on at Suster's blog, we should know about that here at AVC and have a quick link to get there from here.

Fortunately the team at Disqus knows that. I'm not announcing any features here. But I am pointing out that communities like AVC don't exist in a vacuum and there is a network of communities out there and Disqus is powering most if not all of them. And so there's a lot Disqus can do to make the network come to life in powerful ways. I'm looking forward to watching them do just that.



#Web/Tech#Weblogs

Open APIs and Open Standards

As Dave Winer has been pointing out in recent weeks, there is something quite interesting happening in the blogging/microblogging world.

First WordPress allowed posting and reading wordpress blogs via the Twitter API.

Then yesterday our portfolio company Tumblr did the same.

John Borthwick has been advising companies for a while now to build APIs that mimic the Twitter API. His reasoning is that if your API look and feels similar to the Twitter API then third party developers will have an easier time adopting it and building to it. Makes sense to me.

But what WordPress and Tumblr have done is a step farther than mimicing the API. They have effectively usurped it for their own blogging platforms. In the case of Tumblr, they are even replicating key pieces of their functionality in it, as Marco describes:

The really cool thing – because our following models follow a lot of
the same principles, we’ve been able to take advantage of a ton of
native features:

  • Retweeting = Reblogging
  • Replying = Reblogging w/ commentary
  • Favoriting = Liking
  • “@david” = ”http://david.tumblr.com/”
  • Conversations = Reblogs

And as Dave Winer points out, this effectively creates a standard that third party clients can adopt. And Dave ends his post with this highly provocative thought:

If Facebook were to implement the Twitter API that would be it. We'd have another FTP or HTTP or RSS.

I'm still trying to wrap my head around all of this and the implications of it. And I'm not writing here in my capacity as an investor in Twitter and Tumblr or a board member of Twitter. I just think its fascinating and worthy of discussion in this community. So let's get on with it.

Reblog this post [with Zemanta]
#VC & Technology#Web/Tech#Weblogs