8,865 karma · joined May 17, 2016
I personally don't like it due to the excessive amount of whitespace (form > function), but it's good to have the choice!
/etc/machine-id isn't the only thing to worry about when duplicating a VM - think SSH host key, DHCP leases, various filesystem UUIDs, log files, MAC addresses in ifcfg-* files and udev-persistent-net rules...
You can use virt-sysprep[1] to clean up a disk image.
In theory, you could use aggregate heat demand from the Ally thermostats to control a modulating OpenTherm boiler.
IIRC, Git is also relatively popular as a local Piper frontend.
You can make it work but it requires more effort than most corp teams are willing to put up with.
Of course, it all comes down to organizational issues in the end (they knew about the risk and ignored it), but this seems like exactly the kind of thing that politics want to prevent when they throw around money for "cybersecurity".
As a mass-market hosting provider, Hetzner is subject to constant fraud, abuse and hacked customer servers, and in consequence, their abuse department is very trigger-happy and will usually shoot first and ask questions later. They can and will kick out customers that cause too much of a headache, regardless of their ToS.
Their outbound DDoS detection systems are very sensitive and prone to false positives, such as when you get attacked yourself and the TCP backscatter is considered a portscan. If the system is sufficiently confident that you are doing something bad, it automatically firewalls off your servers until you explain yourself.
Likewise, inbound abuse reports sometimes lead to automated or manual blocks before you can respond to them.
They also rate limited or blocked entire port ranges in the past to get rid of Chia miners and similar miscreants with no regards to collateral damage to other services and without informing their other customers.
Their pricing is good and service is otherwise excellent, and if you do get locked out, you can talk to actual humans to sort it out. But, only after the damage is already done. If you use them, have a backup plan.
They don't do that.
Biggest issue with WA is the backup mechanism. You can encrypt it with a passphrase nowadays but AFAIK that's off by default, rendering E2E moot if either party backs it up to their Google Drive.
It uses a homebrew encryption scheme and does not have E2E encryption (yes, you can enable E2E for individual chats, but nobody uses it because it breaks most features).
Not to mention the weird corporate structure, lack of transparency, failed crypto token launch, dishonest marketing...
Other than that, IntelliJ is as universal as it gets.
Trackpoint sideways scrolling not working (works fine with libinput), inexplicably high power usage, wifi disconnects...
That's true - some kinds of social engineering cannot be prevented by technical means. BUT hardware keys prevent an entire class of extremely common attacks that every other form of MFA is vulnerable to. It would have prevented the method of compromise used here.
Any company not using FIDO/WebAuthn in 2022 is behind on best practices.
Umm... well, yes? The study does not prove (or even suggest) any such thing.
> [...] implies that new cell lines will have been created which can produce SARS2 spike proteins
This is nonsense (in the most polite sense) - the study does not show any such thing. In fact, it makes no mention of DNA or transcription whatsover.
In Germany, very few people have credit cards, and mostly for online purchases. Everything else is done via direct debit. Fraudulent charges can be reversed just like a CC payment.
Plus some overhead costs (but with Hetzner, I'd assume they're minimal - they have razor thin margins).