For now, search.twitter.com will continue functioning as it does today -- you don't enter credentials of any kind to make use of it and all rate limiting is in respect to your IP address.
There is a future where the Search API will properly belong in the api.twitter.com domain, and at that time it will be subject to whatever authentication rules are in place when that transition happens. That might mean it doesn't require authorization of any kind. But it also might mean that for server-to-server operations it may require two-legged OAuth (OAuth without access tokens, meaning the "actor" in the request is your application, not a user using your application), or even full three-legged OAuth. Or one of the OAuth2 profiles. Or all three of these. That future is unclear, but the unification of the Search API and the standard Twitter REST API is a sure thing, with many benefits in store. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Mon, May 10, 2010 at 11:33 PM, sandeepcec <sandeep....@gmail.com> wrote: > As Twitter is going to stop basic Authentication. > > My question is Does Twitter also going to stop Twitter JSON API ???? > (http://search.twitter.com/search.json?q=<query>) > > Does it comes under basic Authentication module i am not clear about > it ???? >
