street
Joined 10 years ago
Joined 10 years ago
But to follow up on your point: I hope the EB script that updates the pages automatically while doing maintenance will not wait for a response to its POST requests before actually letting EB perform the maintenance. Otherwise you create a crucial unwanted dependency on your status server.
Regarding your last paragraph: I'm not sure why you're attacking me personally here.
You don't have such an agreement with Amazon.
Regarding your edit: I don't want to vote for anything. I'm simply pointing out that there is a (real-life!) agreement, and a party (slock.it et al.) not holding themselves to that agreement, and that I'd enjoy seeing that played out in court, where it belongs.
The "hacker" simply used the DAO as it was meant to be used (i.e. according to the smart contract code), and deserves the funds. If there is a hard fork, I hope he sues slock.it for controlling the DAO, and for stealing the funds he is owed according to their own terms ("The contract is king").
You're saying you trusted it, got burned, and are already looking forward to the next one?
The DAO was described as "the code of the contract is the absolute truth, any other description is just a guideline", which was hailed as a new miracle by the investors, and now that it doesn't mean mountains of gold the founding principles are suddenly not important anymore?
The "hacker" simply used the DAO as it was meant to be used (i.e. according to the smart contract code), and deserves the funds. If there is a hard fork, I hope he sues slock.it for controlling the DAO, and stealing the funds he is owed according to their own terms ("The contract is king").