But then you cannot scale.

You do not see the problem because you probably manage less than 5 nodes.

Because you can't mesh at scale with wireguard (unless you have an infinite amount of monkeys).

Try to build a mesh with wireguard.

You will soon find you have a combinatorial problem. If you have 10 nodes and want to add an 11th node, you will have to update the 10 already existing nodes.

These projects are automating the configuration of the nodes. You simply configure a new node and the other nodes are informed of the presence of the new guy.

I’ve built a 3 node wireguard mesh network, by hand, and it did get tedious!

Please, elaborate or provide sources.

Same here. Nebula might not be wireguard based, but it is open source and very stable.

Though, I have to say that if you are using Nebula within a LAN it sometimes takes minutes for two nodes to realize they are within each other's reach. In the mean time, they talk through the lighthouse which can severely affect performance.

Where did you study?

20 years ago, I was doing computer engineering in Canada and neural networks were not sold as a dead end. It was made clear they were a very powerful tool.

Not neural networks in general, multilayer neural networks as they were called then ("deep" now). This was self-study but I did read widely on the topic and that was the general consensus.

The doc you linked to specifically says there is no daemon on Windows and Mac.

I am confused.

The podman CLI tool compiled for mac doesn't allow you to run the daemon on macOS natively.

The way podman desktop works includes running a podman daemon by default inside the podman linux VM. That's the daemon I'm talking about.

The docker cli also runs on mac, but the docker daemon doesn't run on macOS directly, but instead as a daemon inside the linux VM.

Hence, in podman desktop on macOS, just like docker desktop on macOS, you have a similar daemon running inside the linux VM that's launched.

Do you understand now?

Are you sure the podman machine's VM is running as root?

Kinda, a bit, it's hard. So podman will need virtualisation and networking permissions to do its job. Also the directory mapping seems to work without extra confirmation. At that point, who needs root? You control the main user`s files, networking, and can effectively hide any process from easy inspection by using virtualisation.

If you need someone to physically check on you to keep you accountable, you have a problem and should definitely work at the office.

Don't poison the lives of the ethical workers that are productive from home.

Amusingly, I keep hearing from a loud minority that return to office is required because it will magically enhance productivity.

They never provide numbers.

Well, that depends on your null hypothesis. Most of the decision makers in corporate America know what in-office environment is, they have risen through it. So they don't need any more data about it.

Remote work is a new paradigm which needs heavy investment in rewiring the culture of work. Obviously, the burden of proof is on remote work to prove it's utility.