[twitter-dev] verify_credentials returning the wrong user id

[Scott Aikin]

I've encountered a strange problem where sometimes verify_credentials
gives me the wrong user id.  In these cases the number is usually very
large and is different each time.  All the other user details are
correct.  How can this be?

[twitter-dev] Re: Showing Twitter profile information on OAuth sites - rate limit problem

[Scott Aikin]

Thanks Vincent! I've applied to be on the whitelist.

[twitter-dev] Re: Showing Twitter profile information on OAuth sites - rate limit problem

[Scott Aikin]

So it seems the only scalable solution is to cache the data and update
once a day using verify_credentials.  Thoughts?

[twitter-dev] Showing Twitter profile information on OAuth sites - rate limit problem

[Scott Aikin]

I've got an OAuth site that lets people register through Twitter to
create a profile and post to my site.  When you see comments or posts
by these users I show their Twitter profile information and have been
retrieving it with users/show.  The problem is that I can only show
this information 150 times each hour which quickly runs out.  What is
the best-practices method for accomplishing this?  Do I need to cache
their profile information and update it via my crontab?  I like the
real-time nature of my current solution, but with the 150 limit it's
just not going to work.  Any suggestions?

[twitter-dev] Re: Updating the APIs authentication limiting policy

[Scott Aikin]

Jim,

What you're suggesting is basically what they offer with OAuth.  Apps
are given a token to represent logins and a secret key to represent
passwords for their authenticated users.  Both are very long and
impossible to guess.  This mechanism works very well and basically
corrects all the issues with collecting actual logins and passwords
from users.

Scott