dan

The drivers have gotten a lot better over the last few years, and Nvidia even have an official open-source driver now, but there's still issues with them. Wayland works very well now, but not perfectly (especially on GPUs with low VRAM).

If you're on Linux and are buying a new GPU, stick to AMD. Their driver is part of the Linux kernel, it's more stable, and it gets all the newest features first.

install newest proprietary nvidia drivers

On newer cards, the open source drivers work pretty well as of version 555. The process for installing them is usually very similar to the proprietary drivers, but there's often some flag you need to set to tell it to use the open source ones instead. For Fedora, the instructions are here: https://rpmfusion.org/Howto/NVIDIA#Kernel_Open (ignore the part about it only working for data center GPUs, as that's no longer true)

sudo sh -c 'echo "%_with_kmod_nvidia_open 1" > /etc/rpm/macros.nvidia-kmod'
sudo akmods --kernels $(uname -r) --rebuild 

If you use Nvidia's installer, it automatically uses the open source driver instead of the proprietary one if you have a new enough GPU (20 series or newer)

Nvidia has helped the Nouveau devs by answering questions in the past, but they also have their own open source driver here: https://github.com/NVIDIA/open-gpu-kernel-modules

There's no reason your media server needs to be directly exposed to the public internet. Use Tailscale. Get everyone that uses it to sign up for a Tailscale account, and add them all to your Tailnet.

Tailscale will perform better than a Cloudflare tunnel because it's a direct connection between the two peers, whereas Cloudflare tunnels route through Cloudflare.

Tailscale does have relay servers, but they're only used in very rare cases, if both peers have very strict firewalls. Almost always, the connection between two peers over Tailscale is a direct connection, so there's no extra latency (other than some small overhead for the encryption)

You could use Wireguard and manually configure it to be in a mesh config, but Tailscale makes it so much easier. I'm a big fan of their product.

But for there to be used cars, there needs to be new cars... How do the people that buy new cars pay for them?

This just hides the menus. They can still access all of Home Assistant.

I loved the explosion sound, and the "oh no" when you click the undo button. I have the Windows versions of KidPix on CD somewhere.

I don't see any mention of torrents in the article?

Oh yeah, there'll be some overhead if you're running Wireguard on a router. Hitting your router's public IP won't go out to the internet though - the router will recognize that it's its IP.

It's common to run Wireguard on every computer/phone/tablet/etc where possible rather than just on the router, since this takes advantage of its peer-to-peer nature. For home use, that's how it was originally designed to be used. Tailscale makes it a lot easier to configure it this way though - it's a bit of work for vanilla Wireguard. Tailscale does support "subnet routers" if you have any devices that you want to access over the VPN that can't run Tailscale.

Most of those points are true for programs written in Go too, and C# (if you use Native AoT).

My point is that since the VPN uses a different subnet, it's fine to keep it connected even at home. It'll only use the VPN if you access the server's VPN IP, not its regular IP.

In any case, Tailscale and Wireguard are peer-to-peer, so the connection over the VPN is still directly to the server and there's no real disadvantage of using the VPN IP on your local network.

Yeah, this. Plus if you leave it connected, you can use the VPN IPs while at home instead of having to use a different IP when at home vs when out (or deal with split horizon DNS)