Dewald Pretorius wrote:
Raffi,
There appears to be ground for confusion here. I'm sure some folks are
still sending some API calls to twitter.com.
Could you please put up a page that explains which calls *must* go to
api.twitter.com, and after tomorrow won't work on twitter.com? And
vice versa, which calls must go to twitter.com, and won't work on
api.twitter.com.
Here is my understanding:
Right now, you might be able to access resources through api.twitter.com
that aren't part of the official public API. Starting tomorrow,
api.twitter.com will only implement the official, public API. If you
rely on resources that aren't in the official public API, and you are
accessing them through api.twitter.com, your program will probably stop
working tomorrow.
If you are only using the published API through api.twitter.com, or you
are accessing resources through the twitter.com domain, this change
doesn't affect you (AFAICT), but, you should change your code to use
http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the
base URI at your earliest convenience, as Twitter said a few months ago.
Since the OAuth resources are documented as being on twitter.com (not
api.twitter.com), you should be accessing them through twitter.com (not
api.twitter.com), even though you should be accessing the Twitter API
through api.twitter.com.
Correct?
- Brian (@BRIAN_____)
