I'm still seeing the errant <user>id</user> node at noon EST.
On May 6, 10:03 am, janole <s...@mobileways.de> wrote: > Just as a follow-up, I've just seen a <user>id</user> again while > doing a verify_credentials.json call after I've retweeted some user. > > The <user>id</user> entry is inside the <status> entry of the calling > user's <user> entry. Oh, complex. It's like: > > <user> > <status> > <retweeted_status>...</retweeted_status> > <user>id</user> > </status> > </user> > > Here's the link to the data:http://data.mobileways.de/brokentweet.txt > > Ole > > -- > Jan Ole Suhr > s...@mobileways.de > On Twitter:http://twitter.com/janole > > On 6 Mai, 15:18, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: > > > > > It's taking a long time. We're investigating possible means to hasten the > > resolution and any other reasons the cache might not be resolving. > > > Taylor Singletary > > Developer Advocate, Twitterhttp://twitter.com/episod > > > On Thu, May 6, 2010 at 3:17 AM, rohit <mrro...@gmail.com> wrote: > > > Seems like the cache has still not cleared. > > > > Regards, > > > Rohit > > > > On May 6, 6:14 am, Taylor Singletary <taylorsinglet...@twitter.com> > > > wrote: > > > > The bug is fixed. The cache, however, has to negotiate its way through > > > the > > > > dusty corridors of memory. > > > > > Please let us know if you don't see a significant improvement in regards > > > to > > > > the impact this had on your applications within a reasonable amount of > > > > time. > > > > > Sorry about the mess. > > > > > Taylor > > > > > On Wed, May 5, 2010 at 2:02 PM, Taylor Singletary < > > > > > taylorsinglet...@twitter.com> wrote: > > > > > Hi Folks, > > > > > > We've identified the bug where an inner user object is being passed > > > with > > > > > the current status on users/show, are working on a fix and will have a > > > > > deploy go out as soon as we can. Thank you for your patience. > > > > > > Taylor Singletary > > > > > Developer Advocate, Twitter > > > > >http://twitter.com/episod
