CalicoJack

Frequent enough that I've gone back to LL, even though I like Readarr better when it works. Goodreads isn't going to change the API, Readarr probably isn't going to change providers.

You have some options here. Your new internet doesn't mean you can't torrent from home. If you're using a VPN (you really should be) then your ISP port forwarding doesn't even matter. You just choose a VPN provider that offers port forwarding on their end, like Proton, and use that port for qbit. The only real advantage to setting up at your parent's place would be if their connection was faster or more stable.

As for the server, the arrs can handle everything. They have settings (off by default) to rename and tag all of your files, based on rules you define. It's pretty easy to set it up to fully automate all of that processing busywork, so you just request things and wait for them to show up in Jellyfin.

Look into Caddy instead if you just need something simple for outside access. All you need is a DynDNS service (duckdns is easy), a few lines worth of Caddy config to point that address to your internal ports, port forwarding 80 & 443 to the machine running Caddy, and you're good to go. If you follow the documentation, you'll be running in 10 minutes.

These days, I'm partial to EndeavourOS with KDE for those kinds of installs. It's still Arch underneath, and I don't mind a "lazy" install for a DE.

It also gives you several DEs to choose from during install, so you can take your pick.

Yes, that's how it's supposedto work if they're all on the same Docker network (same yaml). In practice, it can be flaky and you're much better off using ip:port.

The VPN is for a torrent client. No need to worry about streaming services when you're sailing the high seas instead.

If a sysadmin expected me to use vim for every minor config tweak, I wouldn't want to be on their machines either.

Docker is a cleaner solution for split tunneling. Container for the VPN (gluetun), and container for qbit bound to the VPN container for network access. You still need to manage the listening port when Proton changes it, but that's easy enough.

If you set it up right, it also doubles as a bulletproof killswitch since qbit can't see any other network.

They absolutely design cars with some pedestrian safety in mind. That's why hood ornaments went away and bumpers moved away from solid steel.

I don't remember the exact numbers, but they have a metric along the lines of "X% of pedestrians survive impacts up to Y speed" that they need to meet.

You can get Usenet very cheap. I pay $6/month (less than my VPN for torrents), but there are cheaper options available. And it's worth every penny. Downloads are much faster, more content is available, no dead links, no share ratios to worry about, no VPN needed, the list goes on.

It does feel kinda silly paying money to pirate, but you get over that as soon as you start using it.

Arch has been daily driver for years, I'm already familiar with the process. There's an option for a guided system. The default is a terminal with no guidance.

That's only if you use an automated script, and only if it works. 'Default' install is almost entirely manual, other than letting pacman grab what it needs to.