I realize you may be shaking something out but in case you are not aware:
http://stackauth.com/0.8/sites is returning
{ "api_sites": [] }
asked Jun 17, 2010 at 8:16
1 Answer
This has been fixed.
Its worth noting that if stackauth is down, the "sites" data served up the API will eventually go down as well. Its cached fairly heavily, but is still ultimately stackauth sourced.
answered Jun 17, 2010 at 14:46
-
1interesting. 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. Commented Jun 17, 2010 at 22:43
-
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. Commented Jun 18, 2010 at 2:23
-
@code poet - we're still in beta. What's the difference between broken because of service outage, and broken because a method signature changed? Commented Jun 18, 2010 at 8:05
-
.. 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. Commented Jun 18, 2010 at 8:51
-
I cannot mark this as answered because I see it as an avoidable point of failure. Commented Jul 9, 2010 at 0:56
/statscall doesn't return meta data anymore (such as site name, etc..)