Geeks With Blogs

News
Joe Mayo

Hello Twitter API v1.1! Actually, Twitter API v1.1 has been around since September 2012. That’s when Twitter deprecated v1.0. Yesterday, Twitter shut down v1.0. You can read more details of yesterday’s events in on the Twitter API blog at API v1 Retirement is Complete - Use API v1.1.

Soon after Twitter API v1.1 was available, LINQ to Twitter upgraded to Twitter API v1.1 and changed its version from 2.0 to 2.1. You can download the latest version of LINQ to Twitter, which is v2.1.06 as I write this, and have full support for Twitter API v1.1.

Here’s a summary of important changes:

  • Rate Limits apply per API, as opposed to every API call. Statistically, this works out to a better rate limit overall, but it also means that you might need to adjust your design on how it scales to match the new policies. You can get rate limits with a HelpType.RateLimits query.
  • Json is now the only available response format. Generally, this doesn’t change your code because LINQ to Twitter deserializes most queries into entities. However, if you use Streaming, Raw commands/queries, or reading the TwitterContext.RawResults property, and you were working with XML, you’ll need to deserialize Json instead. The good news is that your application performs and scales better because queries and commands execute more quickly and use less bandwidth.
  • You must authenticate for all API calls. I know this is painful if you’ve used Search or another unauthenticated API. The good news is that LINQ to Twitter has extensive support for all Twitter OAuth options, so you don’t have to write your own OAuth code.
  • Search merged with the main API and is more consistent. LINQ to Twitter’s Search option also changed extensively. Primarily, search results and Status entities, which are the same type as Status query results. Though it requires a code change, it adds consistency to the API and improves the development experience.

As  the Twitter API matures and moves forward, so will LINQ to Twitter. Thanks to all the people who have contributed code, submitted pull requests, and made constructive changes over the years.

@JoeMayo

Posted on Wednesday, June 12, 2013 9:22 AM | Back to top

Copyright © Joe Mayo | Powered by: GeeksWithBlogs.net