Canonical's snap use a proprietary backend, and comes at a risk of vendor lock in to their ecosystem.

The bash installer is fully open source.

You can make the bad decision of locking yourself into a closed ecosystem, but many sensible people recognize that snap is "of the devil" for a good reason.

I've tried snap, juju, and Canonical's suite. They were uniquely frustrating and I'm not interested in interacting with them again.

The future of installing system components like k3s on generic distros is probably systemd sysexts, which are extension images that can be overlayed onto a base system. It's designed for immutable distros, but it can be used on any standard enough distro.

There is a k3s sysext, but it's still in the "bakery". Plus sysext isn't in stable release distros anyways.

Until it's out and stable, I'll stick to the one time bash script to install Suse k3s.

I actually tried this right after I made this post, and it was not where near as smooth as I wanted. KDE would put the window that I had assigned to all desktops on top, whenever I would switch virtual desktops.

I found a solution though, it looks like mpv has support.

Maybe nginx proxy manager can do this.

https://nginxproxymanager.com/

I'm not spotting it. "AI" is only mentioned once.

The key and secret in the docker compose don't seem to be API keys, but keys for directus itself (which upon a careful reread of the article, I realize is not FOSS, which might be anpther reason people don't like it").

Directus does seem to have some integration with openai, but it requires at least an api key and this blog post doesn't mention any of that.

The current setup they are using doesn't seem to actually connect to openai at all.

There’s only one project that provides truly static/relocatable python that work on both glibc/musl: https://github.com/leleliu008/python-distribution

There is the python provided by APE/cosmo. They also have two other distributions containing various goodies, pypack1, and pypack2. https://cosmo.zip/pub/cosmos/bin/

But this came at the cost of discontinuing support for Android & Windows

I don't care about android support, but for the competition, and I don't really know about Windows support. Right now, RDP is used to authenticate and managed the machines, but maybe a portable VNC we can quickly spin up, so more than one person can be on the same machine, would be useful.

My original thought was to replace in place, insecure services with secure one's via something like docker containers or nix. But I think many of the machines have too little ram bundled libraries for the services to be viable. I actually tested replacing apache, but it simply wouldn't launch (I think the machine only had 2 GB of ram?).

https://games-on-whales.github.io/

https://github.com/giongto35/cloud-morph

Doesn't fedora use zram by default nowadays?

From what I've heard, true multiseat is very to configure. You probably also want to investigate using GPU accelerated containers, because it's legitimately easier to share the same GPU across multiple containers as opposed to multiple seats.

You cannot run a GUI in LXC

It's probably possible, especially considering lxc can run systemd nowadays, and I can find many sources on this, for GUI and for GPU acceleration (but not in proxmox):

https://stgraber.org/2017/03/21/cuda-in-lxd/

https://blog.simos.info/how-to-run-graphics-accelerated-gui-apps-in-lxd-containers-on-your-ubuntu-desktop/

And then there are also technologies like KasmVNC which can serve a GUI as a website, and it doesn't need a GPU at all.

EDIT: Two year old guide, but a redditor pulled it off

https://linuxgamingcentral.com/posts/steamos-getting-nix-support/

Dunno if this ever came to fruition though.