We think this should be all resolved out within the next few hours -- already hearing reports of some relief for a number of Twitter clients. We're slowly expiring the cache on several objects in the system to clear this up rather than waiting for them to clear on their own. This has to be done with great care.
Thanks for the patience and apologies for the effect this has on your users. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 6, 2010 at 1:01 PM, melissa <melissaleff...@gmail.com> wrote: > Any ETA? We need to know how long, and propagation time, or we will > have to deploy a workaround. It's been about 24 hours now, and t is > affecting our customers. > > Thanks, Melissa, Awareness > > On May 6, 12:19 pm, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: > > We're working on getting this fixed as soon as we can. > > > > Taylor Singletary > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Thu, May 6, 2010 at 9:12 AM, irhetoric <karst...@microsoft.com> > wrote: > > > This appears to still be broken. It affects anyone using the > > > TweetSharp library as well. There's a workaround (http:// > > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but > > > hopefully it will be fixed soon so that we don't have to redeploy with > > > the workaround. > > > > > On May 6, 5:23 am, Raffi Krikorian <ra...@twitter.com> wrote: > > > > i'm currently looking into this now. > > > > > > On Thu, May 6, 2010 at 4:51 AM, Rich <rhyl...@gmail.com> wrote: > > > > > Yep looks like I spoke to soon, many of my users are still seeing > this > > > > > issue. I've actually handled it but Apple are now taking about a > week > > > > > to approve updates > > > > > > > On May 6, 6:50 am, Raul <raulr...@gmail.com> wrote: > > > > > > We still see this issue on every request athttp://streamd.in, > Also > > > > > > all other apps that use twitter4j are experiencing this issue. > > > > > > > > On May 5, 6:04 pm, Taylor Singletary < > taylorsinglet...@twitter.com> > > > > > > wrote: > > > > > > > > > This should now be fixed, though it may take a little while for > the > > > > > cache to > > > > > > > completely clear the labyrinth. > > > > > > > > > Let us know if you're still having wide spread problems. > > > > > > > > > Thanks! > > > > > > > Taylor > > > > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich <rhyl...@gmail.com> > wrote: > > > > > > > > Cool, thanks Raffi, I was more concerned if it was > intentional > > > rather > > > > > > > > than a bug :) Of course we all get unintentional bugs from > time > > > to > > > > > > > > time > > > > > > > > > > On May 5, 10:21 pm, Raffi Krikorian <ra...@twitter.com> > wrote: > > > > > > > > > my stance on versioning is for when something has changed > that > > > > > breaks > > > > > > > > > backwards compatibility. in this case, we haven't broken > > > backwards > > > > > > > > > compatibility, but a regression was introduced. > regressions > > > can > > > > > get > > > > > > > > > introduced in a variety of different ways, and across a > variety > > > of > > > > > > > > different > > > > > > > > > properties unfortunately. software projects do their best > to > > > avoid > > > > > them > > > > > > > > -- > > > > > > > > > but its orthogonal to versioning.... > > > > > > > > > > > either way - we're working on a fix. > > > > > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) < > > > > > or...@orianmarx.com > > > > > > > > >wrote: > > > > > > > > > > > > Well, I'm not sure if Rich was referring to the output > per se > > > or > > > > > > > > > > rather that this bug was probably tied to the skip_user > > > parameter > > > > > that > > > > > > > > > > was just added to timelines... which one could argue is a > > > > > candidate > > > > > > > > > > for versioning. > > > > > > > > > > > > On May 5, 5:02 pm, Raffi Krikorian <ra...@twitter.com> > > > wrote: > > > > > > > > > > > versioning has absolutely nothing to do with this - > this is > > > > > clearly a > > > > > > > > > > bug. > > > > > > > > > > > > > On Wed, May 5, 2010 at 1: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 > > > > > > > > > > > > > -- > > > > > > > > > > > Raffi Krikorian > > > > > > > > > > > Twitter Platform Teamhttp://twitter.com/raffi > > > > > > > > > > > -- > > > > > > > > > Raffi Krikorian > > > > > > > > > Twitter Platform Teamhttp://twitter.com/raffi > > > > > > -- > > > > Raffi Krikorian > > > > Twitter Platform Teamhttp://twitter.com/raffi >
