Twitter Retiring Old API- Remember to Update your Items

I was skeptical too, I thought the display requirements were only meant for the more high class sites and for TV, but according to this discussion with a Twitter employee, they say it’s for everything. https://dev.twitter.com/discussions/15327

Yes, the display requirements apply to all scenarios in which Tweets and Twitter content are shown

This means all kind of widgets will need to be adjusted to coincide with the guidelines, but it’s not really a massive deal because all the jQuery or other JS based plugins will break when they switch to v1.1 of the API.

phpdude said
I was skeptical too, I thought the display requirements were only meant for the more high class sites and for TV, but according to this discussion with a Twitter employee, they say it’s for everything. https://dev.twitter.com/discussions/15327

Yes, the display requirements apply to all scenarios in which Tweets and Twitter content are shown

This means all kind of widgets will need to be adjusted to coincide with the guidelines, but it’s not really a massive deal because all the jQuery or other JS based plugins will break when they switch to v1.1 of the API.

Yup, timeout infinite load loop!

Hi, you there use twitter api test link show correct? Here show : Bad Authentication data

I’m not make sure that 1.0 & 1.1 will all not support user_timeline.json get tweets.

activetofocus said
Hi, you there use twitter api test link show correct? Here show : Bad Authentication data https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=twitterapi&count=2 I’m not make sure that 1.0 & 1.1 will all not support user_timeline.json get tweets.

I personally think that the current changes (new API + display guidelines) seems to push people into using their own embedded timeline. After all, the display guidelines will somehow make your ‘custom timeline’ look 90% like theirs and there is no rate limit for their own timeline widget.

billyf said

activetofocus said
Hi, you there use twitter api test link show correct? Here show : Bad Authentication data https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=twitterapi&count=2 I’m not make sure that 1.0 & 1.1 will all not support user_timeline.json get tweets.

You need to generate OAuth signature before you can request for user_timeline. Considering those are public information, I’m not sure why are we forced to use OAuth for it. I personally think that the current changes (new API + display guidelines) seems to push people into using their own embedded timeline. After all, the display guidelines will somehow make your ‘custom timeline’ look 90% like theirs and there is no rate limit for their own timeline widget.

Byebye twitter widget.

This is just sad, their display requirements ruin any chance of creativity. Bye, bye Twitter widgets from us too.

Enabled said

Smartik said
Who need twitter? From 5 March Twitter Widget is not in my features list. Goodbye Twitter.

I just broke up with Twitter too… she’s still crying!

Well she wanted it!

Bye.

Always thought Twitter is stupid…

duotive said
Byebye twitter widget.

Still researching this, but it seems like usability is a little clunky for the Theme customer. If you create a custom twitter “widget”, the Theme customer still needs to create a new “application” on the twitter website:

Then copy and paste FIVE different pieces of information in the widget:

1. Twitter Application Consumer Key

2. Twitter Application Consumer Secret

3. Account Access Token

4. Account Access Token Secret

5. Twitter Feed Screen Name

I’m thinking it just might be easier to get rid of the any custom twitter widgets and just paste a twitter timeline in a text widget:

Unless I’m missing something?

Andre