RE: 10 Things I Did While The Blockchain Was Down
From what I saw in the chat, it seems the bug, or one of them was a small difference between if I remember right 12 seconds verse 12 hours. a misplaced decimal point or something. It was working fine on the testnet, or so it seemed to timcliff, and then the bug was found by an action, and boom kapowee and the lockdown invalid action or whatever.
The thing people need to remember is that the safety system did work. It stopped and waited to be fixed. My guestimate 12-13 hours of downtime. Not sure on the exact number but no funds lost everything safe and sound and back to normal. For a software bug mind you.
MS, Apple, and other software people hide their bugs people don't know their stuff is not safe until after MS, Apple, etc tell them or they get caught by the media, "oh yeah, we had an issue with that a few months ago, it tooks us 6 weeks to fix it but your all safe now". type statements. So people missed a few hours of time, that in the end is all they lost.
I can't speak for anyone else, but my issue isn't with what comes after the failsafe kicks in, it's before. It's what can be done to prevent these things from happening. So far, the answer is nothing. We just wait until it breaks. I don't know how that compares to those other companies. I can't speak to the transparency of Steemit Inc, either, when it's the entire blockchain that goes down. Rather obvious something happened, and it's affecting everyone trying to get on at once.
I was thinking it was basically 11 hours.
The reason why it was working on the testnet is because the testnet didn't include testing for what happened, which is odd, since what happened was a result of the change in upvoting in the current 12 hour lockout period. So, the bug makes it through.