Admittedly, a very odd condition and a side effect our tests didn't appear
to pick up.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Wed, May 5, 2010 at 1:45 PM, Rich <rhyl...@gmail.com> wrote:

> My app is usually pretty resiliant to this, however I didn't expect a
> second user tag
>
> On May 5, 9:42 pm, Taylor Singletary <taylorsinglet...@twitter.com>
> wrote:
> > Looking into it. Sorry about the chafe. While the versioning in the API
> is
> > important as noted, we continually stress that API clients need to be
> > resilient to new fields appearing on any node.
> >
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > On Wed, May 5, 2010 at 1:40 PM, Orian Marx (@orian) <or...@orianmarx.com
> >wrote:
> >
> >
> >
> > > This totally just broke my app as well. Twitter please change this
> > > back ASAP!
> >
> > > On May 5, 4:39 pm, Rich <rhyl...@gmail.com> wrote:
> > > > Oh I'll add, I thought the point of a versioned API was that this
> sort
> > > > of thing didn't happen?
> >
> > > > On May 5, 9:37 pm, Rich <rhyl...@gmail.com> wrote:
> >
> > > > > I noticed today inside the user tags an extra user tag has appeared
> >
> > > > > We now have user->status->user
> >
> > > > > This is causing a crash on my app and number of engines I've tried.
> > > > > When did this get added and did I miss the notification?
> >
> > > > > Many thanks
> > > > > Richard
>

Reply via email to