K42B3

K42B3 does not currently provide support for this item.

7 comments found.

you can’t use quotation marks in your tweets with this, not a huge deal, but a window pops up and says, “incorrect signature”

hi andrewjtalcott,

thanks for the information I will look into the code and try to fix this.

best regards k42b3

Every time I go to use tweet commander it takes me to the OAuth Twitter authorize page, I have already given access to it, is there a way to make it so that it doesn’t need to grant access after the first time you allow access?

hi andrewjtalcott,

this is in the scope of twitter.com the twitter commander can not do anything about that. I think twitter has made that because they want that the user has everytime an application access the API the option either to grant or deny the request. But I agree with you they probably should add a checkbox like “Remember answer” so that you get redirected to the application.

best regards k42b3

@K42B3,

You are incorrect in your response to @andrewjtalcott re: repeated authorization. While I haven’t purchased your app nor do I have any plans to, it sounds like you are not storing the OAuth token and token secret upon authorization and using them on subsequent calls to the Twitter API .

When using OAuth for authentication, you need only authorize an app one time. Repeated accesses are authenticated with the users OAuth token and OAuth token secret which you are supposed to provide Twitter for authentication. These tokens are supposed to be stored and subsequently sent by your script to prevent these repeated requests for authorization.

Please read this link to learn more how to use OAuth.

hi digidave0205,

thx four your response. A good point to store the authorized tokens but tweet-commander works probably not in the way you think. To store authorized tokens we need a way to assign these tokens later to the user. So i.e. if we had a user table we could save these authorized tokens and re use them again but the authentication system of tweet-commander is complete based on twitter so you have to authorized everytime again.

In example if you login into twitter via tweet-commander the application gets an authroized token and token secret but if another user logs in he cant use this authorized token and token secret so he will create another pair. In the theoretically case I would store all these authroized tokens I have no way to assign them to the user if he comes back later because there is no way I can identify him. To wrap it up each user must allow in twitter the application tweet-commander therefor every user that uses this application will be redirected to twitter. If twitter has an option to remember an authorized application (like I mentioned in my post before) they could redirect you straight back to tweet-commander back. Therefor tweet-command can not do anything about it except of building an complete user system into the application but thats out of the scope of tweet-commander. If there are any ambiguities do not hesitate to contact me.

best regards k42b3

in regards to what @digidave0205 said, was wondering if you could fix this, if I get around to messing with it I will let you know.

@K42B3,

Let me make my point more clearly..

Why should I need to register my car each time I want to drive it.

hi digidave0205,

you need to open your car with a key every time you want drive it because else anybody can drive with it. The same applies to your twitter account you need to authenticate every time so that the application knows who you are.

best regards

Your logic makes no sense which is probably why you only have 4 sales. Use OAuth correctly and perhaps you’ll do better. Best regards

This project is dead…? :(

by
by
by
by
by
by