I’d just delete older stuff you’ve already watched, unless it’s something you plan on re-watching at least.

Proxmox has a UI for ZFS. But you don’t really need it, ZFS is kind of set and forget and setting it up is quite easy via CLI.

Crowdsec does everything fail2ban does so not much point.

You can analyze with either the CLI or log files piped into something like OpenObserve which is what I do. You don’t technically need their dashboard.

RClone maybe? https://rclone.org/

There are some open source rclone android apps like RCX, and on windows/linux you can just use rclone mount to use it like a normal filesystem.

I do worry.

Technically right now the age thing in systemd is just a stored field that you can set to anything easily. In its current form pretty benign and not a privacy issue.

But it almost always gets worse and more and more controls get added, until we’re at face verification services and other privacy invasive stuff.

Komodo.

Technically you only need 1 interface when using VLANs. Basically any device with a CPU and NIC can be a router.

An SSL error is expected because you’re using localhost and not the common name that the cert is issued for. But the fact that it’s connecting and showing the error means the server is working.

Start with basic diagnostics, see if apache is running inside the container, if it is can you curl from inside the container, if that works can you curl from the docker host, if that works did docker create the firewall rule to expose the port or is the VPS overriding things in some way?

If that all looks good, is there a VPS provider firewall in place outside the OS?

Gotta start with the basics.

Android has a huge market share compared to iOS, plus it’s a lot harder to develop these types of applications for iPhone because of apples policies.

Windows sandbox is easy.

A gaming focused distro will do everything else well too, so thats probably why.

If Linux is going to be usable by the average person on windows it needs to do something better than booting to a CLI and making the user figure out how to manually downgrade a package.

Sorta, but you run one command to update everything at once, and even though the system knows what GPU you have it still seems to update the driver to one thats not compatible, instead of holding that update back.

Also if it didn’t warn the user when updating, the user had no idea they were pulling any trigger, especially when Linux falls back to CLI after this instead of just falling back to a basic driver.

Surely there’s a way to keep the older driver on Linux, its absurdly easy on Windows.

Windows doesnt drop to CLI and break if the graphics driver is missing. But also GPU driver updates are not forced on you just by updating the system.

It makes me wonder why the package still auto updates if it detects you’re using the driver that would be removed, surely it could do some checks first?

Would be vastly preferable to it just breaking the system.

Windows doesn’t force update your driver and remove support though, and even if it did it won’t drop you to some CLI, it will still work.

Gotcha, that does make it significantly more difficult to block outgoing connections from some new executable, as most are likely to use port 443 like everything else does.

I’ll have to research some more, I have Fedora on my laptop and it would be nice to have a comparable firewall.