So, I’ve been told by @uxgch that my twtxt feed was a little bit broken in some clients: It needed “charset=utf-8” in the HTTP content type header. As a workaround, https://www.uninformativ.de/twtxt.txt.utf-8 now exists. Maybe I’ll set up a redirect … not sure yet.

I can finally control this special LED on my keyboard on Linux. And guess what: No hackery required, the manufacturer told me which USB packets to send! What a pleasant experience! 😎️ Blog post with details soon-ish.

enotty.dk slowly discontinuing all their feeds, even “we-are-twtxt”. :( Why, what’s going on?

I want a private sauna. While we’re at it, I want a Mökki in Finland. With high-speed internet. And no gnats. On Mars.

Hallo! Ich bin Experimentalinformatiker. Ich klopfe irgendwo auf Bits drauf und gucke, was passiert. Was anderes fällt mir im Zeitalter von hyperkomplexen Systemen oder am besten noch Cloud-Blackboxen nicht mehr ein. #thankgoditsfriday

Turns out, there’s another problem with using ancient browsers in 2020 (aside from the fact that they don’t support today’s SSL ciphers), that I completely forgot about: They don’t support HTTP/1.1. Only 1.0. Meaning, they can’t select a VHost. Meh.