@bender@twtxt.net Yes! You guys have this thing called a “5th wheeler” 🤣 We (Aussies) just don’t normally have big enough trucks to drag those “House on wheels” though 😅

I think I understand now. Americans do not go camping, we do recreational activities. I don’t think campers are a thing here, but RVs (Recreational Vehicles) are. That’s why it would never cross my mind to get anything with fabric, that folds. No mate, we get a house on wheels, with a million miles engine. 🤣

Other than that, it looks nice!

@doesnm@doesnm.p.psf.lt Haha, nice! :-D I haven’t come across this one before.

Discover the OPUS OP4 TLX: The Perfect off-road Camper for Families Kind of thinking about this now hmmm 🤔

Nuke it from orbit: https://www.aaron.ai/

Nooooooooooooooooooooooooooooooooooooooooooooooooooooooo, the doctors have started using AI voice agents and they understand jack shit. 😭😭😭

@lyse@lyse.isobeef.org I know web server which reject request with Referrer header

@movq@www.uninformativ.de That’s an interesting idea. For privacy, I’d just omit the Referer altogether. But maybe this helps talking to misconfigured HTTP servers that reject requests without such a header. No clue.

@lyse@lyse.isobeef.org Hm, I don’t think so, the requested page was a Linux-specific post. 🤔 I sometimes wonder if privacy-oriented browsers might do this on purpose, to create garbage data? 🤔 No idea.

@lyse@lyse.isobeef.org I honestly wish I could do more than just sit here and wait. It’s just a matter of time until they remove X.Org from the repos. 🫤 But I really can’t dedicate so much time to this …

@movq@www.uninformativ.de I only know three letters: S (…), O (—) and E (.). ;-)

@arne@uplegger.eu Das ist wie mit Kulis. Die verschwinden auch urplötzlich auf völlig unerklärliche Weise.

@movq@www.uninformativ.de Yeah, you can’t rely on them. Anybody could just transmit whatever they wanted. Bots and spammers abuse them all the time. But maybe some older version of that page actually referenced your site. :-?

@movq@www.uninformativ.de X.org forever!

I give up.

Let’s try again next year. I don’t have the stamina. Death by a thousand paper cuts.

Can’t set up a meaningful taskbar: https://github.com/labwc/labwc/discussions/2924 (This is not a labwc issue, it’s a generic issue in the broader Wayland ecosystem.)

HTTP referrers are quite broken, aren’t they?

Because of that recent storm on my blog, I had a peek at them. There’s a lot of garbage in there. For example, https://docs.freebsd.org/en/books/handbook/disks-virtual.html is supposed to refer to one of my blog posts …

What’s going on here?

@bender@twtxt.net Even I don’t believe in that anymore. :‘(

@lyse@lyse.isobeef.org Don’t remind me about Morse. I really wanted to learn that and tried so for quite a while, but no success. 😢

@lyse@lyse.isobeef.org Ja, eine kleine Inventur vorab kann auch nicht schaden. Der Bestand an Erdankern, Heringen und Gaskartuschen ist durch mich die Tage schon wieder aufgestockt worden.
Wo das Gas bleibt weiß ich. Warum die Befestigungen immer weniger werden, obwohl wir durchzählen (!), ist mir unbekannt. Vielleicht sind wir im Zahlenraum von 1 bis 20 einfach nur noch sehr unsicher. 🤓

@bender@twtxt.net Finally! Let’s wait and see how it turns out. :-D

@arne@uplegger.eu Au, Zelturlaub klingt klasse! Bei mir ist es auch bald so weit, freu mich schon. Dank der Ausrüstungsüberprüfung im Materiallager haben wir demletzt festgestellt, dass gleich zwei Spinnen (so Metallketten, an denen die Jurtendächer hochgezogen werden) fehlen. Ein Probeaufbau – und sei es nur unter Laborbedingungen – lohnt sich in jedem Fall. Improvisieren zu können ist zwar von Vorteil, aber wenn es sich vermeiden lässt, fängt der Urlaub gleich ein wenig entspannter an. :-)

This is it, boys and girls! The year of the Linux Desktop is this! I can smell it! :-D

For the first time, Linux has officially broken the 5% desktop market share barrier in the United States of America! It’s a huge milestone for open-source and our fantastic Linux community.

Bald geht’s in den Urlaub. Nach Dänemark und auf die Insel Fehmarn. Alles mit dem neuen Zelt, welches wir dringen mal zum Probieren aufbauen sollten. 🤔

@movq@www.uninformativ.de Oh wait, I should post a picture of my old Walkman and a couple of cassette tapes to verify 😆

@movq@www.uninformativ.de I also had to laugh when I saw that. :-)

@movq@www.uninformativ.de Don’t forget about Morse Key Monday and Teletypewriter Tuesday.

@aelaraji@aelaraji.com And I read the following funny response to that:

Bluesky: Users verify their age by adding a payment method or uploading a photo ID.

Mastodon: Users verify their age by posting pictures of the vintage computer equipment in their homes.

https://beige.party/@maxleibman/114848276288629121

😏

@movq@www.uninformativ.de Permaculture should do the trick 😉

ROFL 🤣 I’ve just read from someone on the Fedi, that Bluesky has started asking people for ID

AI this, AI that.

Tech is no longer interesting. I need to find a new field.

