@movq@www.uninformativ.de Yeah. The thunderstorm was supposed to hit us, sneak north and south around us, directly pay us a vistit again, miss us to the north, directly hit us, and now it’s back to a northern diversion. The thunder heavily roars in the distance at the moment. It’s down to just 10 liters. A mate just got a wet laundry, though, and had to mob up a – luckily – just tiny flood.

As I type, the first drops begin to fall.

@lyse@lyse.isobeef.org Ah, yes, you live in “the zone”: https://social.bund.de/@DeutscherWetterdienst/116839789079697685

@itsericwoodward@itsericwoodward.com … does your cat wear a bow tie?

@bender@twtxt.net There already is one haha 🤣 I already wrote ed and vi in Go 🤣

@prologic@twtxt.net gonix-vim, of course. 😅

@movq@www.uninformativ.de Oh dear! :-(

Now, it’s cooler outside than inside. Time to open the windows and start the wind machines.

@lyse@lyse.isobeef.org Don’t worry, my apartment is still at around 28-30 °C, too, and there’s the construction site outside which is noisy is fuck. Everything sucks at the moment. 🤣

@movq@www.uninformativ.de Lucky you! My damn work laptop heated up this room to 29°C. The hottest so far.

@movq@www.uninformativ.de LOL

@movq@www.uninformativ.de no AC—because it has never been needed—is terrible, fully agree. That takes it to another level! 🥵

@prologic@twtxt.net Depends on what you want, I guess.

Stability: vim-classic > vim > neovim

Features: neovim > vim > vim-classic

😅

@kiwu@twtxt.net Last time you asked we were all tired. Now we’re EXHAUSTED because it’s 40 °C around here. 🥵😂😭

@movq@www.uninformativ.de It was nice at around 5 o’clock on the balcony with just 22°C and the tiniest breeze. But I got eaten alive. Fucking mozzies.

@lyse@lyse.isobeef.org It was around 29 °C for a while inside and pretty nice on the balcony, but that’s over now. 🤣

@movq@www.uninformativ.de 26°C inside, 30°C outside right now.

@bender@twtxt.net I know heat (I’ve been to Southeast Asia, for example – or Florida 🤣), but you’re right, it does hit very differently when it’s at home. “At home” is usually the cool and relaxed place, but now it’s hell. And no AC anywhere in sight.

@thecanine@twtxt.net Oh, I’m absolutely bad with videogames. Never heard of that one.

@bender@twtxt.net Please, mate, keep the heat to yourself! I don’t wanna trade that. ;-)

@lyse@lyse.isobeef.org so pretty! Ah, the anticipation of an incoming heat wave! Now you guys have a small glimpse of what we live with here almost every single day. 😅

@lyse@lyse.isobeef.org Thanks! You had one of the strangest guesses so far, first one I had to look up. 😄 It is a reference to a (human) cop/detective, from a 2019 videogame. Since there’s no spoilers tag on Twtxt, the name of the file on my site, includes the correct answer.

@movq@www.uninformativ.de Oh my! :-O We reached 38°C. It’s now down one degree.

I just got up from my two, three hours siesta. And I tell you, that was bloody amazing. Layed in bed in undies, no blanket, just some power metal in my headphones and I was sleeping like a baby. Normally, I NEED a blanket, no matter what. But this summer, it’s already the second time that I actually manage to drop off without one.

@prologic@twtxt.net (I haven’t checked out CEF recently. Back then (over 10 years ago), just using a GTK widget was certainly much easier than CEF. 😅)

@movq@www.uninformativ.de CEF turns out to be pretty easy. I had to write a bit of C and Go to bridge, but once that got going I was able to write it into my pure Go go-wayland wlui library for final rendering. The delegating the entire CEF part was a good idea though because it keeps all the complexity in a container Image, leaving me with just the Go + C stubs/interface and SHM/IPC parts.

@prologic@twtxt.net Ah, the joy of making your own browser – welcome to the club. 😃 (I chose WebKitGTK back then and that was not super compatible with websites … CEF would have been better, but also harder to use.)

@movq@www.uninformativ.de Oooph! Web development is tidious.

I also include width and height from now on in my galleries.

@movq@www.uninformativ.de I second that!

@lyse@lyse.isobeef.org I noticed that loading="lazy" might not be so great after all.

This is without lazy loading:

The total page load time is around 400-500 ms. Okay.

Now this is with lazy loading:

It finished much quicker, after about 250 ms. Sounds good.

But notice this gap right here?

This wasn’t there before. With lazy loading, it now takes something like 80-100 ms until the browser even starts loading images. This is Chromium, but Firefox shows a similar gap.

