Adam Green
Twitter API Consultant
adam@140dev.com
781-879-2960
@140dev

Twitter is spending more money on API dev support

November 21, 2013

I’ve been seeing a definite trend towards more and more Twitter staff responding to questions on the developer mailing lists. This is another in a series of positive signs for the future of the API. What I especially like is an apparent specialization by support staff, with some people seemingly assigned to specific areas of […]

Read the full article →

Engagement Programming: Follow leaders for great following leads

November 21, 2013

A lot of my engagement programming for clients has involved finding good leads for them to build relationships with and gain as followers. Obviously, the search API is a good place to start, but just searching for keywords that match your engagement interests is not the best approach. For example, if I wanted to find […]

Read the full article →

Engagement Programming: User ids are the correct key, not screen names

November 20, 2013

When you start programming with the Twitter API, the natural tendency is to identify users in your database and code by their screen name. It seems right, since that is how you identify them when using Twitter. I used to do that too until I found out that users in some communities change their screen […]

Read the full article →

New SSL Certificates are not a problem for anyone using the 140dev code

November 20, 2013

Twitter posted a notice today about the need for new SSL certificates: At the end of 2013, all Browsers and Certificate Authorities will no longer support 1024 bits RSA certificates to be compliant to National Institute of Standards and Technology (NIST) guidelines [1]. The SSL certificate currently used on api.twitter.com is signed with the older […]

Read the full article →

3rd party API devs are a valuable resource now

November 11, 2013

Before the IPO I predicted that devs would be viewed as an asset, not just a burden. That change is happening right on schedule. Check out this NY Times article. The money quote: Twitter is counting on millions of websites to link to the service and encouraging legions of independent developers to find creative new […]

Read the full article →

Kindle version of Twitter API book is now available on Amazon

October 28, 2013

We converted the Twitter API Engagement Programming book to Kindle version last week, and it is now available in Amazon stores all over the world. If you don’t own a Kindle, Amazon provides a free reader app for Windows, Mac, and all major mobile devices: iPad, iPhone, Android, etc. http://www.amazon.com/gp/feature.html?docId=1000493771 This is the first Kindle […]

Read the full article →

5 Reasons the Twitter API will Survive the IPO

October 15, 2013

To say that the relationship between Twitter’s management and its API developer community has been rocky over the last couple of years would be an understatement, so it isn’t surprising that some developers and tech bloggers have speculated that after the Twitter IPO access to the API will be removed or severely restricted. I can […]

Read the full article →

My new book on Twitter API Engagement Programming

October 2, 2013

I’ve been building custom Twitter engagement systems for clients since 2009, and now I’ve combined all of my favorite techniques and tools into a new book available on Amazon: amazon.com/dp/0989875806 Just as with my 140dev Twitter Framework code and my ebooks on topics like OAuth, the code in this book uses PHP and MySQL. It […]

Read the full article →

Converting the 140dev Twitter Framework to use OAuth and API 1.1

April 3, 2013

Twitter has announced that they will be turning off basic authentication for the Streaming API on May 7th. I’m preparing a new version of the 140dev Framework to use OAuth now, and will have it posted tomorrow. That will be good for new users of this code, but if you already have the code in […]

Read the full article →

Twitter API Ebook: Javascript Programming for Twitter API 1.1

February 6, 2013

Javascript programming for Twitter changes dramatically with Twitter API version 1.1. The requirement to use OAuth with every API request means that you can no longer call the API directly from Javascript. Instead you have to rebuild all your Javascript code to proxy your requests through your own server. I know that a lot of […]

Read the full article →

Most common Twitter OAuth programming errors

January 26, 2013

My Twitter OAuth ebook has been out for 2 weeks now, and I’ve had a chance to help a lot of people get over the hump of running their first OAuth code. I’ve collected a list of the most common problems they have: No callback URL When you create an app, Twitter has an input […]

Read the full article →

New Twitter API Console tool

January 22, 2013

My Twitter OAuth ebook closes with the source code for an API Console application. This app got such a favorable response that I decided to enhance it and put it out as a free tool. I have found this to be an invaluable debugging aid when testing an API request. It lets you enter just […]

Read the full article →