Comments on: Developers, It’s Time to Open Up Twitter’s API

By: Jesse Stay

Jesse Stay — Thu, 31 Dec 2009 01:28:18 +0000

Robin, be sure to see some of the conversations in the Google Group I set
up. That will help you understand a little further my thoughts on this.
This subject has been discussed before. The idea is to create an open
source gateway that would be simple for anyone to install. Then, as more
adopted we could start to establish standards around it. So long as Twitter
is in control of the Twitter client though they set the standard.

By: Robin Millette

Robin Millette — Wed, 30 Dec 2009 23:50:56 +0000

Did you read that wiki page? It was done following a sesion at a recent StatusCamp. So yes, it is StatusNet oriented, but it also points to a bunch of other ressources/protocols.

I just don't understand what you mean by Open API I guess. You expect the backend code to be opensourced? But that has to be tied to the actual application. There could be a php lib shared by both WordPress and StatusNet I guess, and maybe that will happen. But there will need to be one in Python, Java, Ruby, etc.

I see no problem in reusing the method names as they're currently implemented. Copying the documentation is another manner, but that can be rewritten.

Maybe http://groups.google.com/group/twitter-developm... will eventually have an answer.

By: Jesse Stay

Jesse Stay — Wed, 30 Dec 2009 22:17:50 +0000

Robin, OpenMicroblogging is a Federation protocol, not Twitter protocol.
There's nothing just strictly focused on Twitter right now.

By: Robin Millette

Robin Millette — Wed, 30 Dec 2009 16:04:37 +0000

http://status.net/wiki/OpenMicroblogging_and_Fe... shows some progress.

By: Jesse Stay

Jesse Stay — Tue, 22 Dec 2009 06:05:25 +0000

Dave, it's still there, but the focus for openmicroblogging.org is around
federation, not Twitter-like syntax. There is code in Laconi.ca that does
this, but I think what would be more useful is a gateway that serves as a
middleman in all this. If we could build a gateway that takes
RSS/Atom/ActivityStrea.ms as input, and outputs in a Twitter-client
compatible format, we could then start to set standards around the export
format, especially as more people adopt this. The goal would to make it as
easy as possible for anyone to adopt, then, when the people are in control,
we could add additional layers and standards for the Twitter
client-compatible side rather than Twitter controlling that process. The
idea is to get it out of the hands of one company and into the hands of
many.

Of course, I'd love to see Twitter involved in this too and joining this
effort (as would I Facebook). I think the more we can get the developers
and consumers controlling these APIs, the better. The more companies
involved in this the better. Hopefully that makes sense.

By: David Recordon

David Recordon — Tue, 22 Dec 2009 05:57:48 +0000

Whatever happened to http://openmicroblogging.org/?

By: MikeGrace

MikeGrace — Sun, 20 Dec 2009 06:04:18 +0000

Look forward to the discussion.