Twitter API Upgrade

[Sachin Shende]

Steve et al,

We were hit by Twitter API upgrade blackout yesterday - https://dev.twitter.com/blog/api-v1-retirement-final-dates

Lot of code in Mezzanine Twitter app will have to be re-written due to this upgrade. I feel the new API has a lot of baggage. I have worked on search API using Twython but need to refine the code. Will be happy to re-write this and commit. Please let me know if you have any other ideas. 

Thanks,

Sachin

[Stephen McDonald]

Well that's disappointing.

I assume the Twython lib requires oauth keys and secrets defined? If so then we might as well use requests-oauthlib (http://docs.python-requests.org/en/latest/user/authentication/#oauth-1-authentication) which would mean the least code changes in Mezzanine, and would be more broadly useful in terms of new dependencies. 

With that in places, I imagine all we'll need to do is define new setting for the oauth keys/secrets, and update the api urls as well as the code that calls them. 

Does that actual data returned change?

--
You received this message because you are subscribed to the Google Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Stephen McDonald
http://jupo.org

[Stephen McDonald]

Also worth mentioning the mezzanine.twitter app almost seems redundant now given Twitter's own support for client-side widgets:

https://dev.twitter.com/docs/embedded-timelines

I guess the only case to be made for keeping mezzanine.twitter is that it gives you greater access to styling the feed. 

[Sachin Shende]

Thanks Steve. Yes, the actual data returned has changed too. Those changes are manageable though. 

Do you want me to change this and send it for your review?

Thanks

[Stephen McDonald]

That'd be awesome, thanks a lot for your help.

[Stephen McDonald]

Hi all,

Big thanks to Sachin who has done all the work in upgrading the mezzanine.twitter app to use their new API version which is now required. This has been merged in, so if this affects your project, please give it a test as soon as possible before the next release is made available which should be soon.

Please note that integration with Twitter's API now requires authentication, which means setting up a Twitter app with keys/secrets configured in Mezzanine settings via the admin interface for settings.

On Sat, Jun 8, 2013 at 10:43 PM, Sachin Shende <sachin...@gmail.com> wrote:

[Matt Mansour]

Just wanted to give a big thanks to Sachin as well. Your changes made my upgrade to the new Twitter API very easy. Much appreciated.

[Richard Ersek]

I'll second that - thanks Sachin!   I installed 1.4.8 and it looks like I need to get OAuth keys.   Is there anything specific needed for the callback URL or does that not matter in this case?

 

-Rich

 

[Richard Ersek]

Figured it out - I just used my own domain.