You should not trust those builds. Everything you need to know is documented here: https://learn.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services

Windows 10/11 Enterprise is recommended as that’s the version where Microsoft can’t fuck up.

No, that’s a myth. Registry edits may revert in some cases yes, but group policy is different as it designed exactly to configure machines in a stable way.

Group policy may be beyond the general skill level, which makes the constant Linux suggestions even more laughable.

Ahaha yeah, I’ve said that SO MANY times. People have issues setting a few toggles on a point-and-click UI but then it is okay to suddenly move to a entirely different OS that most likely won’t have the software they’re used to and requires terminal skills to deal with most things. Laughable indeed.

Completely bullshit, garbage clickbait title.

Windows 10 is near EoL, however that’s for Home/Pro/Enterprise versions, you can move to one of those for more time:

• Windows 10 Enterprise LTSC - 2027
• Windows 10 IoT Enterprise LTSC - 2032

To be fair I don’t really believe that Microsoft will kill it when they say they will. And even if they do it, porting security updates from those LTSC versions into the regular ones might be doable.

Now on Windows 11:

You can just disable copilot and all the other garbage using group policy, now that hard and you’ll end up with essentially Windows 10. https://www.xda-developers.com/how-disable-microsoft-copilot/

Yes, I’m aware… however there’s nothing making it so we can’t port the directory listing from caddy (most likely just HTML/JS) into nginx. Or, someone might already have done it, I guess will have a look.

Yeah I would totally use that for nginx.

What software are you using on the server to list the directories?

So… if you go into North Korea for about two weeks you may end up becoming full communist. This is very inline with the recent headlines about China allowing people from certain countries to be there for 15 days without visas… hm…

AirPods work so… how much more proprietary can you get? :P

Yeah because apparently it is too hard to double click on setup.exe but using a docker is okay.

So, looks like tons of HTTP services and SSH.

Great, but what services are you hosting ? What ports you need?

Yeah, those may work. Since you’ve one how does it look like? Are there blocked ports line SMTP? Are the IP good / aren’t blacklisted everywhere already? Thanks.

Yeah, it may be less customizable but at least is fast and error free (unlike NextCloud)

Yeah, Incus FTW!!

Yeah because making it isn’t only about just waiting for time to pass and money to come it, it is also about compounding.

The thing with Ubuntu / Canonical isn’t that it doesn’t work, it is that they’ve bad policies and by using their stuff you’re making yourself vulnerable to something akin to what happened with VMWare ESXi or with CentOS licensing - they may change their mind at some point and you’ll be left with a pile of machines and little to no time to move to other solution.

For starters Ubuntu is the only serious and corporate-backed distribution to ever release a major version on the website and have the ISO installer broken for a few days.

Ubuntu’s kernel is also a dumpster fire of hacks waiting for someone upstream to implement things properly so they can backport them and ditch their own implementations. We’ve seen this multiple times, shiftfs vs VFS idmap shifting is a great example of the issue.

Canonical has contributing to open-source for a long time, but have you heard about what happened with LXD/LXC? LXC was made with significant investments, primarily from IBM and Canonical. LXD was later developed as an independent project under the Linux Containers umbrella, also funded by Canonical. Everything seemed to be progressing well until last year when Canonical announced that LXD would no longer remain an independent project. They removed it from the Linux Containers project and brought it under in-house development.

They effectively took control of the codebase, changed repositories, relicensed previous contributions under a more restrictive license. To complicate matters, they required all contributors to sign a contract with new limitations and impositions. This shift has caused concerns, but most importantly LXD became essentially a closed-off in-house project of Canonical.

Some people may be annoyed at Snaps as well but I won’t get into that.

Will they learn how to apply padding to stuff this time?

This means I don’t need to mess around with QBT’s “proxy” settings?

No, you don’t. In short, trackers will look at the source address of the incoming connection on their side, that means you VPS IP because you’re doing NAT on the VPS.

Just make sure qBittorrent is restricted to the WG interface and nothing else.

I agree with that, 100% but for the majority of the world how green it is usually depends on how far-left you are.