🕑 Hi, the current time is about eight o’ clock in the morning 🌄.

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 Yeah, you gotta love when a “totally real decentralized protocol” does that. How are they doing this and still pretending to be one, is beyond me.

Gente amiga, que provider europeu recomendam para registo de domínios?

O Gandi subiu imenso os preços, e estou a olhar para o OVH, mas antes de mergulhar queria saber o que se usa por aí

@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! %)

@movq@www.uninformativ.de @lyse@lyse.isobeef.org i like this emoji too (it’s rhombus with question on my side)

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

“Brett Cannon on #Python humans… and packaging”

https://www.bitecode.dev/p/brett-cannon-on-python-humans-and

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:

Image

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.

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

Um exemplo mínimo de como usar #Python para ler dados de uma planilha #Excel com a biblioteca #openpyxl e como modificar um arquivo #Word com a biblioteca #docx

https://gist.github.com/villares/560e231da78cd1b8f5701c5a6897348f

Image

Another hacky #Python script using the #HackMD API… this one is to change the write permissions… you might want to adapt it or check out the other API helper methods:

https://gist.github.com/villares/177c2323d424d5b2b0de49570fb4e2fd?permalink_comment_id=5673097#gistcomment-5673097

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.

@lyse@lyse.isobeef.org Haha 🤣

We covered quite some ground in the two and a half hours today. The weather was nice, mostly cloudy and just 23°C. That’s also why we decided to take a longer tour. We saw four deer in the wild, three of which I managed to just ban on film, quality could be better, though. My camera produced a hell lot of defocused photos this time. Not sure what’s going on with the autofocus. https://lyse.isobeef.org/waldspaziergang-2025-07-10/

When the sun came out, colors were just beautiful:

Image

@prologic@twtxt.net @bender@twtxt.net That’s what I thought as well, sounds way too expensive to me. But I have no idea what the prices are over here. Probably also astronomical. Campers sit around most of the time, one really would need to use them a lot to justify spending so much money on them.

But yeah, each to their own (expensive) hobbies. :-) I, for example, burn my money on tools that I don’t really™ need. :-P

@bender@twtxt.net An older Firefox on Debian.

@prologic@twtxt.net well, the ones down there (on your list) are pretty minimal, basic even. Yet, their pricing is super high (number wise, haven’t checked the equivalent from AUD to USD).

@bender@twtxt.net are they really though when you factor in the weaker AUD? 🧐

Those campers are so expensive! For comparison: https://www.rvtrader.com/Orlando/rvs-for-sale?city=orlando&state=Florida%7CFL

Been spending a lot of time researching campers as I want to / plan to upgrade our current Camper Trailoer (forward fold) Stoney Creek XL-FF6 to a slightly larger Hybrid Camper/Caravan with ensuite, internal kitchenette, external full hitchen, pop-top roof and twin bunks.

This is the summary and whittling down of my research so far: https://wiki.mills.io/s/1103bc9c-dd75-4a98-b64b-8dadc5b0e51f/doc/comparision-Ln03Moiibq

Impossible Linux things in my to-do list:

• Fix erratically jumping mouse wheel scrolling on a Dell
  
• Make a “SysRq key” work so I can do “REISUB” or something, when my computer freezes
  

I must have spent days (multiples of 24 hours) trying to solve these things and maybe I should just give up.

I suppose that if I had a “Linux experienced” friend by my side these could be solved in minutes, maybe?

#OldManScreamsAtLinux

@lyse@lyse.isobeef.org which browser do you use? Chrome, Edge, and Firefox, under Ubuntu, all show it fine.

@movq@www.uninformativ.de This one is too bleeding edge for me, not even my browser can render it.

@anacat@anacat ei, chegaste a arranjar o flipper zero? Rende?

Yeah, little fellow. I also just want to walk away. https://movq.de/v/bef8c35f01/ach.mp4

“🫩” is my new favorite emoji.

Pessoas da comunidade brasileira de #ProgramaçãoCriativa por muitos anos fizeram encontros sob o nome promovido pela Fundação Processing, os chamados #ProcessingCommunityDay, fizemos encontros em várias cidades e então depois de 2020, com a pandemia do COVID-19, fizemos três eventos nacionais muito inspiradores em 2021, 2022 e 2023 (vide https://compoetica.github.io/links/)

Ano passado não conseguimos fazer e este ano pretendemos retomar, só que usando outro nome: #Compoética. Vamos aos poucos divulgar mais sobre o encontro brasileiro de programação criativa em https://compoetica.github.io/CP2025/

Meus agradecimentos profundos ao @guilhermesv@guilhermesv que dedica generosamente um enorme esforço para organizar esses eventos da comunidade e cria o design e peças de comunicação sempre emocionantes de lindos.

Video

Lazy-fedi-question… I have a “working”(?) code example of TF-IDF #tfidf using #scikitlearn and I know the main concepts, but all the tutorials I find are a bit — I don’t want to be harsh but —crappy… Can someone point me to some nice open resource on it?

