Click here to show or hide the menubar.
Thread started by Dave Winer on Thursday, May 09, 2013.

Blogging 2.0

I wrote a piece in August 2012 which I posted on Medium entitled We Could Make History, in which I proposed that we get together and create a new API to connect authoring tools to publishing environments.

At the time I thought it was a long shot, but worth putting it out there in case anyone was listening at Medium, or elsewhere. That's why I made it openly. And why I put the post on Medium.

Today I'm writing this post on my own blogging platform, which is more or less some scaffolding I put together to hook my outliner up to the web, so I could publish, before we had something real that others could use.

Now I can make a more concrete proposal because Fargo is visible, people can better imagine what I'm talking about.

1. I don't like the idea of writing something to have it visible in only one place.

2. Sometimes I find that a comment I wrote in one place is really a blog post, but why should it stop being a comment?

3. Copy/paste is an awful synch protocol. It's 2013. We can do better! In fact we live in a time of great progress in sychronization, thanks to Dropbox. Publishing should make the leap into the future as well.

4. Software now runs in the browser, written in JavaScript. It's indistinguishable from desktop software. So any protocol we come up with must work equally well with JS apps running in the browser.

5. Meanwhile there are a number of projects underway to bring blogging up to date. But they're doing it without APIs and without feeds. Why? That's not really progress.

6. We were able to hook up Fargo to WordPress, largely to show what's possible. But we had to set up a proxy server so that our JS app running in the browser could call their server. This is a waste of resources and does not scale.

7. We will have a for-real CMS running on a server. It will do things that are new, that none of the other publishing platforms do. But there will still be things they do that we don't. APIs are needed. But I'd prefer to work with others to come up with the API, rather than do both ends myself. If we do it that way we get there sooner, better.

8. I'm pretty sure there will be APIs here. But I'd rather there just be one. We had that worked out pretty well in Blogging 1.0. But let's do it even better in 2.0.

9. Who wants to go first? :-)

XML