Timeline for http://stackauth.com/0.8/sites down
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2010 at 0:56 | comment | added | Sky Sanders | I cannot mark this as answered because I see it as an avoidable point of failure. | |
| Jun 18, 2010 at 8:51 | comment | added | Sky Sanders | .. response coming... i want to give this some attention but i am just taking a short break from a cruel challenge and need to stay in zone. | |
| Jun 18, 2010 at 8:05 | comment | added | Kevin Montrose | @code poet - we're still in beta. What's the difference between broken because of service outage, and broken because a method signature changed? | |
| Jun 18, 2010 at 2:23 | comment | added | Sky Sanders | something to keep in mind is that there are many people building on the api. when a component of the api fails, our apps fail. the user doesn't think 'oh, some part of the underlying technology failed due to lack of fault tolerance' they think 'wow, this app sucks. this dude/company really doesn't deserve any more of my attention'. first impressions are irrevocable. | |
| Jun 17, 2010 at 22:43 | comment | added | Sky Sanders | interesting. sounds like a bit of fault tolerance might be in order. i can't imagine this data as any degree of volatile so perhaps a persistent cache would be a good idea. | |
| Jun 17, 2010 at 14:46 | history | answered | Kevin Montrose | CC BY-SA 2.5 |