@kat@yarn.girlonthemoon.xyz I dislike him big time. It was a sad day when Tumblr felt on his hands.

@lyse@lyse.isobeef.org Yeah, if there’s no stable API, then it’s not a lot of fun … Bah. :|

@kat@yarn.girlonthemoon.xyz Ok 👌

i made a new tumblr account to interact with fandom last week. while using the site today i got logged out and when i logged back in i was told my account was terminated. mullenweg will pay for this

@prologic@twtxt.net i’ll email you!

@movq@www.uninformativ.de I couldn’t agree more! It’s far from easy. I’m not free of this guilt either. But I’m hardly trying.

We got some colorful spots in the sky this evening: https://lyse.isobeef.org/abendhimmel-2025-07-08/

Image

@movq@www.uninformativ.de I’d love to have a Python script pushing my local CSV, too. But that’s never gonna fly, not in a thousand years. I can’t imagine that ever becoming reasonably stable without having to fix everything after the reverse-engineered API changes again.

… but you can’t set SDL_VIDEODRIVER=wayland globally, because that breaks Wine again …

… okay, the SDL backend works if you also set SDL_VIDEODRIVER=wayland.

@lyse@lyse.isobeef.org dmenu is a great example.

There have been several attempts at porting dmenu from X11 to Wayland. Well, not exactly “porting” it, more like rewriting it from scratch. Turns out: It’s not that easy.

dmenu is super fast and reliable. None of the Wayland rewrites are (at least none of the popular ones that I know of). They are either bloated and/or slow.

It takes a lot of discipline and restraint to write simple software and not blow up the codebase. This is much harder than people think. It’s a form of art, really.

@lyse@lyse.isobeef.org I do my timetracking in a little Python script, locally. Every now and then, I push the data to our actual service. Problem solved – but it’s a completely unpopular approach, they all want to use the web site. I don’t get it. Then, of course, when it’s down, shit hits the fan. (Luckily, our timetracking software is neither developed nor run by us anymore. It’s a silly cloud service, but the upside is that I’m not responsible anymore. 🤷)

Some of our oldschool devs tried to roll out local timetracking once, about 15 years ago. I don’t remember anymore why they failed …

This is developed inhouse, I’m just so glad that we’re not a software engineering company. Oh wait. How embarrassing.

Oh to be anonymous on the internet. That must be nice. 😅

@prologic@twtxt.net Ta!

@movq@www.uninformativ.de Yeah, luckily, there is the suckless project. I couldn’t live without dmenu!

… but the SDL backend is broken as well, albeit differently …

@movq@www.uninformativ.de Yeah, it’s a shitshow. MS overconfirms all my prejudices constantly.

Ignoring e-mail after lunch works great, though. :-)

Our timetracking is offline for over a week because of reasons. The responsible bunglers are falling by the skin of their teeth: https://lyse.isobeef.org/tmp/timetracking.png

1. The error message neither includes the timeframe nor a link to an announcement article.
   
2. The HTML page needs to download JS in order to display the fucking error message.
   
3. Proper HTTP status codes are clearly only for big losers.
   
4. Despite being down, heaps of resources are still fetched.
   

I find it really fascinating how one can screw up on so many levels. This is developed inhouse, I’m just so glad that we’re not a software engineering company. Oh wait. How embarrassing.

… which is probably a GTK bug.

QEMU on Wayland unusable, because it can’t grab the mouse … I’ll add it to my TODO list and investigate/report it eventually.

@movq@www.uninformativ.de This is a really good example of “simplicity” but achieves the intent and goals 👌

(Now, I don’t know if your screen reader can work with this. Let me know if it doesn’t.)

I don’t use a screen reader fortunately (actually they’re pretty garbage). So all good 👍 (I juse use full-screen zoom).

@prologic@twtxt.net Yeah, this really could use a proper definition or a “manifest”. 😅 Many of these ideas are not very wide spread. And I haven’t come across similar projects in all these years.

Let’s take the farbfeld image format as an example again. I think this captures the “spirit” quite well, because this isn’t even about code.

This is the entire farbfeld spec:

farbfeld is a lossless image format which is easy to parse, pipe and compress. It has the following format:

╔════════╤═════════════════════════════════════════════════════════╗
║ Bytes  │ Description                                             ║
╠════════╪═════════════════════════════════════════════════════════╣
║ 8      │ "farbfeld" magic value                                  ║
╟────────┼─────────────────────────────────────────────────────────╢
║ 4      │ 32-Bit BE unsigned integer (width)                      ║
╟────────┼─────────────────────────────────────────────────────────╢
║ 4      │ 32-Bit BE unsigned integer (height)                     ║
╟────────┼─────────────────────────────────────────────────────────╢
║ [2222] │ 4x16-Bit BE unsigned integers [RGBA] / pixel, row-major ║
╚════════╧═════════════════════════════════════════════════════════╝

