TIGblogs TIG | TIGblogs GROUP TIGBLOGS LOGIN SIGNUP
Canada's World
Canada's World TIGblog is part of a movement to get people thinking about Canada’s role in the world in a new more active and more constructive way. Below are posts from several amazing bloggers from diverse backgrounds who write about any and all international issues, examined through the lens of Canada’s global interest and responsibility. Unfortunately, their bylines don't appear here but you can find more information about our authors by visiting our Wordpress homepage at canadasworld.wordpress.com.



CWBloggers   CWBloggers Canada's World's TIGblog
Canada's World's profile

Post and Read via Twitter API


The other day I talked about micro-blogging and mega-blogging and shared my view that new forms of social media, including micro-blogging, are complementary to blogging. We’ve seen ongoing growth at WordPress.com as people started using Twitter, and we expect that to continue.

Of course one of the coolest things about Twitter right now is the client applications, particularly the mobile/iPhone ones. I use Tweetie 2 on my iPhone every day. Wouldn’t it be cool if you could get all your blog subscriptions and post to your WordPress.com blog from apps like Tweetie? Well here’s an early Christmas present…

We’ve enabled posting to and reading of WordPress.com blogs via the Twitter API. Any app that allows you to set a custom API URL will work. This project came out of our Quebec meetup and was developed by Team 55 (Andy, Terry, and Raphael).

For this walkthrough we’ll use Tweetie 2. To get started, launch Tweetie 2 and click the “Accounts” button. Then press the “+” button to add your WordPress.com account. Enter your WordPress.com username and password, and click on the gear icon under the password field.

For API Root, enter: https://twitter-api.wordpress.com/ and then click the Add Account button. (No search API… yet!) Save this account and after your information is verified you can start posting to your WordPress.com blog from Tweetie 2. (There’s more detailed info about setting up your WordPress.com profile to work with the Twitter API in our Support doc.)

Here’s what it looks like when I read WordPress.com blogs I’ve subscribed to in Tweetie.

You can write a status update and post to your WordPress.com blog and also have it displayed in the blog reading view.

If you’ve enabled geotagging for your posts, the geolocation data gets exposed as well. You can change what blog the posts go to under your profile.

APIs are Biz Dev 2.0, as Caterina Fake put it, our ability to connect Tweetie 2 to WordPress.com proves this out. We didn’t have to talk to Loren Brichter because he built custom API support into Tweetie 2 — thanks Loren! (As an aside, I’d love to see custom API support added to TweetDeck and Seesmic, my two favorite desktop Twitter clients.)

There are still some rough spots around the edges but the core posting and reading bits of the API are solid and the rest is coming soon. I see the Twitter API as one of the new de facto standards that as many applications should support as possible. (Amazon S3 API too, why don’t all cloud storage providers use that?) We’ll be open sourcing the server as a WordPress MU plugin, so that other people can take advantage of our work and benefit their readers and communities.


December 12, 2009 | 1:12 AM Comments  0 comments

Tags:
You must be logged in to add tags.



Owner
This Group TIGBlog is owned by: Roberta Yeo.

Membership
Canada's World
Reilly Yeo

You must be logged in to join this group TIGblog.

Latest Posts
Editor’s Note:...
Editor’s Note:...
McChrystal And...
Is the BP Fiasco...
The Vuvuzela Comes To...

Monthly Archive
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
November 2008
December 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009
August 2009
September 2009
October 2009
November 2009
December 2009
January 2010
February 2010
March 2010
April 2010
May 2010
June 2010
July 2010
August 2010

Change Language



49280 views
Important Disclaimer