(… maybe followed by “tmux Thursday” to cool down …)

Thinking about doing “Wayland Wednesday”. Only use Wayland every Wednesday. Collect bugs, report bugs, fix bugs.

@lyse@lyse.isobeef.org 06.jpg is quite funny. Block the road for 30 minutes! %)

@bender@twtxt.net Hm, it is now. 🤔 I should have made a screenshot when I first saw it.

What a banger! I just came across the band Year Of The Goat: https://www.youtube.com/watch?v=H3FoOGp0jmc

I meant, the first line is the only one on the blockquote.

@movq@www.uninformativ.de it is.

@movq@www.uninformativ.de That’s really cool! I wanted to experiment with Landlock in tt as well. But other than just thinking about it, nothing really happened.

Depending on the available Landlock ABI version your kernel supports, you might even restrict connect(…) calls to ports 80, 443 and maybe whatever else has been configured in the subscription list.

A mate visted me and we went on a few hours long hike. We came across a mythical creature in its natural habitat:

https://lyse.isobeef.org/waldspaziergang-2025-07-12/

@prologic@twtxt.net Yeah, it’s not a strong sandbox in jenny’s case, it could still read my SSH private key (in case of an exploit of some sort). But I still like it.

I think my main takeaway is this: Knowing that technologies like Landlock/pledge/unveil exist and knowing that they are very easy to use, will probably nudge me into writing software differently in the future.

jenny was never meant to be sandboxed, so it can’t make great use of it. Future software might be different.

(And this is finally a strong argument for static linking.)

Looks like here’s something wrong with Markdown parsing. 🤔 The original twt looks like this:

>This extension was turned off because it is no longer supported

Thanks Google.
This browser was uninstalled because it absolutely sucks!

So only the first line should be a quote.

This extension was turned off because it is no longer supported

Thanks Google.
This browser was uninstalled because it absolutely sucks!

@movq@www.uninformativ.de Nice! 👍

Landlock is still young and a bit unpolished, but it’s slowly getting more popular. 🥳

Another example:

$ setpriv \
    --landlock-access fs \
    --landlock-rule path-beneath:execute,read-file:/bin/ls-static \
    --landlock-rule path-beneath:read-dir:/tmp \
    /bin/ls-static /tmp/tmp/xorg.atom

The first argument --landlock-access fs says that nothing is allowed.

--landlock-rule path-beneath:execute,read-file:/bin/ls-static says that reading and executing that file is allowed. It’s a statically linked ls program (not GNU ls).

--landlock-rule path-beneath:read-dir:/tmp says that reading the /tmp directory and everything below it is allowed.

The output of the ls-static program is this line:

─rw─r──r────x 3000 200 07-12 09:19 22'491 │ /tmp/tmp/xorg.atom

It was able to read the directory, see the file, do stat() on it and everything, the little x indicates that getting xattrs also worked.

3000 and 200 are user name and group name – they are shown as numeric, because the program does not have access to /etc/passwd and /etc/group.

Adding --landlock-rule path-beneath:read-file:/etc/passwd, for example, allows resolving users and yields this:

─rw─r──r────x cathy 200 07-12 09:19 22'491 │ /tmp/tmp/xorg.atom

PSA: setpriv on Linux supports Landlock.

If this twt goes through, then restricting the filesystem so that jenny can only write to ~/Mail/twt, ~/www/twtxt.txt, ~/.jenny-cache, and /tmp works.

st tries not to redraw immediately after new data arrives:

https://git.suckless.org/st/file/x.c.html#l1984

The exact timings are configurable.

This is the PR that changed the timing in VTE recently (2023):

https://gitlab.gnome.org/GNOME/vte/-/issues/2678

There is a long discussion. It’s not a trivial problem, especially not in the context of GTK and multiple competing terminal widgets. st dodges all these issues (for various reasons).

Something happened with the frame rate of terminal emulators lately. It looks like there’s a trend to run at a high framerate now? I’m not sure exactly. This can be seen in VTE-based terminals like my xiate or XTerm on Wayland. foot and st, on the other hand, are fine.

My shell prompt and cursor look like this:

$ █

When I keep Enter pressed, I expect to see several lines like so:

$
$
$
$
$
$
$ █

With the affected terminal emulators, the lines actually show up in the following sequence. First, we have the original line:

$ █

Pressing Enter yields this as the next frame:

$
█

And then eventually this:

$
$ █

In other words, you can see the cursor jumping around very quickly, all the time.

Another example: Vim actually shows which key you just pressed in the bottom right corner. Keeping j pressed to scroll through a file means I get to see a j flashing rapidly now.

(I have no idea yet, why exactly XTerm in X11 is fine but flickering in Wayland.)

The WM_CLASS Property is used on X11 to assign rules to certain windows, e.g. “this is a GIMP window, it should appear on workspace number 16.” It consists of two fields, name and class.

Wayland (or rather, the XDG shell protocol – core Wayland knows nothing about this) only has a single field called app_id.

When you run X11 programs under Wayland, you use XWayland, which is baked into most compositors. Then you have to deal with all three fields.

Some compositors map name to app_id, others map class to app_id, and even others directly expose the original name and class.

Apparently, there is no consensus.

@iolfree@tilde.club Oh dear! All the best to this feller. I wouldn’t want to trade places with him.