In general, our recommendation is to use api.twitter.com/1 from here
on out as we are beginning our transition of all our endpoints to the
versioned api namespace. We don't know exact dates, but at some point
we will deprecate accessing the API from twitter.com directly.
On Nov 26, 2009, at 1:10 AM, bang <bang...@gmail.com> wrote:
I found new APIs use api.twitter.com instead of twitter.com
in some lists APIs
http://api.twitter.com/1/twitterapi/team/members.xml
is the same as
http://twitter.com/1/twitterapi/team/members.xml
but some other lists API , for example
http://api.twitter.com/1/twitterapi/lists/subscriptions.xml is ok
but
http://twitter.com/1/twitterapi/lists/subscriptions.xml
is not found
this's a bug? this problem is very unconvient for me to develop my app
