The direction you'll want to be heading is letting the users allow
your app access once. You can then store the user's oAuth token and
oAuth token secret with their account. (instead of their username and
password) These won't change unless the user revokes your website's
access.
jarón
On Feb 1,
My app offers users the feature to see their tweets, retweeted (using
retweets_of_me - http://dev.twitter.com/doc/get/statuses/retweets_of_me).
However, I would also like to show how many times a particular tweet
has been retweeted, but the response does not offer that data.
I could call
Ok, thanks! I'm going to try that.
jarón
On 12 dec, 20:14, Tom van der Woerdt i...@tvdw.eu wrote:
The best way is to urlencode() the key and secret separately, and then
separating them with a space.
Tom
On 12/12/10 8:07 PM, jaronbarends wrote:
I have a webapp in php without any database
I have a webapp in php without any database associated with it. I'm
just saving the user's (encrypted) oAuth token and token secret in two
separate cookies. Now I want to build in multi-user support, and I'm
wondering what would be the best way to store the multiple tokens and
secrets.
My idea is
You can go further than making a reasonable assumption. If you hover
over the link back to your app, you'll see it looks something like
this: http://yourapp.com/callbackurl?denied=q3vuR41XYa.
So, Twitter sends a get-var called denied to your callback url. If
you check for the presence of that
don't refers to look and feel, not to button, so don't is
correct.
On Sep 29, 2:45 am, Mike under619ta...@gmail.com wrote:
Under Users login signup Custom Connect with Twitter Button it
reads:
If the default look and feel of the Connect with Twitter button
don't meet your needs, @Anywhere
When a user denies your app access, it says something like you denied
YourAppName access... The text YourAppName is a link, and when the
users clicks that, he gets redirected to your callback url, with an
additional parameter denied=someLongVariable.
So you can catch this scenario easily by
I just spent some time figuring out why I was getting a 401 -
Unauthorized error when trying to post tweets from an @anywhere
tweetBox. Turns out I had forgotten to check the Read Write radio
button in my app settings. (And it even says Note: @Anywhere
applications require read write access.)
Hi, I'm using the @anywhere tweetbox, and I am confused by the
revoking / re-granting access is handled. This is the scenario:
0) I type a tweet in the @anywhere tweetbox and hit Tweet
1) In the popup screen, I allow the app to connect to my account
2) I post a tweet. All is well.
3) I revoke my
And as an addition to what D. Smith said: you're probably storing your
users' token and token_secret somewhere. So if you do have a tokens
are present, you know they have granted access before. Also, you can
check the message in the headers. Twitter sends a 401 when access has
been revoked, and
Twitter also sends an error message in the response. These errors are
a quite descriptive, but afaik they're not fixed and could change in
the future. In my app I'm currently catching and handling a few of
these in a special way; with others I'm showing a general error
message. To be able to
Yes, this would be very cool. Any ideas on when this would be rolled
out?
1) It would be nice to have the profile_image_url in it as well. I can
imagine a lot of nice visual enhancements with that.
2) +1 for making it optional. A lot of people are suggesting
additional stuff, so maybe it would
Twitter uses this error not only for stuff that you would excpet to be
forbidden, but als for other actions that are probably unintended.
Other examples are favoriting a tweet you already favorited, trying to
follow a user you're already following, etc. The error is usually also
accompanied by an
@Dave
Thanks for your suggestion. I do indeed have a mysql, but haven't seen
the need to implement it in my app (http://twimply.com) since it
basicly only offers an alternative web interface for using twitter.
The only mentioned using a database as a possible solution: creating a
desktop app
,
can it?
On Apr 25, 4:49 am, jaronbarends jaronbare...@gmail.com wrote: I
moved my web based app from ba...
This issue has discussed in this group before here:
https://groups.google.com/group/twitter-development-talk/browse_threa...
Being a frontend developer, I may have misunderstood
I moved my web based app from basic auth to oAuth just last week. I
subsequently got several pleas from Chinese users to put the old
version back up, as they could no longer use my app, since access to
Twitter.com is blocked in China.
This issue has discussed in this group before here:
16 matches
Mail list logo
