240 posts
  • Affiliate Level 1
  • Author Level 5
  • Collector Level 1
  • Top Monthly Author
+4 more
phpdude
says

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.

4948 posts Community Mod Building awesome stuff for your mobile devices!
  • Trendsetter
  • Weekly Top Seller
  • Elite Author
  • Author Level 8
+17 more
Enabled
Moderator
says

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! :D

821 posts We're a nice team!
  • Top Monthly Author
  • Weekly Top Seller
  • Elite Author
  • Author Level 8
+11 more
ThemeFocus
says

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.

734 posts
  • Beta Tester
  • 3 Years of Membership
  • Author Level 6
  • Affiliate Level 1
+2 more
billyf
says

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.

3007 posts
  • 5 Years of Membership
  • Affiliate Level 5
  • Author Level 9
  • Bundle Boss
+8 more
duotive
says


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.

17 posts
  • Author Level 5
  • Beta Tester
  • Exclusive Author
  • Bosnia and Herzegovina
+1 more
pixeldizajn
says

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

954 posts
  • Affiliate Level 1
  • Author Level 3
  • Beta Tester
  • Most Wanted Winner
+3 more
aleluja
says


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! :D

Well she wanted it!

Bye.

972 posts
  • Power Elite Author
  • 4 Years of Membership
  • Author Level 13
  • Trendsetter
+9 more
Dream-Theme
says

Always thought Twitter is stupid…

1482 posts
  • Envato Team
  • Author Level 6
  • Meetup Participant
  • Affiliate Level 5
+14 more
kailoon
Envato team
says

Byebye twitter widget.
+1
121 posts
  • Elite Author
  • Top Monthly Author
  • Weekly Top Seller
  • Trendsetter
+8 more
Themewich
says

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:

https://dev.twitter.com/apps

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:

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

Unless I’m missing something?

Andre

by
by
by
by
by
by