How will LinqToTwitter be effected by Twitter API v1.1

Sep 8, 2012 at 3:32 PM

Will there be anything that we need to watch out for with the latest twitter news? How will these changes effect LinqToTwitter? It appears March 5, 2013 the old endpoints will no longer be available. 

Twitter API v1.1:
https://dev.twitter.com/blog/current-status-api-v1.1

News:
http://techcrunch.com/2012/09/05/twitter-officially-launches-v1-1-of-its-api-developers-have-until-march-5-2013-to-switch/

Coordinator
Sep 9, 2012 at 12:31 AM

Hi,

I'm currently doing the v1.1 cutover and am about halfway through.  The good news is that the developer experience appears to be largely unchanged. I'm still working though the API and will have more to say in a few days.  I'll pull it together and blog what my experience during the cutover was.

Joe

Sep 14, 2012 at 7:29 PM

How is the migration to v1.1 going?

Coordinator
Sep 15, 2012 at 12:08 AM

I did a check-in the other day with the bulk of the REST API.  Work has had me busy this week, so it's going slow, but I'll be back at it after punching through my current backlog. The good news is that everything I've seen so far is going well. Thanks for asking.

Joe

Sep 15, 2012 at 2:40 AM

hi,

@JoeMayo, i hope everything will be ok, can't hardly wait :-)

by the way, twitter says that they will cut support for RSS, XML and ATOM, is it LinqToTwitter affected by this? my understanding, twitter will only allow JSON as the returning format (CMIIW), may i know the strategy for this JSON things on your LinqToTwitter code?

Coordinator
Sep 15, 2012 at 3:02 AM

I converted LINQ to Twitter to full JSON a while ago.  The writing was on the wall as Twitter added new features to JSON payloads only.  Now I'm very glad I did because it's made the conversion to v1.1 much easier.

Joe