Linux

Since I switched to GNOME and Wayland on my desktop I have been missing XScreenSaver. JWZ is rightly not planning to add support for this unless there are some significant changes in GNOME. I felt left out whenever I saw a new version with new hacks being released. Recently I stumbled over retrosaver by c-premus. It is basically a workaround to run the hacks on GNOME Wayland. It doesn’t lock the screen and leaves that to GNOME, so it isn’t really a replacement for XScreenSaver. At home, this is probably good enough. ...

As part of moving my services to EU-based infrastructure, I’ve been migrating away from GitHub to Codeberg, a non-profit code hosting platform based in Germany. One of the things I needed was a CI pipeline to build a container image and push it to the Codeberg container registry for my wildfires project (which also posts to @catfires@rls.social). It took a few tries to get right, so here’s what works for me. ...

Like a lot of Europeans, I realise that the US isn't a reliable partner anymore. I am just talking about myself here, and not my employer, or my family. I do use a lot of services that are based in the US, and some I will probably not migrate in the near future. But when I receive a bill, it is a good moment to consider if it is a candidate for migration. ...

For my new job, I (annoyingly) have to use a silly MacBook. For everything else, I have a nice, beautiful desktop running Fedora. I looked into KVMs to share my monitor and keyboard between the two computers, but couldn’t really find something reasonably priced and functional. Synergy/Barrier/InputLeap for keyboard sharing I have used Synergy before to share keyboard and mouse between Linux computers, and this was already a good step. There is a fork for Synergy on Linux called Barrier, which now has been forked again to InputLeap. Now the maintained version is Deskflow. It also allows copy & paste between systems. ...

It is fairly common that you might be contributing to multiple git repositories which make different git configuration necessary. Mine and probably the most common case is that I am using different contributor email addresses for my private and work git repositories. You might also want to have separate global git ignores or other options that differ in multiple repositories. The way I do it is having one ~/.gitconfig which looks like this: ...