I don’t see a problem here. If the US auto makers are so worried, they should buy a few of them, copy their secrets, and sell them at a marked down price.
Turnabout is fair play, after all.

It’s only minor if the data points in this breach are used by themselves.
Once you aggregate this with other data breaches, you could end up with a much bigger capability to target anyone in this breach.

Enough games. If you can’t get him to shut up, go over his head to every social media site he blabs on and hand them legal orders to remove the offending comments and disable his accounts.

The only thing that got botched is that thumbnail. Why do the Roman style columns look like an M.C. Escher painting?

Knock it off, Microsoft. You’re not my buddy, you’re an OS. Your job is to sit down, shut up, and run the programs I choose. That’s it.
If I find a function that’s useful for more than a week, I might make a batch file for it. Until then, you’re spare code.

Or the XCOM games.

There’s also a limited federation mode that server admins can use. Users and posts are still searchable, but they do not show on the public federated feed.
Useful for this exact case where a server may have beneficial accounts, but the rest should be hidden for moderation reasons.

Still would prefer it being on a proper mastodon server, but I can live with this. Whatever server ends up hosting a President’s account now has to deal with record preservation laws for their posts. Let’s leave that bureaucratic stuff to threads.

Having managed an exchange instance for my old job, I can safely say that DKIM and DMARC are just some extra DNS entries for out-of-band verification. They can be boiled down to a pair of checkboxes on a compliance sheet.
I can also say that most of the companies we got emails from didn’t have DKIM, and even fewer had DMARC. Or worse, they had DMARC set to p=ignore. Which is honestly even more infuriating.

Meanwhile, Microsoft’s Exchange platform blatantly ignores DMARC failures for senders and relays on its “Good PTR list”. Bit of a glaringly large hole for spam to pass through.

If you have admin portal access to write transport rules, I recommend writing a rule that has the server reply with a 550 5.7.1 Delivery Refused error. Trigger it based on the keyphrases “top of Google search” and “affordable SEO” to start with.