Skip to main content

Joining @twitterapi as a Developer Advocate

On this nice sunny day I'm happy to announce that I will be joining the Twitter Platform team as a Developer Advocate. This is especially exciting for me as I have been thinking about developer communities a lot recently and can now officially start implementing some of my Unicorn Theories.



I will also be acting as a voice representing the third-party community within the company and will be looking into pushing a few projects out the door. High on my priority list are: open sourcing Twitter for Android, increasing rate limits to 1500 requests/hour, launching a cleaner, simpler version 2 of the API, and opening Annotations to a wider audience.

As I start implementing Unicorn Metrics I will be keeping a birds eye out for potential additions to the advocate team. If you are interested solving hard problems be sure to check out #jointheflock. All new employees get an awesome Twitter shirt!

Stay tuned for news on Chirp 2 (Trust me! You are going to love it!), and be sure to to enjoy this beautiful April day.

Note: This page was posted for April Fool's Day - 2011

Comments

  1. Wait, are you saying Annotations *DO* still exist?

    I.. oh.. date.. *sigh* You update so rarely it took me a whole day to receive this in my feed reader.

    That makes me sad.

    ReplyDelete
  2. Annotations *do* still exist. I have then enabled on my account but I haven't used them in ages.

    Do you use Google Reader? Or something that is pubsubhubbub enabled? Those should be instant.

    ReplyDelete
  3. Wait, are you saying Annotations *DO* still exist?

    I.. oh.. date.. *sigh* You update so rarely it took me a whole day to receive this in my feed reader.

    That makes me sad.

    ReplyDelete

Post a Comment

Popular posts from this blog

CloudSense: the Future of Advertising

With the whole cloud taking off and more and more services switching to a push it into the cloud, leave it there until you need it, and pull it out model. I can only imagine what will be switching to this model soon. Oh wait. I can imagine.



Advertising!


Reading an article about how Avril Lavigne is supposed to have a $2 million check "appear" in her mailbox because of the absurd number of streams her videos get from YouTube got me thinking about creator compensation. The problem Avril is having is, a) Google wants to keep the money, and b) Google is having trouble figuring out how to monetize video streams. But on a grander scale it is whoever puts the ads on the page that gets the money not the content creator.

Little known @Twitter and @TwitterAPI tips and tricks

Be sure to comeback as new tips and tricks get added. If you know of anything I missed be sure to let me know.

Static URL for profile images based on screen_name:

https://api.twitter.com/1/users/profile_image/abraham

* This performs a http redirect to the actual profile image URL. Currently https redirects to http. You can also add "?size={mini | bigger | normal}" to get specific sizes.

Redirect to profile based on user_id:

https://twitter.com/account/redirect_by_id?id=9436992

In_reply_to_status_id mentions:

https://api.twitter.com/1/statuses/update.json?status=reply+to+@abraham&in_reply_to_status_id=12410413197

* In the web interface new mentions are only replies if they start with @screen_name. By pushing @screen_name further along in the string your followers who do not follow @screen_name will still see the status.

Profile image sizes:

http://a3.twimg.com/profile_images/54160223/chart-black-small.png

* By default you get the original image size you can add _mini, _normal, and …

Installing Storytlr the lifestreaming platform

"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."

I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.

Assumptions:
LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started!
Get the code: wget http://storytlr.googlecode.com/files/storytlr-0.9.2.tgz tar -xvzf storytlr-0.9.2.tgzYou can find out the latest stable release on Storytlr's downloads page.

Import the database:
Within protected/install is database.sql. Import this into your empt…