That's good to know, thank you. I'm been considering moving away from systemd, and certainly don't use Chrome.

The number of things you need to try to keep track of merely _improve_ your privacy is maddening. The whole world seems to be against you.

I don't like the idea of a persistent id for my machine. Would there be any harm in rewriting the machine-id at every boot? Or just deleting it as part of the shutdown sequence?

I went to check if Flatpak would protect against this but it seems although it's a wanted feature it's not so straightforward to implement: https://github.com/flatpak/flatpak/issues/4311

Thanks, I wasn't aware of that.

I have the urge to grab a pitchfork, but I know better than to make assumptions about why that functionality was added. Time to do some homework I guess.

Wow, three pieces of software I don't use for other reasons, just gained a new reason to evangelize against them!

The utility of and presence of unique identifiers in software should be no surprise.

But if you are using TelemetryOS (i.e. you cannot fully switch off the chatter) and your daily Web browser doesn't offer privacy extensions, you are the product.

Sounds like chrome is the problem.

In dbus, it seems the feature is intended for two processes to know they can access the same shmem and other system resources. I'm struggling to understand in which circumstances would that be useful.

Trying to imagine a world where I use Chrome unironically.

But does browser send these id?

As an Hyperbola user both systemd and dbus are a no-no there.

Is this specific to Debian?