Sustaining an effective engagement campaign can take a surprising amount of work. You could limit yourself to following the leads from the data you collect, but following without interacting first will get you a very low follow-back ratio. More importantly, if you follow and then forget people, they may follow back, but they’ll soon forget you. A high number of followers who don’t reply to, mention or retweet your account are of no value. True engagement is long-term and repetitive.
Controlling a local database is vital for collecting tweets and users from the Twitter API. Once this is accomplished, you no longer have to worry about rate limits, API reliability or speed of access. I do most of my work with MySQL, but any server-based database can be used—even a flat file in CSV format is a viable solution for minimal storage needs.
Successful Twitter engagement is generally measured with the simple goal of gaining a high follower count, but true engagement doesn’t end with a follow-back—that is just the beginning. What you really need for success on Twitter is an ongoing conversation with like-minded individuals, folks who will provide informed feedback on your tweets, introduce you to their friends on Twitter who share your opinions and help spread your messages. This series of articles on engagement programming will show you how to use Twitter API 1.1 to move from simply following to truly engaging on Twitter.
Twitter has just announced the availability of custom timelines, a brand new type of timelime that allows developers to have more control regarding organization and delivery of Tweets on the Twitter platform. Twitter has also announced the launch of the Custom Timelines API which is in beta and available to a small group of developers selected and approved by Twitter.
As companies, organizations and professionals become more and more interconnected via social networks such as Twitter, LinkedIn and Facebook, a new trend is beginning to emerge—social network data visualization. So let’s make a data visualization of our own.
There are over 1,000 social APIs in the ProgrammableWeb directory. The big names in that list, Facebook, Google Plus, LinkedIn and Twitter, are also amongst the most popular public APIs overall. Since other API providers look to these leaders for examples in engaging with developers, I thought it would be useful to see how each uses a common communications medium. That’s right, how do the social APIs use social media themselves?
Sometimes what is happening now is not as important as what happened then. I am speaking of the past and how it can help you piece events together. This what makes Gnip’s newest Twitter search API so powerful.
A new Facebook Keyword Insights API has been made available to a select range of media partners in the United States, allowing registered developers to create finer-grain, real-time data analysis of popular reactions to the latest news, sport and pop culture stories.
You are a major brand wanting to advertise. Do you: A) hire an advertising agency and pay big bucks for photo shoots, or B) crowdsource images from your fan base for free? The Olapic API integrates answer B into other apps.