Pretty much, yeah

I assume the equivalent would just be ‘takeown /r <folder>’

As far as I can tell it always uses the currently logged in user as target though

It’s quite common to login as admin on windows though (in home setups), you’ll still have to authenticate for administrative tasks (the UAC popups).

The issue here is mostly that the user has probably upgraded and windows changed their account, resulting in the files being owned by their old account.

In linux, that’s fixable with ‘sudo chmod -R’

In Windows, there’s no built-in way, you need the take ownership script.

Here’s some hints:

Another word for athletic is “Fit”

Reducing the size of installers is done by “Repacking” its contents.

.eu and your local tld are often quite a bit cheaper too!

So why not use forejo, which is completely open source?

If your criticism is MS pulling the plug, then Gitlab pulling a Redis/Hashicorp move and re-licensing their core should also be a concern

Because my pc uses 4-5 times the power to run the same ps4-era game. (Especially nice when it’s hot in summer)

So I play it on my ps5, which offers me quick resume as well.

I love pc gaming, been building pc’s for over a decade at this point, but I do also see the advantages my ps5 has over my pc.

Could I build a more efficient and quiet pc, attach it to my tv and use that? Probably, and it’d be quite good with steamOS on it, but it’d be finicky to get sleep/resume working on it, and it’d probably cost me more.

Wireguard (which is what tailscale is built on) doesn’t even require you to open ports on both sides.

Set up wireguard on a vps first, where it is accessible, then set it up from within your network. It’ll traverse NAT and everything, and you don’t have to open a port on your network.

Tailscale is the exact same thing, just easier because it does everything for you (key generation, routing, …). Their service replaces your vps, up to you if you think that’s acceptable or not. IMHO, wireguard is worth learning at least. I eventually (partially) switched to tailscale because I’m lazy, and all services I host have authentication anyway, with vpn just being a second layer.

I’m confused - does it explicitly ask you now?

I’ve had firefox as default for a while now

it’s still comically bad compared to various alternatives, even apples-to-apples alternatives like C#.

I’d be interested to hear why. IMO Java has the superior ecosystem, runtime(s!), and community. The best part is that you don’t even HAVE to use java to access all this - you can just use kotlin, groovy, scala,… instead.

In terms of the language itself, while it (still) lacks some more modern language features, it has improved massively in that area as well, and they’re improving at a significant rate still. It also suffers from similar issues as PHP, where it has some old APIs that they don’t want to get rid of (yet?), but overall it’s a solid language.

And the people hating on it somehow never used any version above 8, which is 10 years old and EOL.

Kubernetes yes, but minikube is kinda meh as a way to install it outside of development environments.

There’s so many better manageable ways like RKE/Rancher (which gives you the possibility to go k3s),Kubespray or even kubeadm.

All of those will result in a cluster that’s more suitable for running actual workloads.

The difference being that when you’re 10 billion into a renewables project, you usually have SOME generation already, whereas your nuclear reactor isn’t doing shit until it’s fully completed.

I don’t mind nuclear, but the fact is that the reactors take decades to build, whereas renewables can be deployed far quicker. Going all-in on nuclear, and then twiddling your thumbs for 10-15 years while the reactors are built doesn’t sound like a great idea.

I don’t think programming language is a good metric for security. I assume everything I host has issues, and then try to mitigate from there.

IMHO, a better approach is to vet the project beforehand, looking at whether it is still actively maintained. I usually use things like commits, issues, etc to try and gauge whether a piece of software is actively maintained so that when an issue arises, it can be fixed.

You can mitigate much of the risk by using some basic best practices, like isolating all apps from each other (using docker, for example), using a reverse proxy, tools like fail2ban or a web application firewall, using proper database permissions for each app, etc

What I also do is add another layer by making certain applications accessible only over vpn. That won’t work for some tools, obviously, but also reduces the risk for tools you are only using yourself.