There is no such thing as easy or hard.

Give it a try, fuck it up, and give it a try again. Try not to fuck it up in the same way as the first time. Repeat until it works - it will work eventually.

It took me about 6 hours and 3 disk re-formats my first time. I was particularly bad at it. I barely knew what a disk was, nevermind a partition.

Actually I’m still not sure what a partition is.

You’ll do fine :)

Use network namespaces :)

A brand new network namespace doesn’t have any network interfaces. When you start a process in a namespace, all its child processes will start there too. It’s like a little network jail, and the functionality is baked into the kernel / is kernel enforced.

I use this to keep certain processes on a vpn, with no need for interface-binding support from the process, or a vpn-killswitch.

Another fun fact, this is the functionality that enables containerization, like docker/podman

I strongly recommend the NAT loopback route over attempting split-horizon dns.

If youtube manages to stop fast forwarding, maybe at the very least we could auto-mute, and maybe overlay photos of puppies or something

At what point does a collection of microservices become a monolith that uses http instead of a bus 🤔

Helix + vim => Helim => Helium?

Vim + helix => velix / vimix / vix / velimix?

Tailscale might be the best bet at this point. It will manage the wireguard mesh for you, and use nat holepunching for handshaking instead of needing listening ports.

I love i2p. I wish it had more adoption / was easier to use.