Other than the few Unicode issues I mentioned recently, vim-classic works just fine. I completely forgot that I switched to it.

Starting the day with 32 °C inside and absolutely no cooling from the outside.

@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.

We’re at 39.5 °C now. Are we going to hit 40?

@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. 😅)

@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.)

Compromise: Don’t lazy-load the first ~7 images or so, i.e. the ones that are immediately in view.

tl;dr: Lazy loading is much better on slow internet lines but shittier on fast ones. 🫠

Ah, with lazy loading, browsers only start loading images when the load event occurs. And that takes time. Hm. Not a fan, I might revert this. 🤔

@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. 🤔

Interesting, HTTPS is almost twice as slow as plain HTTP on my server (~72 ms vs. ~135 ms):

$ hyperfine -r 50 "curl -so /dev/null 'http://movq.de/blog/postings/2024-05-23/0/t/word11a.jpg.jpg'"
Benchmark 1: curl -so /dev/null 'http://movq.de/blog/postings/2024-05-23/0/t/word11a.jpg.jpg'
  Time (mean ± σ):      72.7 ms ±  17.2 ms    [User: 6.2 ms, System: 4.8 ms]
  Range (min … max):    49.5 ms …  99.7 ms    50 runs

$ hyperfine -r 50 "curl -so /dev/null 'https://movq.de/blog/postings/2024-05-23/0/t/word11a.jpg.jpg'"
Benchmark 1: curl -so /dev/null 'https://movq.de/blog/postings/2024-05-23/0/t/word11a.jpg.jpg'
  Time (mean ± σ):     135.5 ms ±  28.9 ms    [User: 17.8 ms, System: 5.6 ms]
  Range (min … max):    93.2 ms … 198.5 ms    50 runs

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

Okay, I’m using the “official” validator now:

https://github.com/w3c/feedvalidator

That repo is supposed to be a website/webservice, though. The feedvalidator directory contains the actual validator. I’m using this wrapper on top: https://movq.de/v/94b5b8978c/

@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. 🤣)

Damn, I broke my Atom feed (and a reader let me know, that’s cool!).

I run vnu on all HTML and CSS files after each build of the website, but I don’t run a feed validator. 😬 Time to change that.

I complain about this a lot:

https://movq.de/v/e7cb49eefb/hiccupfx

But to be honest, my blog did the same thing – to some degree.

This is fixed now. The trick is to add width and height to all <img> tags. That way, modern browsers know how much space to reserve for the image. Without this, they just reserve zero space, so when the image finally loads, you get jumpy layout.

This effect is even worse when you use <img loading="lazy"> – which I can finally use, now that the jumpy layout has been fixed. 🥳

@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.

Numbered headings in blog posts, yay or nay?

Biggest problem of having them: Links to section anchors (like bla.html#my-first-section) will break if I add a section later on. 🤔

https://movq.de/v/cf0903ebc3/

@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. 🥴

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.)

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

@lyse@lyse.isobeef.org You think I thought about it on that level? 😅 I just heard that weird animal noise in the dark and I was the one who was running. 😂

This is a test.

@lyse@lyse.isobeef.org Omfg, that’s a big “no” from me. 😃 Nononononono. 😃 I had such an encounter with a fox once deep at night and that was scary enough. 🤣

Easy way to do digital detox: Use a Mastodon instance that someone else maintains. And when it’s down, there’s nothing you can do but wait. 😅

@prologic@twtxt.net Yeah, Rust is quite popular in the Wayland scene, it seems.

In image viewer in 170 lines? Show me. 😅

@prologic@twtxt.net The only image viewer I like in general is this one:

https://codeberg.org/nsxiv/nsxiv

It’s for X11, though.

Allegedly, this Wayland image viewer is somewhat similar to nsxiv, maybe you’ll like that? 🤔

https://github.com/artemsen/swayimg

@bender@twtxt.net Someome else’s BDay. I’ll convey the wishes. 😅

It’s ten thousand million degree celsius outside and I have to go to a birthday party today because wElL iTs My BiRtHdAy ToDaY, I think I’m going to die, send help.

@lyse@lyse.isobeef.org Ich zitiere von woanders und bin zu faul zum Übersetzen:

Ich gucke schon den ganzen Tag dem Storm Tracking zu und alle Gewitter in der Nähe haben sich kurz vor meinem Standort ausgeregnet oder sind abgedreht. 😭🥵

Bloody heat, omfg

@iolfree@tilde.club 😨😨😨

@prologic@twtxt.net Awwwww. 💚

Am I glad that I host nothing but static HTML.

Bracing myself for the next round …

@lyse@lyse.isobeef.org Hmmmmmm. Can you at least see those? ’ „ “ ”

@lyse@lyse.isobeef.org My thermometer claims 27 °C now but I don’t trust it. It’s hot, it’s humid, it’s horrible.

@lyse@lyse.isobeef.org Sounds lovely! (I think. Not sure about spider webs and such. 😅)

I woke up to 26°C this morning. 🥵

@itsericwoodward@itsericwoodward.com (I still hate that these photos look so good, despite being made with a telephone. 😝 I mean, the (probably built-in) filters are easy to spot, but it looks super convincing when you don’t pay attention.)

@lyse@lyse.isobeef.org Oh wow, we’re talking about such a detailed level. 🤔

I agree with most of what you said.

I probably would have written it like this:

// Arbitrary reference date.
//                   Y  m   d   H  M  S  nano
date := time.Date(2026, 6, 19, 17, 0, 0, 0, time.UTC)

Would this be better or worse? 😅

@lyse@lyse.isobeef.org Apparently some new ones, yeah, like these: 🫠🫩

@itsericwoodward@itsericwoodward.com

But it also wouldn’t surprise me to find out that people like Bezzos, Musk, and Zuckerberg are actually ghoulish aliens

Yeah, that’s easier to accept, isn’t? “Phew, they’re not human after all. They’re not absolute psychopaths with zero empathy – they’re just aliens. Humans are good!” 😅

@lyse@lyse.isobeef.org … I also meant to comment on the very neat and stylish Play Button, but forgot to do so. 😅😅😅

@itsericwoodward@itsericwoodward.com When I first watched that movie (decades after it was released, probably like 10 years ago), I didn’t expect that. 😅 Feels super silly today, and all the fighting and the “look at me, I’m a strong man” stuff. 😂

@lyse@lyse.isobeef.org Oh wow, nice. 😲 Never seen those in the wild myself.