Someone from Twitter did chime in - Matt works here. I'm sure he's investigating if he said he's investigating. Hang tight!
On Thu, Jan 8, 2009 at 10:19, FrankieShakes <frankma...@gmail.com> wrote: > > Just wondering if there has been any progress on this issue... Can > anyone at Twitter chime in? > > For what it's worth... I'm still experiencing the problem. Just had > it happen again this morning. > > > Thanks, > -f > > On Nov 27 2008, 7:51 pm, FrankieShakes <frankma...@gmail.com> wrote: >> Hey Matt, >> >> I received the error message again this morning. It always returns >> the same error message in the HTML body: >> >> ----------- >> <span style="font-size:1.8em; font-weight:bold">Something is >> technically wrong.</span> >> <br /> >> <div style="font-size:1.2em;margin-top:2px;color:#b6b6a3"> >> Thanks for noticing—we're going to fix it up and have things >> back to normal soon. >> </div> >> <br /> >> <p style="margin-bottom:10px;text-align:center"><img src="http:// >> static.twitter.com/images/please_fix.png" /></p> >> ----------- >> >> I suspect nobody's around at Twitter during Thanksgiving ;) Hoping >> you can give me some feedback when you're back from the holiday. >> >> Happy Thanksgiving! >> -f >> >> On Nov 24, 1:59 pm,FrankieShakes<frankma...@gmail.com> wrote: >> >> > Hey Matt, >> >> > Thanks for looking into it for me. >> >> > I went back to my system logs and actually did find a case where it >> > happened to me: >> >> >http://pastebin.com/m2e1ae375 >> >> > If you look at the timestamp, this was on Nov. 13 @ 14:53:20 (EST). I >> > also found other occurrences: >> >> > - 2008-11-12 16:54:16 (EST) >> > - 2008-11-18 15:54:23 (EST) >> >> > Maybe this will give you some further insight. In my case, however, >> > the server returned a 502 instead of a 500 serve error. >> >> > Let me know if you come across anything. I'd love to get this >> > resolved. >> >> > Thanks again, >> > Frank >> >> > On Nov 24, 12:51 pm, Matt Sanford <m...@twitter.com> wrote: >> >> > > Hi Frank, >> >> > > Nothing comes right to mind. I'll start looking through logs and >> > > see if I can find anything. Is the issue always with /favorites.json? >> > > Do you have a general idea when this started, or when you started >> > > receiving reports of it? >> >> > > — Matt Sanford >> >> > > On Nov 24, 2008, at 09:45 AM,FrankieShakeswrote: >> >> > > > Hey Matt, >> >> > > > Unfortunately, I haven't been able to reproduce this myself. I have, >> > > > however, had quite a few users email me with their logs and each of >> > > > them has the exact same payload. >> >> > > > Any ideas? >> >> > > > Thanks, >> > > > Frank >> >> > > > On Nov 24, 12:31 pm, Matt Sanford <m...@twitter.com> wrote: >> > > >> Hi Frank, >> >> > > >> A 500 is normally an error on the Twitter side. Can you provide >> > > >> an example account where you're seeing this? >> >> > > >> Thanks; >> > > >> — Matt (@mzsanford) >> >> > > >> On Nov 24, 2008, at 09:26 AM,FrankieShakeswrote: >> >> > > >>> Hey everyone, >> >> > > >>> I've been receiving quite a few reports lately where users are >> > > >>> experiencing issue with requesting the timeline. I've asked for log >> > > >>> reports, and each and every single one of them includes the >> > > >>> following: >> >> > > >>>http://pastebin.com/m36523b99 >> >> > > >>> I'm hoping someone could shed light on the situation... I'm not sure >> > > >>> what would be causing this (other than load on Twitter's servers). >> > > >>> The only thing that concerns me is that I don't know whether other >> > > >>> clients are experiencing the same issue -- I'm thinking not. >> >> > > >>> Any help would be greatly appreciated. >> >> > > >>> Thanks, >> > > >>> Frank > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