The net result is that there is a very noticeable delay/flicker when you open a page, because it takes so long until the images have loaded. Yes, the layout doesn’t shift around, but that has nothing to do with lazy loading.

How odd. 🤔

@movq@www.uninformativ.de I see. I just use CDATA (and still have the XHTML trailing slash for <img … />). But of course, it also has its drawbacks: https://waspdev.com/articles/2026-05-11/avoid-using-cdata-in-rss I might just move away from it.

Everything is a web service these days. :-/

@lyse@lyse.isobeef.org Oh my god, there’s nothing that CSS can’t do, eh? 😳 Crazy stuff.

@lyse@lyse.isobeef.org Putting HTML into the feed. It should be XHTML. 🤪 (I used <img ...> instead of <img .../>.)

@lyse@lyse.isobeef.org Nice! (But if you ask me, a day without sun would a welcome change. 🤣)

@movq@www.uninformativ.de Congrats, how did you break it? :-)

@movq@www.uninformativ.de Good idea, I should probably do the same for my photo galleries.

@movq@www.uninformativ.de Yes, that’s what I was thinking, too. For a moment, I wanted to suggest to use <ol> instead of <ul> to fix that. However, that’s only gonna work for the first level, but subsections then miss their parent level.

And it turns out that I was wrong. At least sort of. There are some CSS tricks to fix it: https://stackoverflow.com/a/26243681 Of course, with text or retro browsers, this is not gonna fly.

I also came across this interesting article. I just skimmed it and it’s about real tables of contents with page numbers, so not what you have in mind, but cool nevertheless: https://css-tricks.com/a-perfect-table-of-contents-with-html-css/

@lyse@lyse.isobeef.org It was a wild ride for sure. 😂

@lyse@lyse.isobeef.org Besides, have a look at again: When it goes from item 9 to item 10, the indentation of the text (after the number) changes. Pretty ugly. In other words, a table of contents should be a table, not a list like it is at the moment. And that would require me to write my own extension for python-markdown … Probably not worth it.

@lyse@lyse.isobeef.org Mhm, yeah … I’ll probably not do it. Just keeping the numbers out of the anchors would be pretty hacky, I guess.

@movq@www.uninformativ.de Oh my goodness, what an adventure, hahaha! :-) https://movq.de/blog/postings/2026-06-25/0/POSTING-en.html

@movq@www.uninformativ.de I reckon section numbers are not really needed for articles. But if you number them, the anchors should probably not contain the section number, just the title. Especially for articles that may receive updates.

It’s probably another story for specifications. They’re kinda fixed and thus I found it useful in the past to include the section numbers in the anchors, so they show up in URLs when linking to specific sections. W3C RFCs only include the numbering in the anchors. This makes URLs fairly short, but it would be also nice to directly see what kind of section that URL actually links to.

@thecanine@twtxt.net I don’t know if the Dinosaurs TV series is a meme, but this cute thing surely reminds me of that.

@movq@www.uninformativ.de Right. A Go programmer eventually knows that its nanoseconds precision. Keyword arguments like in Python are just sooo superior to unnamed positional arguments. I wish that Go had them, too.

@movq@www.uninformativ.de It’s working fine. I can still read your messages. :-)

@itsericwoodward@itsericwoodward.com This will never end. Chat control in the EU is back as well, it seems. 🙄

@bender@twtxt.net Yeah, that would be good, it only supports gzip, though. 🥴

Finally finished another meme one, I always wanted. It took forever, to get it right, so I really hope people get the reference.

@movq@www.uninformativ.de using zstd first, and gzip after for everything is kind of standard these days, isn’t it? I use Caddy, and have encode zstd gzip on all sites.

Using gzip compression for the twtxt files now. I don’t expect any issues but let me know if something breaks. 🥁

(This feature is implemented in a pretty minimalistic way in OpenBSD’s httpd …)

@lyse@lyse.isobeef.org Mhm, yeah, I also think I like date := time.Date(2026, time.June, 19, /**/ 17, 0, 0, 0, time.UTC) the most. 🤔 (My only gripe with this is that it isn’t obvious whether the third 0 is milli-, micro- or nanoseconds. These days it’s probably nanoseconds, but you never know.)

@movq@www.uninformativ.de I admit, it’s something different in the pitch dark. Noises are a hell lot more eery. I do wince every now and then, too. :-)

But I’m very glad that I only have to really worry about ticks and boars in our forests. They’re petting zoos compared to everywhere else. Let’s see when the bears and wolves return. It’ll be another story then.

@lyse@lyse.isobeef.org Huh. Yeah. Indeed. 😃