It clearly says iNOME O.

GNOME OS is a distro for testing out GNOME technologies and isn’t intended for daily use.

!fuckcars@lemmy.world

Additionally you could move the git folder to the trash folder. I think it’s usually located at $HOME/.local/share/trash/files/

Moving something to the trash files folder isn’t the correct way to trash it, since the Trash specification requires storing some metadata for each trash item.

You should use eg. trash-cli instead.

I don’t think they state anywhere that they adhere to semantic versioning.

https://stashapp.cc/

Please read the warning at the top of their page:

⚠️ The project is under very active development. Expect bugs and changes. Do not use it as the only way to store your photos and videos!

If you don’t like these breaking changes, this might not be the right software for you (for now).

bwrap wants to have a word with you

they are extra heavy in disk space

While they use more disk space than most native packages, this point is often exaggerated. Flatpak uses deduplication and shared runtimes if multiple apps use the same runtime.

Common libraries like OpenSSL are usually bundled in runtimes. So if my application uses e.g. org.gnome.Platform, I don’t have to update my application if there is a fix in a library of that runtime, I just need to update the runtime.

The runtime is also shared by all applications that use this runtime.

The steam flatpak can’t install udev rules. It works if you install a packacke such as steam-devices on your host system. See https://github.com/flathub/com.valvesoftware.Steam/wiki#my-controller-isnt-being-detected

Time to switch to BSD

I’d just like to interject for a moment. What you’re refering to as GNU Hurd, is in fact, GNU-Linux, or as I’ve recently taken to calling it, GNU minus Linux.

What should be shown if there is currently no playback?

No. I only set up /etc/fstab and /etc/ssh/sshd_config once and they will never change.

That’s why you put your config files in a git repository

The documentation says:

Waydroid uses Linux namespaces (user, pid, uts, net, mount, ipc) to run a full Android system in a container and provide Android applications on any GNU/Linux-based platform.

To my understanding this isn’t even emulation but regular container technology.

Will have to switch back to X.Org until this is fixed by the Wayland/XWayland developers

This isn’t the responsibility of “wayland developers”. The developers of an application need to adapt to the new API.

fedora (Sped Up)

Looks like someone discovered dnf5

Paper doesn’t fry my eyeballs.

Wayland monolith

There seems to be misunderstanding about what Wayland is.

Wayland is set of protocols. They are implemented by wayland servers (compositors) and wayland clients (applications) themselves. There is no single “wayland binary” like in the X11 days. Servers or clients may choose to implement or not implement a specific protocol.