setVeryLoud(true);

I’ve been looking at K3s deployed on FCOS, but I have no clue how I’m supposed to use Terraform to deploy FCOS.

My understanding is that FCOS is supposed to be ephemeral and re-deployed every so often, which would imply the use of a hypervisor like Proxmox on the host, but Proxmox does not play well with Terraform.

I also considered OpenStack, but it’s way over my head. I have a very simple single-node Kubernetes setup to deploy using GitOps, and nothing seems to fit the bill.

Because it’s an OSK, not a touch screen keyboard.

Hopefully someone spends some time developing a proper touch keyboard on GNOME.

It’s not a competition, and insulting developers who donate their time to open-source is counterproductive.

Use whatever you wish.

The piss stain colour palette confirms it.

Both, it’s a dual-purpose item!

In case of armed road rage, remember that your car is a weapon. It’s self-defense if a gun is drawn on you.

Ubuntu Core, based on Snaps, is very much not ready for prime time IMO. It’s kind of a mess outside of server use.

Look instead at Fedora Silverblue, Vanilla OS, and for the bleeding edge of immutable systems, GNOME OS.

KDE is about to launch their analogue to GNOME OS relatively shortly, named “Project Banana”. These two are not exactly distros as they do not distribute the kernel, they are simply platforms that layer a bunch of images together to create a stable, reproducible system. There’s also OpenSuSE Aeon, but I don’t like its style of immutability as it’s immutable by rootfs lock-out rather than immutable by image.

As for advice, learn how to use Distrobox / Toolbx containers. If you’re a developer, this is where you will be working.

Immutable Linux is still young, and a lot of software isn’t written with it in mind, so expect some growing pains.

I’m running an immutable distro at the moment (GNOME OS), and I felt no loss of performance due to Flatpaks. Snaps, on the other hand, do have a perceivably longer launch time.

Given that it’s an immutable distro, everything I need needs to be either a Flatpak, a Snap, an Appimage or an extracted tarball, otherwise it runs in a container. The advantage of this system is stability and making the host incorruptible, as well as the ability to very easily roll back updates or failed systemd-sysext layers.

Not everything can run in a Flatpak at the moment, but we’re hoping the evolution in Flatpak, XDG portals as well as encouraging developers to use the available XDG portals can make this a possibility someday. Namely, IDEs don’t run that well in a Flatpak, but GNOME Builder has proven that it’s 100% possible with the currently available XDG portals as well as connecting your IDE or editor to a container.

I’ve actually been discussing the idea of Flatpaks offering “terminal aliases”, similar to what Snaps do, with some people involved in Flatpak. It’s something that could happen in the future, but for now, you can totally create an alias to run a Flatpak from a single word, it’s just a PITA.

Flatpaks aim to be a middle ground between dependency hell and “let’s pull in the universe” bloat.

Applications packaged as Flatpaks can reference runtimes to share “bases” with other applications, and then provide their own libraries if they need anything bespoke on top of that.

Use user styles at your own risk.

I was using LibreChat for a while

Sunk cost fallacy

GDM won’t be able to launch X11 environments after GNOME 50 is my understanding.

I’m not talking about this website specifically, a lot of sites ask for way too much info.

I just click away when I see a login wall, regardless of requirements. If I really want to read it, I use 12ft.io or similar.

Edit: Here’s a wall-less link: https://archive.ph/mFHH8

I really don’t feel like setting up an alt email address just to read a single article.

Indeed it is, but I’m concerned about the above, and thus don’t create user accounts willy nilly.

I could use a fake name and fake email, but a lot of sites require that you validate your phone number too, and it’s starting to become a lot of commodifiable data points.

Try the Canadian French layout, it’s a much saner French layout IMO.

It focuses on communication, so I use it in combination with the US layout so I can type programming-related characters.

Trust me, I get the feeling.

I’m only arguing from a legal standpoint, where it’s more appropriate to have CC0.

CC0 = Everyone owns it, no one can claim rights to it

Copyleft = No one owns it, the code owns itself and claims rights to itself

Since everyone paid for it, everyone owns it.

If no one paid for it, or if a single owning entity is feeling benevolent, then copyleft is appropriate.

I assume it would be difficult to get the consent of every US taxpayer to license this as copyleft, I believe CC0 (or proprietary, unfortunately) is the rightful default when in this situation. It’s debatable whether any government code should be proprietary, save for deployment secrets.

It’s generally for user data collection / sale and adding you to their marketing list.