Dran

I think that holds true in this case… but I’ll be damned if the ltt screwdriver isn’t the best hand tool I’ve ever owned.

Thank you for letting me know what software not to use; good bot

Crossfading and normalization would both independently be dealbreakers for me. I can’t go back

I would be genuinely surprised if fair use draws the line on format-shifted, legally purchased media, at “remote watch-together”, leaving format-shifting and local watch-together in-tact.

If it were up to the studio’s interpretation of the law, you’d need to purchase a license for each person during local watch-together.

agree in principal, but in practice:

1. parents who live across the state

2. plexamp for music

They are indeed just that keen on our data.

They know they can’t get rid of it for all of their customers, but they do want to make it as hard as possible for random users to do so.

The problem with this is it doesn’t work for home users that want to pay for their software. Crazy… I know… but those people do exist.

For people with “that one game” there is a middle ground. Mine is Destiny 2 and they use a version of easy anticheat that refuses to run on Linux. My solution was to buy a $150 used Dell on eBay, a $180 GPU to be able to output to my 4 high-res displays, and install Debian + moonlight on it. I moved my gaming PC downstairs and a combination of wake-on-lan + sunshine means that I can game at functionally native performance, streaming from the basement. In my setup, windows only exists to play games on.

The added bonus here is now I can also stream games to my phone, or other ~thin clients~ in the house, saving me upgrade costs if I want to play something in the living room or upstairs. All you need is the bare minimum for native-framerate, native-res decoding, which you can find in just about anything made in the last 5-10 years.

Fail2ban and containers can be tricky, because under the hood, you’ll often have container policies automatically inserting themselves above host policies in iptables. The docker documentation has a good write-up on how to solve it for their implementation

https://docs.docker.com/engine/network/packet-filtering-firewalls/

For your usecase specifically: If you’re using VMs only, you could run it within any VM that is exposing traffic, but for containers you’ll have to run fail2ban on the host itself. I’m not sure how LXC handles this, but I assume it’s probably similar to docker.

The simplest solution would be to just put something between your hypervisor and the Internet physically (a raspberry-pi-based firewall, etc)