destroyed

You’ve already destroyed our lives. Show some mercy.

Media Temple's brand destroyed by one press release.

For their pains, their careers were destroyed by the people who run the current mainstream conservative movement. Let's take a look at those points of yours.

Why do people always pass judgment on spending on things they don't agree with as if the money is destroyed. It's not like they pile all the cash onto the rocket and send it to space.

Much like the old CGI model, the entire environment is created, used and destroyed on each request. This is a feature not a problem.

This is "the guest you sent me destroyed my home and sense of safety." This is completely beyond the pale, an incredible stretch no one, clearly, bothered to imagine.

Similarly, bureaucracies get created, but never seem to get destroyed. Compromise slows things down, but it never seems to stop it.

> [Edit to Add] Believe me, I have destroyed the brand new iDevices of senior Government personnel because they plugged it into a classified network to charge it for less than a minute. The law is the law.

Politicians have so destroyed the word "war" that it's impossible to have a reasonable discussion about any use of violence by the state. Perhaps that was the goal.

Professional researchers often sign agreements in their children's blood stating that their data will be stored on an encrypted disk, won't leave their laptop, and will be destroyed when the research project is completed. The cloud is the last place they want their data to go."

Lately, I've come to realize that the September 11 attacks actually destroyed America. In the grand scheme of things, the attacks themselves caused minimal damage and casualties.

One can imagine very few situations outside of drugs were evidence could be so easily destroyed as to justify a no-knock warrant.

If it were true that a Tesla battery pack couldn't be destroyed by letting it fully discharge, or that it had never happened, then they would have mentioned it in the release. In fact, they take the opposite tack, re-emphasizing near the top of the document that users should always plug the car in when parked.

I think it's pretty clear with even a cursory reading of such documents as the Declaration of Independence and the Preamble to the Constitution that the standing belief was that Government should be destroyed and rebuilt if it ever stopped serving the people. Such as when it falls into a perpetual state of war.

Are you now or have you ever been a member of the Communist Party" is a question that destroyed many careers as the blacklists proliferated back in the 1950s. That was indeed a repulsive set of events by which many innocent persons were hurt and today our national conscience wishes it could take back the damage done to them.

While testing we discovered that a sample he'd kept for almost 10 years could be destroyed in a matter of minutes under a methylacetylene-propadiene propane blowtorch. Unfortunately after many samples & tests we where unable to find a effective application method & we parted company on good terms.

According to your article you sit back and say "oh thats totally ok because thats innovation and I'm happy that everyone has copied me and destroyed my advantage". The problems with the patent industry are patents abused by companies who have absolutely no interest in developing them but rather trolling them to simply extract money from other companies.

Your generation, and the ones before you, destroyed and defunded parks, they built malls over open land, they made 100% safe unfun playgrounds, they turned America in the the most litigious country in the history of mankind scaring anyone from allowing anyone ever to make a mistake or get slightly hurt, you buy your kids more screens than books, and then at the end of the day you wonder aloud why kids don't play as much? * That was a proverbial you, no you specifically OP.

Forget innocent until proven guilty, we are months away from any trial, only 3 of the 12 defendants are even in custody, yet domains have been seized and businesses destroyed by an 11-point case filing, of which only 2 or 3 points may ever get to trial If the site owners are found guilty, they could be facing decades in jail. Penalties for money laundering that were increased as a way to lock up leaders of drug cartels and terrorist groups are being applied to people who built successful legitimate companies and had to work around all US banks being sacred of the vagueness of a law that was never directly enacted.

When we first started DigitalOcean we occasionally received tickets from customers about recovering a droplet that they had destroyed. Unfortunately when a droplet was destroyed it was gone from the system and it wasn't possible to recover. To help our customers we decided that it was a good idea to take a temporary snapshot of the droplet after the destroy was issued that would automatically expire. This way if someone mistakenly destroyed a droplet they could still recreate it. This proved to be a lifesaver for many customers of DigitalOcean when a third party company that provided a provisioning service that integrated with DO, AWS, Rackspace, etc. was compromised and the attacker issued a delete to all customers and all instances. Because this mechanism was in place we were able to recover almost everyone's droplets. We ran into an issue with securely scrubbing data which was publicized on HN and we implemented a fix immediately with a scrub flag. Unfortunately we made a mistaken and made the default setting false. Most customers often click the default, and I myself do the same thing, since I assume that the default is the best course of action and this led to this issue resurfacing. This also was posted to HN and we immediately decided that the default behavior should be to scrub. Prior to this when a customer selected scrub securely because they were taking two actions, issuing a destroy, and setting a flag, it was safe to assume that they indeed want the data completely destroyed. However when we had to reverse the default we were left in a situation where the default would not create a temporary snapshot if we used the secure destroy flag as the indicator for whether or not a temporary snapshot should be created. Since we've implemented the temporary snapshot feature we have had 1154 droplets that have been restored after a destroy from different 752 customers. That's 752 customers that were elated to find out that they could recover a droplet that was mistakenly destroyed so obviously this is a very beneficial feature since each time one of those customers recovered a droplet it was a huge win for them. We assumed that since the temporary snapshots are automatically destroyed this would not be an issue. In fact in the control panel we provided an additional feature which would make the snapshot permanent otherwise that snapshot is deleted. I think the issue that is brought up here is definitely worth a discussion and we treat security very highly. Since we had the prior HN post regarding changing our default behavior we have been working behind the scenes to ensure that would be the default behavior so that the scrub flag could be removed entirely and that all destroys regardless of how they would be issued would be secure. That behind the scenes work is almost entirely done so this discussion of the temporary snapshot is great because it allows us to revisit this issue once again. We have not had any other customer complaints that during a secure destroy the droplet and the backups and the snapshots were not immediately destroyed. So it was great to engage in a conversation with the customer to understand their view on how they wanted these commands to functions. We'll be engaging with engineering tomorrow to see if it's time for us to begin to phase out the scrub data flag and instead perhaps open up a new flag which would create a temporary snapshot. For the UX/UI of the control panel we would make the default behavior of the destroy create a temporary snapshot and we would have to discuss to see if the API should behave the same way. Often API customers are creating and destroying many servers so it may be safe to assume that they do not want a temporary snapshot, though having default behaviors differ between the control panel and the API is generally not a good idea. I think in general this highlights an issue that all startups deal with. That is as the product grows and matures and as features are added there are often unintended cascading consequences. In this case we have done our best to do right by the largest number of customers to ensure that data is safely and securely destroyed while still providing a default behavior that would protect customers against accidental destroys whether they be self-initiated or otherwise.