Deletes all instances of Microsoft's GDID and prevents minting of new ones

I like to call this style of writing "advanced technical claudish"

> What causes this obfuscated writing style?

Claude without an editor having worked too long on its own project.

Probably every language at once being expressed in the syntax of English.

"real-shaped PUID" seems like usage of "real-shaped" outside of normal disciplines, but probably accurate enough

It's missing a couple of wrinkles, surfaces, belt-and-suspenders, belt-and-braces, knobs, no-ops, "things that narrate", bookkeeping, stranded sessions, "the gate leads the arrangement", shit-gated, "to be wired after we've dealt with the parked features", "that's not the whole story", "the interface wants classes", slots and "whatever-backed interfaces".

All of this is enhanced claude-era vocabulary minted at the pool-of-efficiency, built as a de-facto evolution of legacy-style language.

Humans and their comment postambles, amirite?

(Here's a literal quote from a claude session: "After the f-war, the evidence itself stops lying."

I don't understand why companies are not focusing more on making these highly intelligent models speak a decent language. Maybe they are, and they're failing. But the last few months have made it pretty difficult to engage with these highly intelligent assistants.)

Thank you for LLMese, that's gold.

Trying to make windows work differently than what Microsoft wants is a losing proposition.

It would make more sense just not use windows to begin with.

Or just have the option of any of these

Same GDID would pollute the data for Microsoft if enough people did it. Which would also incentivise a fix or another way to differentiate.

Random GDID would likely be the most "security through obscurity" approach but still allow tracking per "session" or whatever time period it changed in.

No GDID could stick out more and if enough people did it also incentivise a fix.

Hard to say which is best but I also like another persons suggestion of random GDID assigned at boot. Or maybe no GDID by default with the option to spoof a random GDID manually

Or recreate it on every boot :)

For example, it you are paranoid about Linux's /var/lib/dbus/machine-id file you can easily use dbus-uuidgen(1) to re-create it on shutdown.

Better yet - reply with the same GDID of the machine doing the scanning :-D

> you'll have to unlearn your muscle memory of the Ctrl key

There is another option, which is to use Karabiner to revert to PC-like shortcuts. Learning the mac way is probably better if you plan to use mac exclusively, but I was triple-wielding macos+windows+linux for a period and I wanted my muscle memory to work across all of them.

Adguard Home running on a Raspberry Pi. Point your router at it for DNS, works like a charm.

Two years now, and it consistently blocks 48% to 54% of all the trash, including _all_ Microsoft domains.

Is there anyone maintaining a canonical list of such domains and hosts? This would be useful to add as firewall rules on a router upstream of any windows hosts, or to a pihole.

Run say a linux firewall vm with PCI nic passthrough and give the host windows machine a virtio-pci/TAP interface as its network access is one countermeasure off the top of my head I can think of.

Storing IP address itself is not illegal. The questions are:

1) what is the legal basis for storing it and if that's proper or not (e.g. legitimate interest requires balancing test)

2) if proper GDPR Article 13 notice was given and it covers that processing

3) if all Article 5 principals are being followed in regards to it (e.g. data minimization, retention period etc.)

4) if Microsoft had legal basis to transfer the data to police (they probably did, that's not high bar to clear)

You sure it wasn't one of the other UID numbers that have been in use longer ?

I’ll bite. What is it missing?

There is literally court documents showing this was used by surveilling in at least one case. How that is paranoia