The Copilot integration they recently pushed to 11 says otherwise. They’re going hard on AI moving forward.

It reduces your available peers. You can’t connect to other people with closed ports, one side needs to be open.

It isn’t a huge deal with popular torrents, but it can cause problems with unpopular/old stuff.

You can get a USB IR receiver and use software like LIRC to map the inputs of basically any remote you have. Setting it up takes a little effort, but it works great when it’s done.

grml-zsh-config is its name, and it’s always one of the first things I install on a fresh system. I’ll never understand why it isn’t the default.

I would sell a few of them to shore up the budget, then use those funds to build a NAS box. You can buy everything other than drives for a few hundred, less if you have spare parts sitting around.

This is the fucking dream. Lidarr is serviceable to get a library going, but we could do so much better.

Lidarr is the corresponding program for music, setup is almost identical to what you’re already running. And if you use Prowlarr to manage your indexers, it also works with Lidarr.

If you go to your torrent client and disable the missing file, it should get reported as “complete” to the *arrs. Manual and annoying, but it works.

Exactly. Doesn’t matter if they’re wired or wifi, or where they are, as long as they’re on the same network you’re fine.

If you’re only trying to use Jellyfin at home, you don’t need any reverse proxy or domain. All you need is for both devices to be on the same network, and for the Raspberry Pi to have a fixed internal IP address (through your router settings).

On the Shield, you just give the Jellyfin app that IP address and port number (10.0.0.X:8096) to connect and you’re good to go.

You don’t even need to purchase a domain, free dynDNS services (DuckDNS or similar) are good enough for Jellyfin and the like.

For a NAS, you’re usually concerned with capacity first. And you can’t buy a 20TB m2.

I’ve had this happen a couple times, and contacting the seller directly has gotten it sorted out. Even if they seem sketchy, they don’t want to take a hit to their reputation. If they don’t want to help, I’d escalate to eBay support.

If neither of them work out, then I’d try contacting WD. A refurb with no warranty is better than nothing at that point.

A Zero would probably be way underpowered for the job. I’ve used a Pi 4 in the past and it worked ok, but choked occasionally.

My actual recommendation would be a small x86 box, something like a Lenovo Thinkcentre Tiny. You can get them used for about the price of a Pi, and they’ll be much more reliable.

It isn’t just the cover art, they also A/B descriptions. And some of them are so different they’re basically lies.

Automating updates is generally frowned upon, that’s when things can break. But waiting to run updates until you feel like it (instead of daily) is totally fine. I’ve been using Arch and its forks for years, and have always updated once a week unless something was wrong.

The devs have stated otherwise. The project was originally announced on an Arch Linux forum, so they included a nod in the name.

It isn’t recommended, but dpkg will install it if you really want to. You just need to handle dependencies manually.

But it’s a pretty rare issue. If something isn’t available in the official repo, AUR probably has it.

Same here. But on the bright side, at least data hoarding doesn’t take up a ton of physical space.

If you’re comfortable, you’re fine. Anything more would just be to speed up the rebuild, so it’s less important if you don’t mind taking the time.