The RGB-data should be sRGB for best interoperability and not alpha-premultiplied.

(Now, I don’t know if your screen reader can work with this. Let me know if it doesn’t.)

I think these are some of the properties worth mentioning:

• The spec is extremely short. You can read this in under a minute and fully understand it. That alone is gold.
  
• There are no “knobs”: It’s just a single version, it’s not like there’s also an 8-bit color depth version and one for 16-bit and one for extra large images and one that supports layers and so on. This makes it much easier to implement a fully compliant program.
  
• Despite being so simple, it’s useful. I’ve used it in various programs, like my window manager, my status bars, some toy programs like “tuxeyes” (an Xeyes variant), or Advent of Code.
  
• The format does not include compression because it doesn’t need to. Just use something like bzip2 to get file sizes similar to PNG.
  
• It doesn’t cover every use case under the sun, but it does cover the most important ones (imho). They have discussed using something other than RGBA and decided it’s not worth the trouble.
  
• They refrained from adding extra baggage like metadata. It would have needlessly complicated things.

@lyse@lyse.isobeef.org Nice shot! 😳

For example, I reckon software should treat stdout and stderr with care and never output logs or other such garbage to stdout that cannot possibly be useful in a UNIX pipeline 😅

@movq@www.uninformativ.de Yeah that’s why I’m striking this conversation with you 😅 Not only do I respect your opinion quite highly 🤣 But like you say (and I’ve read their philipshpy) it can be a bit “elitism” for sure. I’m genuinely interested in what we think of as software that “doesn’t suck”. Tb be honest I haven’t really put thought to paper myself, but I reckon if I did, I’d have some opinions/ideas…

@prologic@twtxt.net Hm, I wouldn’t say that. Go code could fall into that category as well.

Maybe this topic could use a blog post / article, that explains what it’s about. I’m finding it hard to really define what “suckless-like software” is. 🤔 (Their own philosophy focuses too much on elitism, if you ask me.)

@movq@www.uninformativ.de So you wouldn;t consider things written in Go to be “suckless”-esque? 🤔

@prologic@twtxt.net Ah, I’m referring to software that’s similar to that of suckless.org: Small, minimal codebases, small tools, but still useful. dmenu is probably the best example and also farbfeld.

Here’s the author of Anubis talking about some of their experiences:

https://xeiaso.net/blog/why-i-use-suckless-tools-2020-06-05/

(You can skip the long config and keybinds part.)

@eldersnake@we.loveprivacy.club Yeah well when you put it like that 🤣

@movq@www.uninformativ.de Curious what you would define as “suck less” software? (language agnostic of course!)

@movq@www.uninformativ.de Happy birthday and good health! :-)

Yesterday’s moon through the window: https://lyse.isobeef.org/mond-2025-07-06/

Image

The lack of suckless-like simple, hackable software these days is appalling.

The Linux installation on my main PC turned 14 today:

$ head -n 1 /var/log/pacman.log
[2011-07-07 11:19] installed filesystem (2011.04-1)

@eldersnake@we.loveprivacy.club This wasn’t always the case, though. Quake3, Quake4, Unreal Tournament 99 and 2004 are examples of games that used to run very well as native Linux games. But that was 20+ years ago …

Serasa Experian é uma empresa tão pilantra mas tão pilantra que agora estão descaradamente fazendo spam a partir de emails coletados do registro brasileiro de domínios (Registro.BR) é muito irritante.

“Layer: In conversation with Casey Reas”

https://layer.com/artists/casey-reas

@eldersnake@we.loveprivacy.club Yeah for sure! The thing that annoys me about a lot of this, is the sheer fact you can’t really self-host let alone self-train these things I’ve been playing around with AI at home over the past few months and building my own neural networks from scratch (in Go) with genetic algorithms on a few tasks and training sets, but man it’s hard™ 🤣 I feel like we’re doing something wrong here…

@eldersnake@we.loveprivacy.club This was an interesting read for sure! 👍 I don’t think it had anything I hadn’t already considered in terms of the ethical/moral points of view. I’m not sure where I stand myself either to be honest. I’ve forced myself to get familiar with the ecosystem and tooling, because in my line of work as a tech lead (staff engineer in sre) you don’t want to be that one guy that ya know 😉 Ethically/Morally though, I’m definitely with the sentiment of this post 😅 Much like the whole Crypto hype yaers back (if y’all remember?!) this is also one of the most energy hungry pieces of “tech” (if you can call it that?) in a while. Then there’s these other issues “stealing people’s work”, “reliance is causing humans to become cognitively weak and neural connections to shrink”, to name a few…

“Can you see circles or rectangles [on the experiment’s image]?
And does the answer depend on where you grew up?” — Anil Seth
https://www.theguardian.com/commentisfree/2025/jul/05/optical-illusions-see-world-perception #perception