Short answer: no
re: people leaving
Note that sometimes we don't let people go. Sometimes they leave us. Business is business.
re: draft troubles
Here is the deal. We had problems with drafts on the morning of 10/20. We did what we typically do in those cases:
- For public leagues, we reset the draft to one week later. This gives people time to leave and join a different draft slot if the new time doesn't work
- Private leagues are in a sense easier now that we let you reset your own draft. We put your draft into a failed state, which means that if you reset your draft time it doesn't count against your limit of 3 resets. Your commish can then choose a draft time that works for your league.
We were frustrated because it really wasn't obvious to us what caused this outage. A key machine lost its mind and became completely nonfunctional. We couldn't even log into it. We had never seen anything like it before. We started work on a few initiatives that will actually make us way more resilient in the future, but we didn't want to be hasty and push out a really big change on short notice right before the season starts.
Alas, at the exact same time a week later, the same thing happened. That was good in that we're almost positive it highlighted what was causing the problem so we can stop it from happening again; it wasn't a coincidence that it happened twice exactly a week apart, and that highlighted the issue. But it was really bad because it meant any drafts that did just schedule one week out from their first failure would probably have failed *again*, and without another week to go before season start. It was also frustrating because we have the really cool long-term fix baking, but it just wasn't ready to push live quite yet.
So there is only so much I can say to apologize to people that got hit by these outages. It drives us nuts when people lose their drafts, because we know how hard it is to schedule them. I'm actually really happy with how much more reliable we've made drafts in the last few years (hint: a TON), but that doesn't make us feel any better when something like this happens. I am feeling good about the long-term fix that is coming out of this incident. It removes another key point of risk for getting drafts kicked off smoothly, and makes it even less likely something like this will happen in the future.
The only other thing I can say is that I definitely wouldn't take the examples you're noting and use them as evidence of Yahoo!'s demise. This was a bug, and nothing more. Not a sign that we're short on people, short on hardware, etc. etc. This particular weakness has always been present, it just never happened before.
EDIT: On a brighter note, for anyone who didn't notice, our basketball mobile app is live for both Android and iOS, prior to season start. Enjoy...