There are so many unknowns in "dark matter" that they can't really claim it doesn't interact with itself. Some of the theories have it not interacting with itself, but that's not a good argument. There are too many possibilities. ...From here on I'm just spinning ideas...
FWIW, I came up with a theory that there are nine basic flavors of dark matter, each about 1/10th the mass of the universe, and the various flavors don't interact with each other, but they do interact with themselves, and are as varied within themselves as ordinary matter is. So you'd have nine types of dark galaxies.

This is a really BAD theory, but it's fun. The problem is that dark matter tends to be associated with galaxies, and local dark suns should be quite noticeable in that circumstance. We don't see that kind of result, so there aren't any local dark suns. I'm not sure we could detect them in another galaxy, but they should affect stellar motions within our own in a noticeable way. Unless you want to special case our own galaxy, dark matter needs to be rather diffuse for some reason...nothing much larger than a G class sun, possibly a M class. The reason you can get away with something that large is that lack of friction with ordinary matter means that you wouldn't get anything captured into a binary orbit with a normal star.

Every time people hear what it actually involves is outrage and opposition, at least all the way back to when Intel first announced that they wanted to hardcode identity numbers inside CPUs in 1999. But the corporations involved have been relentless, and have sunk countless billions of dollars steadily forcing it forwards, and building front organizations to obfuscate and whitewash it.

With Windows 11, Microsoft was finally able to FORCE Trusted computing hardware into every new computer. Not just every new Windows computer, but every computer.

Every new Intel PC CPU has built in Trusted Computing enforcement hardware. Every new AMD PC CPU has built in Trusted Computing enforcement hardware. Every new ARM PC CPU has built in Trusted Computing enforcement hardware. The only processor lines that DON'T have it are the microcontrollers.

There are some unlocked smartphones available, but as far as I can determine it's literally impossible to buy a smartphone that doesn't have hardware trusted computing built in.

I specified that enforcing Trusted Computing at the internet access level is still a long term goal, they couldn't get away with it today. However they are well on the way to success. Virtually all new hardware supporting trusted computing, all the front groups rolling out standards and systems, and as it gets incorporated into things everyone is going to increasingly running into situations where they get locked out of stuff if they're not Trusted Computing compliant. Streaming already restricts you to the worst quality if you're not compliant, and it's only going to get worse as pre-Win11 computers fade out and as more things require it.

I don't think it's been ignored, but it might have been siloed. I was aware of it, and I'm not even close to an expert in that field. (OTOH, that bit about Teflon was surprising. I'd have expected Teflon to be totally inert.)

That's probably a underestimate. But, yes.
The real problem, though, is that many of them intensely support him. I think many of his supporters tend to be more firmly committed than were Nixon's.

Calling him a loser is incorrect. That he has occasionally lost is correct, but find someone who hasn't. Sometimes it seems he's playing a different game than the one we expect him to play.

But I rather agree with the rest of your characterization. And think it leaves out quite a few correct pejoratives.

I'd hardly call exact date of birth "low information content".

And yes this does reveal exact date of birth, regardless of the bullshit obfuscation that it supposedly only reports age range. The server simply tracks the reported result every time the user connects, and on some specific day the result CHANGES to announce their date of birth.

-

This is based on SLSA (Supply-chain Levels for Software Artifacts), brought to you by the same fuckers making Trusted Computing and the TMP (Trusted Platform Module). It's part of the same shitstack to prohibit you from altering your software and to lock you out of your own files, and to send spy reports out over the internet so you can be cut off if you "fail" the Trusted Computing check.

The software can use a TPM's (Trusted Platform Module) Sealing function to encrypt your data such that it's impossible to access your own data if the software is modified. It can then pass control over that data only to software updates that carry a signed security certificate from Broadcom (or any other company using this system).

It is no longer open source, your system no longer works as you can no longer access your Sealed data if you change so much as a single letter of the code. Even recompile unaltered code won't work, unless you magically manage to get your build environment absolutely identical to the company's build environment and get byte-for-byte output. Even that may be impossible with the newer levels of non-deterministic compiler optimizations.

Also, with TMP's Remote Attestation feature can be used to transmit your machine's software configuration over the internet, so that you can be cut off if your system doesn't match Broadcom (or other company's) cryptographically signed certificate.

And then of course there's Network Access Control (NAC) / Trusted Network Connect (TNC). In the long term, the goal is for ISPs to use NAC/TNC to interrogate your computer for Trusted Computing compliance, and deny you any internet access whatsoever if your machine isn't compliant. Software with this sort of "security" certificate would pass inspection, while any attempt to alter the code would be detected as "tampering". You then get "quarantined". What "quarantine" means is that you are denied internet access - with the exception that you do get very restricted access which can only be used to download the approved software to "fix" your computer into Trusted Computing compliance.

I think the problem is that there's a conflict between good security and ease of remote use. They've been pushing ease of remote use with "adequate" security. Now that security is no longer adequate, but they don't want all the customers to be angry with them.

Sorry, but who, officially, has the right to name the lake? I'm pretty sure it isn't the president.

My preference is Eustatia.
I think I first proposed this around 1990, perhaps a little bit later.

To me it appears you've go an extreme definition of "meaningful". It you want to claim the effect will be small, I'll go along with you. If you want to claim it won't be present...why do you believe that? It appears to me to be an unreasonable claim.

Well, actually Denver usually DOES have higher cancer rates. Attribution, however, is difficult. (It's probably not just altitude.)

What do you mean? Denver has frequently been compared with some sea level city, and found to suffer more radiation damage. (The exact radiation damage found depends on the study.) Of course, it's hard to control for the amount of granite, etc. nearby, so they aren't strictly reliable studies, but they *have* been made.

Sorry, that's a bad argument. It may well be true, but any absorbed radiation will raise the temperature, and any raise in the temperature makes unusual chemical reactions more probable. So you need to argue that the factor is too trivial to be significant. This is probably true, but has never been demonstrated, and probably cannot be demonstrated. (I've seen claims that they're demonstrated the harmlessness, but the claims were always logically invalid.)

That's the type of meter the VA issues to me. And, I send my readings to my Diabetes Coach about once a month and we discuss how I'm doing and adjust things if needed. I've been doing this for about 20 years, and am very well controlled.