![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/gWmVEUZ94Z.png)
There is a difference between contaminated water, like in Fukushima, and regular non-contaminated cooling water. There should be no radioactive contaminants in the water that the French nuclear power plants release.
There is a difference between contaminated water, like in Fukushima, and regular non-contaminated cooling water. There should be no radioactive contaminants in the water that the French nuclear power plants release.
Yes and no, it is your instance’s backend that is responsible for this behavior. Once your instance is up-to-date, you should not see these old results any more. No need to wait for all other servers 😉
Wow, that is incredibly annoying! I can’t imagine they wouldn’t get forced to take it down.
Great idea, but the money they have is barely enough to make a dent in the development scope they are aiming for.
Sure, but that isn’t how it works under GDPR. You don’t need to prove the information should be deleted, you need to prove the information must be kept. To give an example, the company I work for deals with long-lived contracts (often 20 years or more), and once they end we are legally allowed to keep the information for about 5 more years. After that we need to remove it.
Something like this might have to be done to comply to GDPR. I’m not sure about the details, but I do know a company cannot keep personal information for longer than they need. At some point, I guess that would probably translate to removing old and unused accounts.
Are you expecting a developer to test everything every time they commit? Thoroughly testing even a small application or feature subset will take up quite a bit of time. You also want devs to commit often, so it is easy to roll back an approach that didn’t pan out, or just to go back and figure out what change caused something to stop working. If you end up committing only a few times per week because everything needs to be thoroughly tested, I’m not convinced it is a good approach.
What would be the probability of u/spez being behind this attack, in an attempt to sabotage lemmy?
Which programming language will you use?