This has no relevance to politics and I’m not attacking anything by saying forcing sign ups is a barrier to content or that you’re wrong about it having anything to do with bots, you dork.

No it isn’t, they are letting bots scrape the articles just like every other news site for that sweet, sweet SEO. Why do you think the archive.is link has the full article?

Still a wall between people clicking the link and the content.

I’ve never used EndeavourOS or Manjaro, but if you’re looking for something similar to Bazzite (gaming-ready, not immutable) and Arch-based I’d check out CachyOS. I’ve been using it for a good while now and I really like it.

That reddit thread is horrible advice, it’s just mapping the LXC root user to the host root user, which is just a privileged LXC with extra steps (and maybe less secure).

The reason you’re probably having issues is that your root user in the LXC is mapped to the host user 100000 by default, and that user doesn’t have access to the share, but you can change that with mount options or creating a user with 100000:100000 and adding it to a group with access.

I use Tautulli, but I’m not sure if that is going to cover all the same use cases.

For anything. You can get a push notification for anything you can make run a script or send an http request.

I use it for when I’m finished with a game or haven’t played it in a while and want to declutter my SSD. It copies my saves and settings to my NAS and then I can just delete everything and restore it later if I want.

I used gamesave manager for the same thing in my windows days.

To get to a bash shell from fish all you have to do is type bash. The prompt should change and you can try your command again. I don’t use distrobox, are you running that command inside the container? Could be your path variables are set in .bashrc and distrobox is trying to keep your same shell in the container.

You could also try dropping to a bash shell before accessing the container’s shell, and that might do it.

Just run docker in an LXC. That’s what I do when I have to.

I’m not really worried about it. Each LXC runs as its own user on the host, and they only have access to what they need to run each service.

If there’s an exploit found that makes that setup inherently vulnerable then a lot of people would be way more screwed than I would.

I don’t have anything publically accesible on my network (other than wireguard), but if I did I’d just put whatever it was on its own VLAN, run a wireguard server on it, and use a VPS as a reverse proxy that connects to it.

I only use unprivileged LXCs and everything I host on my network runs in its own LXC, so I’m not really worried about someone getting access to the host from there.

I like the workflow of having a DNS record on my network for *.mydomain.com pointing to Nginx Proxy Manager, and just needing to plug in a subdomain, IP, and port whenever I spin up something new for super easy SSL. All you need is one let’s encrypt wildcard cert for your domain and you’re all set.