Engagement Programming: User ids are the correct key, not screen names
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...
View ArticleEngagement Programming: Follow leaders for great following leads
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...
View ArticleEngagement Programming: Leaders will point to your engagement targets
In yesterday’s post I recommended searching for the screen names of influential accounts as a way of getting high-quality leads for engagement. A related approach is to collect the timelines of key...
View ArticleEngagement Programming: Super simple rate limit programming
Rate limits are a constant concern when doing engagement programming with the REST API. I’ve settled on an incremental approach. Instead of building a rate accounting infrastructure that measures the...
View ArticleEngagement Programming: Best practices for collecting user account info
The Twitter API provides two requests for user account info: users/show and users/lookup. On the surface the difference between the two seems obvious. Users/lookup returns data on 100 accounts at a...
View Article
