The main reasons for me are security, reliability, and one less daemon. But you do you.
Docker Compose works great with Podman.


Also protecting you from the East Wing of the White House.


OK. Let’s assume nobody has ever gone through it. Do you imagine that - especially in the US - lawyers of massive companies didn’t wring out anything and everything about telemetry?
What is the legal mechanism they have for doing that? Microsoft is holding all the cards here.
Do you imagine companies like JP Morgan, or - famous for money laundering terrorist money - HSBC would be happily using operating systems with “spyware”?
Happily? That I can’t say. But they are using Windows despite any “spyware.” Likely because, like you, they deem the risks worth it.
The one you linked is the Optional Diagnostics Data, this is the one you can disable by toggling telemetry to “basic”.
What percentage of Windows users (power users or otherwise) would you guess disable it? Unless it’s the vast majority, the article’s quote still stands.
Anyway, on the other points, I don’t think we’re going to come to an agreement here. You seem to be defending the questionable behavior of a massive corporation, and I’m not buying that it’s all a big misunderstanding, a beta feature, just a bug, etc etc.
The fact remains that Microsoft has a long and sordid history of privacy violations and security lapses. You can choose to look past that and defend them, and that’s your choice.


Do you honestly and truly believe that nobody has ever analysed these packets? That nobody in any security position, especially in business, has ever checked if sensitive information wasn’t being transmitted? That the entire IT and Data Security world just goes “huh, I guess they’re spying on us, nothing we can do about it”?
Windows telemetry is encrypted, which as you can imagine, makes it hard to analyze.
Huh?
I don’t know exactly what that’s referring to, but maybe it’s the fact that some (not all) of the bullet points in this telemetry doc are super high level, leaving much to the imagination: https://learn.microsoft.com/en-us/windows/privacy/optional-diagnostic-data
Also, even if every last bit of telemetry was completely documented, that doesn’t make it cool to send all that information to a company known for abusing user data.
Oh yeah, Recall, the absolutely horrible… ummm… checks notes fully local and encrypted system… That isn’t even implemented yet… but when it is, you’ll need to manually turn it on…
Again, without source code, you’re taking Microsoft’s word about all of this. But let’s say it is 100% what they say. An earlier version leaked the user’s private information to other processes on the machine and failed to filter out sensitive user data. I have a hard time trusting an organization that is so clearly reckless like this. Either they don’t care about user privacy—or they do care and they’re just incompetent. I’m not sure which one is worse.
Have you read the article you linked?
Yup.


I can totally see that. Maybe it’s something to consider in advance for your next graphics card.




I mentioned telemetry because Windows (by default) regularly shares information collected from your computer with Microsoft. Some people try to work around that when they could instead invest that time elsewhere (say, installing Linux).


Call me crazy, but I get the sense that the same 0.1% of Windows users who jump through arcane command-line hoops to work around their anti-consumer OS would do just fine with Linux’s pro-user arcane command-line hoops.


I’m always amused at the hoops that some Windows users will jump through in a vain attempt to sidestep Microsoft’s telemetry and surveillance—rather than just using an OS that respects your privacy to begin with. It’s gotta be Stockholm syndrome or something.


deleted by creator


deleted by creator


deleted by creator


deleted by creator


Now if only they could work that magic on ICE and IDF. (Microsoft is in bed with both.)


deleted by creator


deleted by creator


deleted by creator
But what LLM wrote this?