i'm bound to forget this in about an hour. is this old/new versioned/not listed somewhere in the API docs?
On Feb 22, 2010, at 9:42 AM, Ryan Alford wrote: > Yes, those are the ones I am talking about. > > Ryan > > On Mon, Feb 22, 2010 at 12:41 PM, Raffi Krikorian <ra...@twitter.com> wrote: > hi ryan. > > yup - those are the original update methods, right? like > > http://twitter.com/statuses/update.xml > http://twitter.com/statuses/update.json > > we haven't set a deprecation date for those yet - but developers should plan > on it. please start to migrate to the api.twitter.com/1/ URLs. > > > On Mon, Feb 22, 2010 at 9:26 AM, Ryan Alford <ryanalford...@gmail.com> wrote: > Raffi, > > Just so you know, "http://twitter.com/statuses/update.format"; also works. > That's what I have been using in my app until today(moved to the versioning). > > Ryan > > > On Mon, Feb 22, 2010 at 12:23 PM, Raffi Krikorian <ra...@twitter.com> wrote: > yeah - please use the /1 URLs. if api.twitter.com works without /1, then > that's inadvertent, and we'll probably "fix" that. > > > On Mon, Feb 22, 2010 at 9:18 AM, Ryan Alford <ryanalford...@gmail.com> wrote: > I *believe* Twitter is moving to "versioning" the API(which is what the "/1/" > means..it's version 1). So I would use the URL with the "/1/", since the > other way be deprecated in the future. > > Ryan > > > On Mon, Feb 22, 2010 at 11:19 AM, Dmitri Snytkine <d.snytk...@gmail.com> > wrote: > Is there a difference between using > http://api.twitter.com/1/statuses/update.format > and > http://api.twitter.com/statuses/update.format (without the /1/)? > > > > > -- > Raffi Krikorian > Twitter Platform Team > http://twitter.com/raffi > > > > > -- > Raffi Krikorian > Twitter Platform Team > http://twitter.com/raffi >
