Nougat

Lower part of the image is incorrect. All the data would pool in the trough, leaving free space at either end.

There's a lot to be said for a good generalist, but at some point, specialization takes you farther. I ended up with Windows server and Active Directory, as well as Exchange (lots of other stuff, too, but those are the main things). Apart from mass workstation management, or when a help desk person asks for a hand, I haven't dealt with non-servers in a loooong time.

No reviewing logs, no digging in at all, just "welp, a reboot didn't fix it. Gonna submit a support ticket and make no further effort".

My last few experiences with Microsoft support (spread over many years) have been "If I can't figure it out, Microsoft probably can't, either." For a smaller company, with a limited IT staff, having someone who is able to efficiently interface with vendor support without necessarily having all the answers themselves can be a useful thing. But I totally get what you're saying.

... "sysadmins" who only know Microsoft, ...

HEY

Seems short sighted to annoy the people who pay you the most money already.

You know, I get if they want to do this to Home editions, but why in the world would they do this to all editions? At the very least, this should never apply to domain-joined computers.

How hard does it have to be raining to require car wash mode?

If you are accepting payments, you absolutely want to offload that to a third party payment processor, so that you don't have to go through the hassle of doing PCI compliance.

Protip: Your shareholder votes are not secret, so if you're voting based on your holdings from an employee stock program, you might experience retaliation if you vote the "wrong way."

That doesn’t have anything to do with it, really. There’s plenty of ways that credentials get “leaked,” not the least of which is users who reuse passwords also falling for scam emails that have them “log in” to something. It could matter if some specific credentials were initially acquired because some other place was storing clear text passwords, and that place had a breach.

Still wouldn’t be an issue at all if users didn’t reuse passwords. That’s the lynchpin. This is users’ fault, not Roku’s.

No. Nobody has stolen hashes. They have usernames and passwords collected from elsewhere, that they tried against Roku, because people tend to reuse usernames and passwords.

Crowdsource it. Everybody go to your local supercharger and remove the "Tesla charging only" signs yourself.

The only thing that would have prevented this in this context would be mandatory MFA. Did they have that? No, but there's a huge number of places that are way more sensitive than a streaming platform that don't have mandatory MFA (coughETradecough).

It is wholly misleading to characterize this as a "Roku data breach," and it's disingenuous to portray Roku in this instance as somehow glaringly worse than everyone else.