4 ms·
Needless to say their (login) servers crashed from the pressure of people resetting their credentials. "Hey, you know what might be a good idea? Let's email al
by notum 9y ago
Needless to say their (login) servers crashed from the pressure of people resetting their credentials.
"Hey, you know what might be a good idea? Let's email all of the accounts at the same time using an Appriver blast!"
Atlassian. I hate to hate you.
- rubyn00bie 9y agoWhile I can see your point in this case I think it was the appropriate action, their ops team should've just beefed up their resources in conjunction with the email blast. Only emailing a rolling amount of your customers becomes a shit show of support, who do you email first? Who do you email last? How long do you wait between groups? For who is security important, your biggest customers, highest paying, most security conscious? It's a real shit show to know, and one you'd absolutely get wrong, letting everyone know as fast as possible is the only acceptable solution to a security breach.
- notum 9y agoThe servers should have definitely been prepared for the increased load. Perhaps I'm overly optimistically using the plural form in this case. Truth to be told I can only assume this was done in a short burst, given my limited sample of (hopefully ever narrowing) circle of people who use Atlassian products. But would distributing the bulk-mail over an hour (two, three) using a randomized sample of their customer base really made a significant impact to security or their support? I wonder how I'd do it, really, if let's say, beefing up my infrastructure for some reason isn't an option.
- throwaway8473 9y agothey dont have an ops team anymore it was all moved to a terrible new product that they hope will make people love them again source:former employee