Real-debrid does filtering based on the torrent name. Media uploaded to usenet is already obfuscated and split into many tiny pieces, the location of which are stored in a .nzb file.

This means eweka can’t filter downloads based on the title. Once media companies get a .nzb file, they can use copyright infringement notices to make usenet providers delete the files, but that does not work preemptively (like filtering based on torrent name).

I remember taking my first selfhosting/Linux steps a year or so after the launch of Let’s Encrypt with a Pi 3. At the time, most tutorials didn’t set up https at all, and if they did, they were self signed certificates (resulting in browser warnings).

Self-signed certificates are annoying and creating them was a series of copy pasting long, weird commands, usually using long exspiration dates (manual renewing sucks).

Not long after, guides started recommending certbot. Nowadays reverse proxys like caddy set up TLS automatically.

At least that’s how I remember it, given my complete lack of knowledge about Linux at the time.

I don’t like playing with Bluetooth controllers. It’s not necessarily the amount of input latency but the inconsistency of it.

For having fun with friends Bluetooth is fine, but if possible go for a cable instead.

That said, there’s the XBox Wireless Dongle which uses the same protocol as an XBox. The latency is minimal like a cable, and it does support up to 8 XBox Wireless Controller.

Sadly the Linux support isn’t perfect but the xone kernel driver sees regular development.

https://github.com/medusalix/xone