StatusNet for Twitter developers
I'm Zach Copley (@zach) the developer relations manager at StatusNet. I'd like to take a few minutes to reach out to developers of third party clients and services in the Twitter ecosystem.
By now you've probably heard that Twitter is in the process of acquiring and developing its own line of Twitter clients. It's still up in the air as to what this will mean going forward for the clients and services built upon Twitter's API, but it's clear that this change will have an effect on most if not all applications that interact with Twitter.
There has never been a better time for the micro-blogging developer community to diversify by adding support for other services -- especially StatusNet.
A Little About StatusNet
If you're not already familiar with StatusNet, we're an Open Source micro-blogging platform similar to Twitter. But we're not just a Twitter knock-off: while StatusNet has similar features to Twitter we also have additional functionality, including groups, media attachments, private instances and federation. StatusNet is fun and interesting for developers to work with!
Some key points:
- StatusNet is open -- we're rooted in Open Web technologies and have pioneered the development of the OStatus protocol.
- We have an established user-base -- there are roughly 1.5M users on tens of thousands of sites worldwide.
- We play well with others -- Many people and brands (shitmydadsays.com and mozilla.status.net, for example) use their own StatusNet installs to run focused communities and to push status updates to other services.
- We're Enterprise-friendly -- StatusNet is increasingly being used internally by large corporations, such as Motorola.
An easy transition for Twitter developers
StatusNet sites all have a built-in Twitter-style API. For developers who are familiar with Twitter, it's pretty easy to get started with StatusNet's API. Many applications have even been converted to work with StatusNet by simply doing a string replace on the root of the API URLs (replacing "twitter.com" with "statusnet.site/api"). We support most of Twitter's core API, but also have some additional methods to support unique StatusNet functionality such as groups and private instances. We also support a slew of other ways for getting data in and out of StatusNet, such as OStatus, XMPP, FOAF, RDFa, microformats and more.
Enterprise Micro-blogging Clients
The enterprise market is mostly untapped by independent client developers. There's a great opportunity for developers to provide clients and services that work well with private StatusNet instances, and instances running behind the firewall. There's also a lot of interest in branded, white-label clients. It's a huge potential source of income for developers, and we'd like to help you connect with these potential customers.
Documentation for our API is located on our wiki:
Our developer mailing list is here:
StatusNet (@evan, @rejon and I) will be attending Chirp, the Twitter developer conference next week, and we'd love to talk to you about adapting your client or service to work with StatusNet. We look forward to meeting with you and answering any questions you have about StatusNet and our API, as well as brainstorming ways to work with us. In the meantime, If you have any questions or there's any way I can help get you started using or developing for StastuNet, feel free to send me email: firstname.lastname@example.org.