Twitter effectively killing JSONP too

This doesn't mean killing JSONP dead, it just means that you'll need a server-side script to generate oauth-authenticated URLs first.<p>This is what I do in one application right now, and it works really well, meaning that for the calls in question, the rate limit applies to the user's IP and not our server's.

The lesson is not "do not build on someone else's platform", but "be careful whose platform you build on". There have been signs for quite some time now that twitter was not particularly supportive of things built on them.

They "sunsetted" @Anywhere so they can focus on embedded tweets, a more focused attempt to provide badges/widgets for browsers. So really I doubt they want browser apps calling their API directly, but rather to use their embed timelines.<p>I realise that's a tiny subset of what's possible with the JSONP API, but that's my guess about why they won't support JSONP.<p>And, if they do shut it down, it sucks. I've run <a href="http://listoftweets.com" rel="nofollow">http://listoftweets.com</a> for several years and made various other Twitter mashups using their JSONP API.

I'm wondering (a) if people are going to switch to screen scraping as a way to avoid the new API restrictions, and (b) how much Twitter could do to thwart such attempts.<p>My (uneducated) guess is that it might play out like other DRM wars. Twitter could come up with new ways to scramble their HTML/CSS/JS to make it harder to automatically scrape... until scrapers evolved to deciper the new patterns, ad infinitum.

They will be killing a lot of third party plugin too, a good example would be the wordpress plugins, a lot of them use the jsonp stuff.<p>Seems weird to mee, but hey, anything to make money in the end I guess

Well, goodbye twitter widgets on lots of websites, I guess. (deviantART does a JSONP widget on user pages, lots of wordpress plugins do it, etc...)

Does this mean that "<a href="http://api.twitter.com/1/statuses/user_timeline/&#60;user&#62;.json" rel="nofollow">http://api.twitter.com/1/statuses/user_timeline/&#60;user&#6...</a> will be deprecated? Or is this talking about authentication?

Do all calls to the Twitter API require authentication now? It used to be that some calls (like search) did not require authentication, and I would assume those would still work with JSONP?

Good. JSONP is stupid anyway.