632 karma · joined January 13, 2014
In Germany, 13% of our energy is nuclear energy. Only 13%. We're a net exporter of energy, big time, so we could (almost) disconnect nuclear power right now, if we didn't want to export energy to our neighbours. We're at 52 TWh (tera whatt hours) export per year right now.
In the last 18 years we've gone from 143 TWh (2000) to 92 TWh (2018) per year nulcear energy generation. In the same time, wind energy alone has added 160 TWh per year, so that alone is more than enough to compensate. There is another 105 TWh from water, sun & bio gas that we added. But wind energy alone is not even close to fully captured.
Thing is: each nuclear energy plant in Germany right now makes more than 1 million € per day in profits. Each plant. If you'd have that plant as an energy producer, would you take it offline?
I do not see how the payer is the account owner. At all. Can you clarify why that would be?
Legally speaking (in german law): The account owner is the person who opened the account, because that is the person who the provider has made the contract with (except the situation of a "Geschäftsbesorgungsvertrag" or a "Vollmacht" [ letter of authorization, power of authority, idk. whats the english term] where you make the contract for someone else). The payer may have a legal connection to the account owner (will, in 99% of the cases, but must not), but not to the provider.
So legally speaking Linode - at least in german law - Linode is providing unauthorized access to a tzhrid party and will be held accountable for all the damages the account owner suffers. That is a violation of GDPR, too. You'd propbably resolve that by a simple letter from your attorney or a court order if Linode does not comply (taking a few days only because of "emergency conditions").
It's not easy to translate all the legalese, I hope you can follow ;-)
It says: "When assessing whether consent is freely given, utmost account shall be taken of whether, inter alia, the performance of a contract, including the provision of a service, is conditional on consent to the processing of personal data that is not necessary for the performance of that contract. "
It's like a butcher shop saying "the meat could be free if we could only reduce our cost by not caring about hygiene".
Edit: oops, the methaphor doesn't work at all :-D
From a european ISP standpoint: the introduction of a systemic weakness is a violation of Art. 32 GDPR. We just can't do it.
Classic double-bind. GDPR is more important than Australia to us, so we just block all access from and to austrialia. We have 195.000 affected webhosting customers (domain, email, website, servers), btw.
You can write a small script to look up all PSL domains and check if the www and APEX domain has the same dns records.
Our implementation (we control 15 or so) does not, have a www-subdomain for the domains. Anybody can register the www-subdomains.
Should you not know which one you have connected to?
Which sane person would make such an investment?