Sadly, the "javascript required" part seriously turned me off to it. Why must sites keep doing this? What functionality on CL that worked fine 30 years ago now requires JS? Sadly, this has made the site largely unusable for me as I browse with NoScript, so I haven't been on nearly as much recently as I was back in the day.

Because if a company has recent instances of cutting safety corners to make a quick buck, and then one of that company's products has an accident, it's not an unreasonable thing to wonder if the same is true again. People have long memories, and trust is difficult to earn and easy to lose. I feel zero sympathy for Boeing, they've put themselves into a position where people doubt their ability to deliver safe and reliable products and they get to face the consequences of that for a while still.

No kidding. Just another data point in how completely out-of-touch ICANN has become.

Maybe it's time for the third change of the entity that holds the IANA function...

Always remember, if a for-profit company gives you a service for free, you are not its customer, you are its product. If you choose to use that service, odds are pretty good that at some point you will be treated like a product. Don't like it? Pay up, or move along. Or if you can do it better yourself, then do. Go get your own domain and use an email address in it. Even if you just forward you mail to Gmail or Yahoo or whatever, if you ever do decide to pick up and leave your new chosen home is just a simple /etc/aliases edit away.

Then you're doing backups wrong. Seriously, if you can't find one good copy of data to restore for a fairly fast-acting threat like ransomware, then there's some parameter of your backup policies that needs to be drastically readjusted. I could maybe see something like that for an advanced infection with a long fuse timer or something, but that's not what we're talking about here. And even in that case, you should at least be able to get your critical data out of the backups, even if you have to nuke the server infrastructure and restore into a greenfield to get rid of the infection (because just that scenario is part of your backup testing strategy, right? And if not, see sentence 1).

Certainly a valid concern, but IMO a better way to address it would be to make it illegal for the landlord to use the data in any way not directly related to building security, and place such harsh penalties on such actions that it wouldn't be worth the risk for the few extra bucks he may get.

Personally, I would always prefer a physical key over an access fob/card/app/whatever, but as someone that has also managed facilities I certainly understand that it is much simpler, faster, and cheaper to go in the computer and disable a lost token than to change a lock whose key has been lost. Especially locks on common areas where everyone has a key that must then be re-issued.

"Second, we need a mechanism to be able to quickly push updates to our users even when -- especially when -- everything else is down."

Sigh, yet another thing that will I'm sure be on by default, with either no way or a very difficult way to opt out of, and gives Mozilla persistent control into your browser way past the initial download. Why can't they learn, once I download the package I should be able to do whatever I want with it, for as long as I want, without ever having to talk to their servers again. I'm getting close to the point of just aliasing every domain Mozilla owns to 127.0.0.1 in my hosts file...

Well stated, and I couldn't agree more. To those looking to implement things like this to "improve my experience with the product", here's a clue: My satisfaction with your product is inversely proportional to how much it spies on my. And a data collection option that's on by default is spying.

Or FreeBSD. It's very unlikely I'll ever install another Linux-based distro on any personally owned system again, for two reasons:

1. Linus' "security bugs are not important, they're just bugs" mentality.

2. systemd.

Stuff like this just reinforces that decision. I've been slowly converting all my personal machines to FreeBSD. Seven down and one to go, and I haven't looked back at all. Though I certainly give a shout out to Devuan and Slackware for at least resisting the second item. If I ever did go back, it'd probably be to one of those distros.

Or even, "Lock the keys in the car when you drop it, and when I get there I'll grab the second set from where I keep it to unlock." Total cost $0.