this post was submitted on 19 Apr 2024
124 points (97.0% liked)

PC Master Race

14977 readers
112 users here now

A community for PC Master Race.

Rules:

  1. No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
  2. Be respectful. Everyone should feel welcome here.
  3. No NSFW content.
  4. No Ads / Spamming.
  5. Be thoughtful and helpful: even with ‘stupid’ questions. The world won’t be made better or worse by snarky comments schooling naive newcomers on Lemmy.

Notes:

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 15 points 7 months ago (2 children)

Didn't they already do that? When you did a fresh install a couple years ago, there were already warnings that you should switch.

[–] Broken_Monitor 8 points 7 months ago (1 children)

Yeah, they made it obtrusive and difficult to setup local accounts. I think their whole system is confusing as fuck now, with PINs, windows hello shit, and a microsoft account password. I had to setup a whole new email just to get a kids account going, probably so they can track everything my kid is doing, which is downright creepy. So I tried to make a local account, but it seems like they’re still tracking that somehow anyway.

[–] CrayonRosary 3 points 7 months ago

Everyone using Windows should install a telemetry blocking program. This one just adds all Microsoft telemetry IP addresses into Windows Firewall with a "block" setting.

Just don't use the "Add update rules" feature because that blocks Windows Update. Just add the telemetry rules.

In addition, you can also change the IP address Windows uses for the "Am I connected to the internet?" test that Windows does all the time. Instead of letting Microsoft know every single time you boot your PC or connect to WiFi, you can instead have it check a Debian server. Or a Mozilla one, I think.

https://crazymax.dev/WindowsSpyBlocker/download/

[–] CrayonRosary 1 points 7 months ago* (last edited 7 months ago)

Oops, replied to the wrong person