Only because I don't want to be mistaken for a policeman.

Exactly. IMDB assigns an identifier to each piece of content, and Plex (or Jellyfin/Emby/etc) use that to pull metadata.

You could do it on the NAS. Qbittorrent is probably the highest-recommended client right now, and it has a web UI that can be accessed from any other device on your network.

That said, I run one of the tiny Thinkcentres as a dedicated torrent and *arrs box. I think I paid $30 for that one, and it has more than enough power for the task.

Jellyseerr doesn't do music, but Ombi does. I run them both, with Ombi set for music only.

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.

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.

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.

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.

I'd call that a downgrade from CLI pacman and yay (AUR). They're already simple to use.

The only way it makes sense is within the same facility. You could use water or refrigerant in heat exchangers, and run insulated lines to other parts of the building. Wouldn't do too much, but might see a slight reduction in heating costs.

The problem with a bigger pack would be weight. The current packs are usually 4-8lbs each and only run for 30-60 minutes. A scaled up backpack that would fit a landscapers needs would be 50-60lbs.

Demand means nothing if battery tech isn't there yet. We need lighter cells with higher capacities first.