240 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 1+ items on Envato Market
  • Became a Top 20 Author of the Month
+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.

4947 posts Community Mod Building awesome stuff for your mobile devices!
  • Had an item that was trending
  • Had an item that became a weekly top seller
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
+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!
  • Became a Top 20 Author of the Month
  • Had an item that became a weekly top seller
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
+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.

724 posts
  • Has been part of the Envato Community for over 3 years
  • Has sold $40,000+ on Envato Market
  • Has referred 1+ members
  • Sells items exclusively on Envato Market
+1 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
  • Has been part of the Envato Community for over 5 years
  • Has referred 200+ members
  • Has sold $250,000+ on Envato Market
  • Had an item featured in an Envato Bundle
+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
  • Has sold $10,000+ on Envato Market
  • Has been a beta tester for an Envato feature
  • Sells items exclusively on Envato Market
  • Located in 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
  • Has referred 1+ members
  • Has sold $1,000+ on Envato Market
  • Has been a beta tester for an Envato feature
  • Won a Most Wanted contest
+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.

968 posts
  • Power Elite Author: Sold more than $1M on Envato Market
  • Has been part of the Envato Community for over 4 years
  • Has sold $2M+ on Envato Market
  • Had an item that was trending
+9 more
Dream-Theme
says

Always thought Twitter is stupid…

1478 posts
  • Member of the Envato Team
  • Has sold $40,000+ on Envato Market
  • Attended one of our Meetups around the world
  • Has referred 200+ members
+14 more
kailoon
Envato team
says

Byebye twitter widget.
+1
121 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Became a Top 20 Author of the Month
  • Had an item that became a weekly top seller
  • Had an item that was trending
+8 more
2winFactor
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