2winFactor said
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:

2winFactor said
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:

There are however some limitations, like limit of 180 requests per 15 minutes for an app. I have created single app for each of my theme, but it can still be a problem if theme is so popular and wide spread like those of yours…so maybe let customer choose to either use your app or give him instructions to create his own app.

PhantasiaAeterna said
There are however some limitations, like limit of 180 requests per 15 minutes for an app. I have created single app for each of my theme, but it can still be a problem if theme is so popular and wide spread like those of yours…so maybe let customer choose to either use your app or give him instructions to create his own app.

whooaaaa!! You crazy?! You are not allowed to give YOUR API INFO to the BUYERS!

It is against Twitter TOS.. How can you even think to do such thing? An experienced buyer could do anything he could want with your twitter account if you give him full oAuth access to your API

A while back, just after the switch to oAuth, I had an item on here that needed to use the Twitter API, and I used my own app tokens, and let the user approve my app when signing in. Needless to say my Twitter account was banned, and my Twitter App access was revoked, so yeah, don’t do that!

Since then, I’ve had to leave instructions for users to create their own Twitter App, and use those details, but it’s an extra step which is a pain, and I get a few (2-3 a month) from people who genuinely have issues setting up the app (as they are doing it for the first time, can be a bit confusing you know?).

Anyway, I highly doubt my next item will be Twitter related. I love the API still, and use it a lot for my own internal apps, but they’ve made it tricky for people to sell or open source projects based around it.

whooaaaa!! You crazy?! You are not allowed to give YOUR API INFO to the BUYERS!

It is against Twitter TOS.. How can you even think to do such thing? An experienced buyer could do anything he could want with your twitter account if you give him full oAuth access to your API

Indeed it is not advisable to distribute your Twitter APP Keys to your Theme Users but a Twitter Employee says you are allowed to distribute your Keys but on your own Responsibility and it is not outright prohibited in their TOS..! INSANE…..!!!!

PhantasiaAeterna said
There are however some limitations, like limit of 180 requests per 15 minutes for an app. I have created single app for each of my theme, but it can still be a problem if theme is so popular and wide spread like those of yours…so maybe let customer choose to either use your app or give him instructions to create his own app.

API limits are 180 requests per 15 mins, per app, per user so number of theme installations shouldn’t be a problem

Post Reply

<strong></strong> to make things bold
<em></em> to emphasize
<ul><li> or <ol><li> to make lists
<h3> or <h4> to make headings
<pre></pre> for code blocks
<code></code> for a few words of code
<a></a> for links
<img> to paste in an image (it'll need to be hosted somewhere else though)
<blockquote></blockquote> to quote somebody