I think it would be very interesting to convert e.g. a regular Fedora installation into a (so-called “immutable”) Fedora Silverblue installation or vice-versa.

As others mentioned, running a minecraft server by itself is pretty easy. If you want additional features like a Web UI, multiple servers at the same time etc. you might take a look at Crafty Controller.

As someone who develops an distributes a small application exclusively on Flathub, I prefer that everyone uses the exact same package on every system. That way I know that if something doesn’t work, the issue should be easy to reproduce.

Recently, there was a situation where a user indicated in the comments of a release announcement that a newly introduced feature “doesn’t work”. It turned out that they installed a third-party package from the AUR (that wasn’t updated yet) without knowing that this isn’t the official and up to date version.

But it comes at the cost of obscurity, Codeberg is a big player but any instance you find is isolated, and any devs you entice to help you need to register additional accounts personal to that instance.

It should be noted that Forgejo is working on implementing federation using ForgeFed, which is based on ActivityPub.

This, but Forgejo instead of Gitea.

Fuck X.com, all my homies use wayland.social

https://github.com/andyholmes/valent/

This is more of a general suggestion: if you use Regular Expression, use https://regex101.com/. It provides syntax highlighting, explains the syntax and allows you to test your regexes.

Additionally, I think that sd is way more intuitive than sed.

There is not much of a difference

It’s the other way around. 0.1 kWh means 0.1 kW times 1 h. So if your device draws 0.1 kW (100 W) of power for an hour, it consumes 0.1 kWh of energy. If your device factory draws 360 000 W for a second, it consumes the same amount of 0.1 kWh of energy.

I’m likely to rebuild the backend in Go

Why bother with another language? Rust offers multiple great backend options. Using the same language for both ends might allow reusing some parts.

I’ll look into it if I find the time.

It uses the browser preference for light/dark theme by default

This doesn’t work for me. It seems like you are using leptos_use::use_preferred_dark with server-side rendering which unfortunately uses the experimental Sec-CH-Prefers-Color-Scheme header which isn’t supported by all browsers, e.g. Firefox.

In my opinion, it is way better to implement theme switching on the client side. The prefers-color-scheme media query is better supported across browsers and allows reacting to a change of the user’s system preferences.

This project sounds like a great idea!

Dark mode, so that you can write articles from the beach or from your basement

It would be great if it respected my browser’s prefers-color-scheme setting.

The Flatpak is official.

But gnome apps don’t do that on XFCE. simple-scan and zenity as an example.

The latest version of both simple-scan and zenity do support custom accent colors. AFAICT, XFCE doesn’t support the XDG accent color setting.

Please don’t implement libadwaita, guys.

This is just extremely misleading. Libadwaita uses the system accent color by default which makes it even easier respect the users preference when developing a GTK application.

# apt apt install
E: Invalid operation apt

To get a TLS certificate from Let’s Encrypt, they need to verify that you are in control of your domain. For regular domains, this can be done via HTTP, for wildcard certificates they require you to create a DNS record with a special token to verify ownership of the domain.

This means that in order to automatically obtain a TLS certificate, caddy needs to interact with the API of your domain registrar to set up this record. Since there are many different providers, this isn’t built into caddy itself and you require a version that includes the corresponding caddy-dns module. Caddy modules need to compiled into the binary, so it’s not always trivial to set up (in my case I have a systemd timer that rebuilds a local container image whenever a new version of the docker.io/caddy:builder image is available).

Caddy automatically sets up certificates for you. Since I don’t want my subdomain to appear in certificate transparency logs, I use a wildcard certificate which requires using a plugin for my DNS provider.

A reverse proxy, in my case Caddy.