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)

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 any tunnel because it’s a direct connection between the two peers - it’s not relaying through an intermediary server like a Cloudflare tunnel would.

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 rather than just on the router, since this takes advantage of its peer-to-peer nature. Tailscale makes it a lot easier to configure it this way though - it’s a bit of work for vanilla Wireguard.

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.

If you have a separate subnet for it, then why do you only want it to be connected when you’re not on home wifi? You can just leave it connected all the time since it won’t interfere with accessing anything outside that subnet.

One of the main benefits of Wireguard (and Tailscale) is that it’s peer-to-peer rather than client-server. You can use the VPN IPs at home too, and it’ll add barely any overhead.

(leaving it connected is assuming you’re not routing all your traffic through one of the peers)

In countries like Australia that have good consumer protection, they’d have to replace failed CPUs even outside of the warranty period, because they’ve still failed in a time frame shorter than a regular person would expect a CPU to last. The USA really needs better consumer laws.

The majority of users aren’t contributors though. It’s fine to mention it in contributor documentation but I find it weird to advertise it as an end-user feature given most apps written in other languages don’t do this.

It’s also a floating signifier for a lot of things.

Like what?

conditional Auto-Connect. If not on home wifi, connect to the tunnel.

You don’t need this with Tailscale since it uses a separate IP range for the tunnel.

Yeah my wife and I are both on Android, and I haven’t been able to figure out why it does that.

The Android client is open-source so maybe someone could figure it out. https://github.com/tailscale/tailscale-android

deleted by creator

small minority of Rust programmers who are very loud

They also list “written in Rust” as the primary feature of software they write, even though the majority of users don’t care as long as it works properly.

and they kept denying there was an issue, until there was so much proof that they couldn’t deny it any more and were like “okay fine there’s an issue so we’re going to be extra generous and extend your warranty one whole year”

flavors of iron

Yum yum

Is it just you that uses it, or do friends and family use it too?

The best way to secure it is to use a VPN like Tailscale, which avoids having to expose it to the public internet.

This is what I do for our security cameras. My wife installed Tailscale on her laptop and phone, created an account, and I added her to my Tailnet. I created a home screen icon for the Blue Iris web UI on her phone and mentioned to her, “if the cameras don’t load, open Tailscale and make sure it’s connected”. Works great - she hasn’t complained about anything at all.

If you use Tailscale for everything, there’s no need to have a reverse proxy. If you use Unraid, version 7 added the ability to add individual Docker containers to the Tailnet, so each one can have a separate Tailscale IP and subdomain, and thus all of them can run on port 80.

That and email protocols are outdated and aren’t too secure. For example:

• Neither SMTP nor IMAP have no way to use two factor authentication.
• Spam blocking is so hard because SMTP was not designed with it in mind.
• SMTP has no way to do end-to-end encryption which is why you need to layer things like GPG on top.

IMAP has a modern replacement in JMAP, but it’s not widespread. SMTP is practically impossible to replace since it’s how email servers communicate with each other.

The “solution” has been for companies to make their own proprietary protocols and apps, for example the Gmail and Outlook apps combined with a Gmail or Microsoft 365 account respectively.