Keep in mind that in practice this didn’t work that well, it wasn’t very efficient at displaying modern interfaces over the network. Showing a simple text editor over LAN worked fine, but using Firefox from another place was quite spotty.

That actually seemed quite useful at first.

It works well when you want to install software that is not compatible with your distro, but it is not a great security measure since it integrates with your host system instead of acting as a sandbox.

Isolation and sandboxing are not the main aims of the project, on the contrary it aims to tightly integrate the container with the host. The container will have complete access to your home, pen drive, and so on, so do not expect it to be highly sandboxed like a plain docker/podman container or a Flatpak.

This is just incorrect

…or containers, e.g. Docker/Podman

Distrobox is a script that manages Docker/Podman containers

What you are installing can cause damage so IMHO it’s more about keeping things manageable while having your actually important data…

Programs are installed the container, not on the host system. When you break the container the host system is fine unless using rootful (or Docker) containers.

…while having your actually important data (not programs, downloaded content, etc but rather things you did yourself, e.g. written documents, sketches, configuration files, prototypes, photos, etc) safe…

Using Distrobox does NOT keep your own files safe, it actually mounts your home directory and external USB drives inside the containers by default fully exposing your documents to whatever you install inside.

From the documentation:

Isolation and sandboxing are not the main aims of the project, on the contrary it aims to tightly integrate the container with the host. The container will have complete access to your home, pen drive, and so on, so do not expect it to be highly sandboxed like a plain docker/podman container or a Flatpak.

Equinix seems to be shutting down their bare metal service in it’s entirety. All projects using it will be affected.

A system daemon to allow session software to update firmware

(In case I’m in the only one who hasn’t heard of it)

I tried this a while ago in combination with tailscale, exposing the VPN as an exit node. However, I found the performance to be problematic.

Paid apps are in the works right?

Linkwarden can manage links and automatically archive the page as PDF, image, and/or HTML/CSS

You could turn it into a Home Assistant control panel if it has touch screen support

FYI, the repo has been moved and the link is outdated

Why does it list Gitea instead of Forgejo?

Is it though?

EDIT: The about page doesn’t mention it being related

I think it would be better to send a message after 1 month of inactivity, have the bot ask if the issue can still be reproduced with the latest version and then repeat every N months.

That’s indeed a Plasma thing

Cockpit’s GUI can only manage individual containers, not stacks

I recommend going with Debian (without desktop) and Docker compose. You can use something like Dockage to make it easier.

Snap is also useful for server software and it can apparently be used for more low level things such as drivers. Still, it being properiatary is enough for me to avoid it completely.

I’m guessing it’s like the definition used by the Cloud Native Computing Foundation since some Bazzite members apparently worked there.

What are you running on it?