On a work computer I'm currently using WSL quite often and thus wanted to see if there is a pbcopy/pbpaste equivalent.
Turns out WSL integrates with the X11 and Wayland clipboard APIs, thus we can simply install wl-clipboard.

With this in place, running wl-paste inside WSL dumps the content of the Windows clipboard.
And echo "foobar" | wl-copy puts "foobar" into the Windows clipboard.

Entdecke das Web – pause.gigold

Ein Button, der dich per Zufall zu unterhaltsamen aber oftmals nicht nützlichen Webseiten bringt – einfach nur, um Zeit zu verbummeln. Dafür wurde das Netz gemacht. Entdecken auf pause.gigold.de.

(via)

Debian 13 (Trixie) was released yesterday. 🎉

As I refer to the stable repositories in my sources list, the following error is now shown since their release information changed:

# apt-get update
Hit:1 https://security.debian.org/debian-security bookworm-security InRelease
Hit:2 https://download.docker.com/linux/debian bookworm InRelease
Get:3 http://mirror.iway.ch/debian stable InRelease [138 kB]
Get:4 http://mirror.iway.ch/debian stable-updates InRelease [47.1 kB]
Hit:5 https://deb.goaccess.io bookworm InRelease
Reading package lists... Done
N: Repository 'http://mirror.iway.ch/debian stable InRelease' changed its 'Version' value from '12.11' to '13.0'
E: Repository 'http://mirror.iway.ch/debian stable InRelease' changed its 'Codename' value from 'bookworm' to 'trixie'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
N: Repository 'http://mirror.iway.ch/debian stable-updates InRelease' changed its 'Version' value from '12-updates' to '13-updates'
E: Repository 'http://mirror.iway.ch/debian stable-updates InRelease' changed its 'Codename' value from 'bookworm-updates' to 'trixie-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

To fix this message (and enable upgrading to the new release!), I use the following command:

# apt-get --allow-releaseinfo-change update
...
N: Repository 'http://mirror.iway.ch/debian stable InRelease' changed its 'Version' value from '12.11' to '13.0'
N: Repository 'http://mirror.iway.ch/debian stable InRelease' changed its 'Codename' value from 'bookworm' to 'trixie'
N: Repository 'http://mirror.iway.ch/debian stable-updates InRelease' changed its 'Version' value from '12-updates' to '13-updates'
N: Repository 'http://mirror.iway.ch/debian stable-updates InRelease' changed its 'Codename' value from 'bookworm-updates' to 'trixie-updates'

Afterwards I run the usual apt-get dist-upgrade to upgrade the system to the new Debian version.

[Keep] a very tight leash on this new over-eager junior intern savant with encyclopedic knowledge of software, but who also bullshits you all the time, has an over-abundance of courage and shows little to no taste for good code. And emphasis on being slow, defensive, careful, paranoid, and on always taking the inline learning opportunity, not delegating.

— Andrej Karpathy, twitter

(via)

Joel Dare explains Why I’m Writing Pure HTML & CSS in 2025.

Pure HTML is evergreen

HTML was invented by Tim Berners-Lee in 1991 as he worked on the World Wide Web at CERN. Some of the earliest examples of web pages are contained in the documentation on the WWW project.

These pages still render in modern web browsers.

(via)

I revoked a signing subkey of my GPG key.
The expiry date of this subkey will no longer be updated (as the key is revoked).
But I plan to keep the revoked subkey itself in my public key (so people can still associate old signatures with me).

The pgp-expiry-monitor would now alert for all eternity on the expiry date once it passes.
To avoid this, I now added functionality to read the revocation status of a subkey and skip the expiry date check if it has been revoked.

You can install the newest version of pgp-expiry-monitor from GitHub:

go install github.com/x-way/pgp-expiry-monitor@latest

The Bash trick you need is:

trap 'echo "Exit status $? at line $LINENO from: $BASH_COMMAND"' ERR

(via)

In the tmux and gist and trying to make students happier article, Jan-Piet Mens explains how to take screenshots with tmux.

As I still haven't migrated from Screen to tmux, I was wondering if this is also possible in Screen.
And turns out that there is indeed a similar mechanism that can be used in Screen.

By using the hardcopy command, Screen can write the current scrollback buffer to a file.
This can also be done for a detached session:

screen -X hardcopy -h /tmp/myscreenshot.txt

It's also possible to specify an explicit session and pane to use:

screen -p 0 -S 12345.pts-0.rocky -X hardcopy -h /tmp/myscreenshot.txt

Turns out docker only restarts unhealthy containers when running in a Docker Swarm setup.

For other setups, the following crontab entry provides a quick and dirty alternative that checks for unhealthy containers and restarts them.

*/15 * * * * /usr/bin/docker ps -q -f health=unhealthy | /usr/bin/xargs --no-run-if-empty -L 1 /usr/bin/docker restart

By providing the --since parameter, we can list the past docker events:

docker events --since=60m

This can be further combined with --filter parameters to drill down to specific events of a specific container:

docker events --filter event=restart --since=24h --filter container=<containername>