Yep, for sure.  And maybe the rash of new 200 errors, and OAuth
errors, etc, are not under the purview of API (though I would doubt

But, at the very least, it's over another, what, 48 hours since the
last official update.  And those developer updates are presumably the
responsibility of API.  And all we've got is breadcrumbs dropped from
the Carolinas by a new part-timer who tells us it is his day off.

Okay, fair.

But WHO in API is "day on" to communicate with us?

On Aug 8, 11:55 pm, Cameron Kaiser <> wrote:
> > Part of it is DDOS response, part of it is API issues... as one of the
> > updates most recently noted with the "known issues" list.
> > And, by the way, if you're a deckhand on a submarine going down, you
> > think you would go to a movie because it's your time off, or do
> > whatever you can to help out?
> If the API is down because of the DDoS pounding on ops, then it doesn't matter
> what the API devs are doing or not doing: it's not going out. I'm not sure
> if you mean that the API devs should be working on the network problem, but
> where I came from, crossing the discipline streams usually turns out to be
> staggeringly unhelpful. I didn't tell the network guys how to run their
> infrastructure, and they didn't tell me how to run my servers.
> --
> ------------------------------------ personal:
>   Cameron Kaiser * Floodgap Systems **
> -- "Use gun kata for fun! Because you worth it!" 
> ------------------------------

Reply via email to