Annoying HTTP error dialogs.

[GoogleCodeExporter]

It's nice to know if twitter has failed...in the moment that it fails and 
shortly after.  More than a few seconds and such information is useless, 
particularly if they being to pile up.  5+ modals that there was a 500-level 
error are not useful at all after coming back to the application after fifteen 
minutes or more.

Please consider a different way of communicating a twitter API issue other than 
a modal window that requires the user to click it away.  If all is well at the 
moment that I'm actually looking at Hotot, error notifications from minutes 
earlier are not needed.

Original issue reported on code.google.com by schet...@gmail.com on 1 Apr 2011 at 6:19

[GoogleCodeExporter]

Original comment by 5h3l...@gmail.com on 2 Apr 2011 at 12:52

• Changed state: Accepted
• Added labels: Type-Defect, Usability

[GoogleCodeExporter]

Issue 332 has been merged into this issue.

Original comment by 5h3l...@gmail.com on 5 Apr 2011 at 2:55

[GoogleCodeExporter]

PLEASE do this. I'll take it a step further - 403 errors happen often enough 
that I simply don't care about them. If I'm actually doing something like 
posting, retweeting, searching, etc. then show me the error, though still not 
in a modal window. Maybe a toaster-style message bar that drops down for a few 
seconds. But not a modal window.

Original comment by jess...@gmail.com on 9 Sep 2011 at 5:11

[GoogleCodeExporter]

fixed it.

Original comment by 5h3l...@gmail.com on 7 Oct 2011 at 12:29

• Changed state: Fixed