You'll have to change clients, but you can obtain the required tokens
to do the same calls. Changing auth schemes shouldn't change what you
can get out of the API. Once you setup your user's app/ids the same
whitelist applies. I just finished my conversion yesterday and
everything's working the same.
I use this now:
Go up a directory from there to see samples.
On Aug 21, 8:47 am, Rushikesh Bhanage <rishibhan...@gmail.com> wrote:
> Hi there,
> I have a white-listed account, but the rate-limit has decreased from 20k
> before 5 days to 12k right now. Initially I thought that this might be due
> to twitter running over-capacity because I was busy in finishing part of app
> to launch it in two days. But i just read one mail from Justin who is having
> same problem, now I realized that this cut off might be due to basic auth. I
> was also aware about the basic oauth shutting down, but didn't click the
> We can switch to Oauth, but here are some doubts:
> 1. *What my app does*? -> in my app, when any twitter user enters his name-
> we crawl his data thru userstatus method, then we crawl his all the
> followers and show him his real followers.
> For this I am using My Twitter Library from Andres Scheffer, to which I
> pass my white listed account user name and password to get all the data. *Now
> which Oauth library should I prefer that will meet my requirement?*
> 2. *How Oauth is going to work*? -> I am doubtful that how Oauth is going to
> work in my case, until now any user can enter his user name and was able to
> get his result. now will I have to take Oauth from each searched user to
> show his result?
> If it is so how can I use my white listed account log ins to get 20k calls.
> Please clear my doubts.
> Thank you in advance.