Found memories: and the memories are French.

A province in the Netherlands. Lots of sea there; translates “sea land”.

https://en.wikipedia.org/wiki/Zeeland

Zealandia is not old Zealand… The name comes from a province in the Netherlands.

https://en.wikipedia.org/wiki/Zeeland

https://en.wikipedia.org/wiki/Zeeland

They’re deadly serious. Every Linux is the wrong Linux.

BSD is the only way.

(hears the rumble of the hurd in the distance)

Ah- then I have to dispute your theology on daemons.

WSL and Android, then?

I suppose, in fairness, climbing the top part is a bit harder than climbing the bottom part.

Though, if you think about it, quite a lot quicker.

I have heard the (Nepali-speaking) Nepalis didn’t even have a name for it at that point, and I have a feeling Qomolungma wasn’t known to the Brits, because the mountain was surveyed from far away at that point.

Incidentally, “Tibetans and Nepalis on either side of the mountain”- it’s Tibetans on both sides. On the Nepali side are the Tibetan group known as Sherpa, whence we get the term Sherpa for a Nepali/Tibetan mountain guide. Further south than the Sherpa people are ‘Nepali’ people by ethnicity. (And of course properly there’s a lot more than two ethnic groups in a cross section of Nepal!)

But what is the base?

Thing is, that’s a more complicated question than it sounds.

Don’t forget the multi-million-dollar marketing campaign and funded research to convince the public it’s no different to, or even better than, real lemonade.

Ok

They pass TCP over UDP.

I took a quick look at the GitHub repo - selfhosted Netbird looks harder and more resource hungry, not easier! At least compared to Nebula.

Wow, self-hosting Netbird is a lot more involved than Nebula, and needing a lot more resources!

Isn’t that the same with all of them? Using UDP so they can tunnel between machines that are both behind NAT?

Thank you, that’s helpful. I’ll look up Authentik.

And yet you’re posting from lemmy.world …Are you a bot?
/s

1. Biggest thing was actually the sign up options. What if I don’t want my machines calling to Google or Microsoft to get access to Tailscale? I need to look up the other OIDC providers but don’t know much about that yet.
2. Then the fact of Nebula being fully open source and fully on my machines. (Though that’s a little undercut by the Android problem being solved only by their managed service).
3. Headscale gave me an impression of being more complicated to set up and maintain. Haven’t tried it yet, that was just my feel when I chose which one to try.
4. More recently, I saw Nebula’s interesting post on performance benchmarks. At high throughout Tailscale can be better for CPU but heavier on memory. Hopefully at my sort of very low throughout it’s small on memory but if I’m squeezing a client into a cheap vps alongside nextcloud and other things, memory use is more concerning to me than CPU… I wonder how much memory Tailscale uses when not doing much.

Does Tinc have advantages over Nebula? I was under the impression that both Nebula and Tailscale improved on Tinc, albeit in different ways.