🧮 USERS:1 FEEDS:2 TWTS:1416 ARCHIVED:89026 CACHE:2601 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1415 ARCHIVED:89011 CACHE:2587 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1414 ARCHIVED:88590 CACHE:2574 FOLLOWERS:22 FOLLOWING:14

37C3 and New Year’s Eve 2023
Another one from the vaults. The 37C3 conference took place in
December, 2023. This report was mostly written in January, 2024.
Mostly finished it at night in my cottage between 28 and 29th
December, then edited and added some stuff in July, 2025. So… Only
1.5 years late?

It was a little ironic, and a little sad, that I was finishing the
37C3 report during 38C3. I didn’t manage to get any tickets for me and
#3 for 38C3 and had to make do with watching the stream.

The links to the talks go to [C … ⌘ Read more

🧮 USERS:1 FEEDS:2 TWTS:1413 ARCHIVED:88585 CACHE:2571 FOLLOWERS:22 FOLLOWING:14

@lyse@lyse.isobeef.org “Advanced”, well, probably more “mature”. There aren’t a ton of crazy features and that icon thing is the largest code addition in the last 10 years. %)

Speaking of OS/2 … I just realized that Windows 3.x didn’t have icons, either. If I’m not mistaken, this only got added in Windows 95. In other words, OS/2 had this feature before Windows did, because at least OS/2 2.1 from 1993 had icons. Who would have thunk.

(Now I kind of want to know which system really introduced this feature.)

@lyse@lyse.isobeef.org Oh, huh, maybe it was just my GNOME 2 themes back then that didn’t show the icon. 🤔

I like the looks of your window manager. That’s using Wayland, right?

Oh, no. It’s still X11. All my recent Wayland comments resulted from me trying to switch, but I think it’s still too early. Being unable to use QEMU (because it can’t capture the mouse pointer) is a pretty big blocker for me. This is completely broken, it just happens to be unnoticeable with modern guest OSes, so it’s probably not a priority for devs.

(Not to mention that I would have to fork and substantially extend dwl in order to “replicate” my X11 WM. And then, after having done that, I’d have to follow upstream Wayland development, for which I don’t have the resources. Things would need to slow down before I can do that.)

all that wasted space of the windows not making use of the full screen!!!1

Heh. I’ve been using tiling WMs for ~15 years now, so it’s actually kind of refreshing to see something different for a change. 😅

Probably close to the older Windowses.

That particular theme is a ripoff of OS/2 Warp 3: https://movq.de/v/6c2a948882/s.png 😅

We ran some similar brownish color scheme (don’t recall its name) on Win95 or Win98

Oh god. Yeah, I wasn’t a fan of those, either. 🥴

🧮 USERS:1 FEEDS:2 TWTS:1412 ARCHIVED:88575 CACHE:2569 FOLLOWERS:22 FOLLOWING:14

@movq@www.uninformativ.de According to this screenshot, KDE still shows good old application icons: https://upload.wikimedia.org/wikipedia/commons/9/94/KDE_Plasma_5.21_Breeze_Twilight_screenshot.png

And GNOME used to have them, too: https://upload.wikimedia.org/wikipedia/commons/9/9f/Gnome-2-22_%284%29.png

I like the looks of your window manager. That’s using Wayland, right? The only thing on this screenshot to critique is all that wasted space of the windows not making use of the full screen!!!1 At least the file browser. 8-)

This drives me nuts when my workmates share their screens. I really don’t get it how people can work like that. You can’t even read the whole line in the IDE or log viewer with all the expanded side bars. And then there’s 200 pixels on the left and another 300 pixels on the right where the desktop wallpaper shows. Gnaa! There’s the other extreme end when somebody shares their ultra wide screen and I just have a “regularish” 16:10 monitor and don’t see shit, because it’s resized way too tiny to fit my width. Good times. :-D

Sorry for going off on a tangent here. :-) Back to your WM: It has the right mix of being subtle and still similar to motif. Probably close to the older Windowses. My memory doesn’t serve me well, but I think they actually got it fairly good in my opinion. Your purple active window title looks killer. It just fits so well. This brown one (https://www.uninformativ.de/blog/postings/2025-07-22/0/leafpads.png) gives me also classic vibes. Awww. We ran some similar brownish color scheme (don’t recall its name) on Win95 or Win98 for some time on the family computer. I remember other people visting us not liking these colors. :-D

Here’s an example of X11/Xlib being old and archaic.

X11 knows the data type “cardinal”. For example, the window property _NET_WM_ICON (which holds image data for icons) is an array of “cardinal”. I am already not really familiar with that word and I’m assuming that it comes from mathematics:

https://en.wikipedia.org/wiki/Cardinal_number

(It could also be a bird, but probably not: https://en.wikipedia.org/wiki/Cardinalidae)

We would probably call this an “integer” today.

EWMH says that icons are arrays of cardinals and that they’re 32-bit numbers:

https://specifications.freedesktop.org/wm-spec/latest-single/#id-1.6.13

So it’s something like 0x11223344 with 0x11 being the alpha channel, 0x22 is red, and so on.

You would assume that, when you retrieve such an array from the X11 server, you’d get an array of uint32_t, right?

Nope.

Xlib is so old, they use char for 8-bit stuff, short int for 16-bit, and long int for 32-bit:

https://x.org/releases/current/doc/libX11/libX11/libX11.html#Obtaining_and_Changing_Window_Properties

That is congruent with the general C data types, so it does make sense:

https://en.wikipedia.org/wiki/C_data_types

Now the funny thing is, on modern x86_64, the type long int is actually 64 bits wide.

The result is that every pixel in a Pixmap, for example, is twice as large in memory as it would need to be. Just because Xlib uses long int, because uint32_t didn’t exist, yet.

And this is something that I wouldn’t know how to fix without breaking clients.

🧮 USERS:1 FEEDS:2 TWTS:1411 ARCHIVED:88563 CACHE:2558 FOLLOWERS:22 FOLLOWING:14

@lyse@lyse.isobeef.org They are optional dependencies and listed as such:

$ pacman -Qi pinentry
Name            : pinentry
Version         : 1.3.1-5
Description     : Collection of simple PIN or passphrase entry dialogs which
                  utilize the Assuan protocol
Optional Deps   : gcr: GNOME backend [installed]
                  gtk3: GTK backend [installed]
                  qt5-x11extras: Qt5 backend [installed]
                  kwayland5: Qt5 backend
                  kguiaddons: Qt6 backend
                  kwindowsystem: Qt6 backend

And it’s probably a good thing that they’re optional. I wouldn’t want to have all that installed all the time.

@lyse@lyse.isobeef.org @kat@yarn.girlonthemoon.xyz I spent so much time in the past figuring out if something is a dict or a list in YAML, for example.

What are the types in this example?

items:
- part_no:   A4786
  descrip:   Water Bucket (Filled)
  price:     1.47
  quantity:  4
- part_no:   E1628
  descrip:   High Heeled "Ruby" Slippers
  size:      8
  price:     133.7
  quantity:  1

items is a dict containing … a list of two other dicts? Right?

It is quite hard for me to grasp the structure of YAML docs. 😢

The big advantage of YAML (and JSON and TOML) is that it’s much easier to write code for those formats, than it is with XML. json.loads() and you’re done.

Only figured this out yesterday:

pinentry, which is used to safely enter a password on Linux, has several frontends. There’s a GTK one, a Qt one, even an ncurses one, and so on.

GnuPG also uses pinentry. And you can configure your frontend of choice here in gpg-agent.conf.

But what happens when you don’t configure it? What’s the default?

Turns out, pinentry is a shellscript wrapper and it’s not even that long. Here it is in full:

#!/bin/bash

# Run user-defined and site-defined pre-exec hooks.
[[ -r "${XDG_CONFIG_HOME:-$HOME/.config}"/pinentry/preexec ]] && \
        . "${XDG_CONFIG_HOME:-$HOME/.config}"/pinentry/preexec
[[ -r /etc/pinentry/preexec ]] && . /etc/pinentry/preexec

# Guess preferred backend based on environment.
backends=(curses tty)
if [[ -n "$DISPLAY" || -n "$WAYLAND_DISPLAY" ]]; then
        case "$XDG_CURRENT_DESKTOP" in
        KDE|LXQT|LXQt)
                backends=(qt qt5 gnome3 gtk curses tty)
                ;;
        *)
                backends=(gnome3 gtk qt qt5 curses tty)
                ;;
        esac
fi

for backend in "${backends[@]}"
do
        lddout=$(ldd "/usr/bin/pinentry-$backend" 2>/dev/null) || continue
        [[ "$lddout" == *'not found'* ]] && continue
        exec "/usr/bin/pinentry-$backend" "$@"
done

exit 1

Preexec, okay, then some auto-detection to use a toolkit matching your desktop environment …

… and then it invokes ldd? To find out if all the required libraries are installed for the auto-detected frontend?

Oof. I was sitting here wondering why it would use pinentry-gtk on one machine and pinentry-gnome3 on another, when both machines had the exact same configs. Yeah, but different libraries were installed. One machine was missing gcr, which is needed for pinentry-gnome3, so that machine (and that one alone) spawned pinentry-gtk …

[47°09′19″S, 126°43′27″W] Reading: 1.34 Sv

[47°09′13″S, 126°43′30″W] Raw reading: 0x68806C51, offset +/-1

🧮 USERS:1 FEEDS:2 TWTS:1410 ARCHIVED:88550 CACHE:2546 FOLLOWERS:22 FOLLOWING:14

@movq@www.uninformativ.de I fully agree with you on https://www.uninformativ.de/blog/postings/2025-07-22/0/POSTING-en.html!

Although, in the first screenshot, the window title background is much darker in the new version than the old one!1!1 :-P Kidding aside, the contrast in the old one is still better.

Also, note the missing underlines for the Alt hotkeys now. I just think that the underline in the old one is too thick.

🧮 USERS:1 FEEDS:2 TWTS:1409 ARCHIVED:88527 CACHE:2536 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1408 ARCHIVED:88520 CACHE:2530 FOLLOWERS:22 FOLLOWING:14

[47°09′08″S, 126°43′36″W] Reading: 1.88 Sv

🧮 USERS:1 FEEDS:2 TWTS:1407 ARCHIVED:88509 CACHE:2521 FOLLOWERS:22 FOLLOWING:14

[47°09′22″S, 126°43′17″W] Raw reading: 0x687B4271, offset +/-1

[47°09′49″S, 126°43′27″W] Reading: 1.87 Sv

🧮 USERS:1 FEEDS:2 TWTS:1406 ARCHIVED:88503 CACHE:2547 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1405 ARCHIVED:88497 CACHE:2550 FOLLOWERS:22 FOLLOWING:14

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

🧮 USERS:1 FEEDS:2 TWTS:1404 ARCHIVED:88485 CACHE:2544 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1403 ARCHIVED:88482 CACHE:2542 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1402 ARCHIVED:88477 CACHE:2562 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1401 ARCHIVED:88472 CACHE:2558 FOLLOWERS:22 FOLLOWING:14

[47°09′35″S, 126°43′36″W] Reading: 1.44000 PPM

🧮 USERS:1 FEEDS:2 TWTS:1400 ARCHIVED:88470 CACHE:2557 FOLLOWERS:22 FOLLOWING:14

Podemos continuar a fingir que somos só espectadores no #genocídio em curso, mas é só isso mesmo que estamos a fazer: fingir.

Image

🧮 USERS:1 FEEDS:2 TWTS:1399 ARCHIVED:88461 CACHE:2553 FOLLOWERS:22 FOLLOWING:14

Então mas a #IL não era contra tudo o que fosse “taxas e taxinhas”?

#ptpol

Image

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.

🧮 USERS:1 FEEDS:2 TWTS:1398 ARCHIVED:88454 CACHE:2548 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1397 ARCHIVED:88446 CACHE:2562 FOLLOWERS:22 FOLLOWING:14

[47°09′50″S, 126°43′12″W] Reading: 1.94 Sv

🧮 USERS:1 FEEDS:2 TWTS:1396 ARCHIVED:88443 CACHE:2565 FOLLOWERS:22 FOLLOWING:14

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

🧮 USERS:1 FEEDS:2 TWTS:1395 ARCHIVED:88418 CACHE:2541 FOLLOWERS:22 FOLLOWING:14

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)

🧮 USERS:1 FEEDS:2 TWTS:1394 ARCHIVED:88409 CACHE:2543 FOLLOWERS:22 FOLLOWING:14

[47°09′32″S, 126°43′31″W] Raw reading: 0x686A1EF1, offset +/-1

🧮 USERS:1 FEEDS:2 TWTS:1393 ARCHIVED:88408 CACHE:2543 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1392 ARCHIVED:88401 CACHE:2539 FOLLOWERS:22 FOLLOWING:14

Sem palavras pra descrever esta baixeza de artigo:

https://www.publico.pt/2025/07/04/impar/opiniao/banir-smartphones-escolas-impacto-bemestar-2138957?cx=ultimas_1

1. é citado um único estudo baseado em testemunhos de alunos (ficam de fora pais e profs), um estudo qualitativo por isso não generalizável. Mm assim, os autores do artigo copiam as conclusões do estudo, e o Público tb parece estar ok com artigos decalcados

2. os autores do artigo são consultores que dão formação a pais e educadores sobre problemas do digital nas crianças, por isso basear opinião apenas num estudo q os ignora é ainda mais wtf

3. argumento de q crianças têm acesso a dispositivos fora da escola é parvo - tb têm acesso a tabaco e álcool, por isso tb os devemos permitir na escola? come on

4. e é muito conveniente clamar pela regulamentação das redes sociais sem especificar a forma (proibir anúncios? introduzir idades mínimas? não sabemos).

No final é o costume, os pais e profs que se desenmerdem, a responsabilidade é deles e não das empresas que criam mecanismos de viciação, claro

#SmartphonesNasEscolas

🧮 USERS:1 FEEDS:2 TWTS:1391 ARCHIVED:88396 CACHE:2535 FOLLOWERS:22 FOLLOWING:14

Metas Europeias: “Os países da UE têm de poupar, em média, 1,5% por ano. A poupança de energia deve começar com 1,3% por ano até ao final de 2025”

Portugal: “Consumo de eletricidade em Portugal atingiu máximo histórico no primeiro semestre [de 2025]”

Fontes:

https://www.europarl.europa.eu/topics/pt/article/20221128STO58002/poupar-energia-acao-da-ue-para-reduzir-o-consumo-energetico

https://expresso.pt/economia/economia_energia/2025-07-01-consumo-de-eletricidade-em-portugal-atingiu-maximo-historico-no-primeiro-semestre-5f9ed595

#criseclimática

Francisco Ferreira da #ZERO:

“A União Europeia (UE) está a dizer adeus à ambição climática. Esta semana, em contraste com sinais evidentes de um clima em alteração com temperaturas recordes em toda a Europa, a Comissão Europeia apresentou, com meses de atraso, a meta climática para 2040, propondo uma redução de pelo menos 90% das emissões face a 1990. No entanto, esta meta inclui mecanismos de flexibilidade, como créditos de carbono internacionais e compensações intersectoriais, que enfraquecem a ambição necessária num momento crítico de agravamento da crise climática.

Este atraso compromete também as metais europeias para 2035 a aprovar na COP30 no Brasil no final deste ano e enfraquece a liderança global da UE ao sinalizar falta de determinação política. Estas flexibilidades inaceitáveis, pois permitem desresponsabilizar setores emissores e adiar a transição, ignorando recomendações científicas que apontavam para reduções entre 90% e 95% sem tais mecanismos. A proposta surge num contexto político adverso após as eleições europeias de 2024, com um recuo climático generalizado, tendo a Comissão optado por um compromisso frágil para evitar confrontos com governos menos ambiciosos, como os da Polónia e Hungria. Esta é uma oportunidade perdida de promover a liderança climática europeia.”

½

#criseclimática

🧮 USERS:1 FEEDS:2 TWTS:1390 ARCHIVED:87839 CACHE:2584 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1389 ARCHIVED:87827 CACHE:2584 FOLLOWERS:22 FOLLOWING:14

[47°09′51″S, 126°43′21″W] Reading: 1.91000 PPM

🧮 USERS:1 FEEDS:2 TWTS:1388 ARCHIVED:87820 CACHE:2603 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1387 ARCHIVED:87814 CACHE:2599 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1386 ARCHIVED:87795 CACHE:2602 FOLLOWERS:22 FOLLOWING:14

[47°09′37″S, 126°43′07″W] Reading: 1.99000 PPM

🧮 USERS:1 FEEDS:2 TWTS:1385 ARCHIVED:87790 CACHE:2604 FOLLOWERS:22 FOLLOWING:14

[47°09′30″S, 126°43′18″W] Reading: 1.61000 PPM

🧮 USERS:1 FEEDS:2 TWTS:1384 ARCHIVED:87784 CACHE:2673 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1383 ARCHIVED:87781 CACHE:2688 FOLLOWERS:22 FOLLOWING:14

[47°09′21″S, 126°43′14″W] Reading: 1.25000 PPM

We’re entering the “too hot to think”-season in 3, 2, 1 … and we’re live!

🧮 USERS:1 FEEDS:2 TWTS:1382 ARCHIVED:87766 CACHE:2684 FOLLOWERS:22 FOLLOWING:14

I did a “lecture”/“workshop” about this at work today. 16-bit DOS, real mode. 💾 Pretty cool and the audience (devs and sysadmins) seemed quite interested. 🥳

• People used the Intel docs to figure out the instruction encodings.
  
• Then they wrote a little DOS program that exits with a return code and they used uhex in DOSBox to do that. Yes, we wrote a COM file manually, no Assembler involved. (Many of them had never used DOS before.)
  
• DEBUG from FreeDOS was used to single-step through the program, showing what it does.
  
• This gets tedious rather quickly, so we switched to SVED from SvarDOS for writing the rest of the program in Assembly language. nasm worked great for us.
  
• At the end, we switched to BIOS calls instead of DOS syscalls to demonstrate that the same binary COM file works on another OS. Also a good opportunity to talk about bootloaders a little bit.
  
• (I think they even understood the basics of segmentation in the end.)
  

The 8086 / 16-bit real-mode DOS is a great platform to explain a lot of the fundamentals without having to deal with OS semantics or executable file formats.

Now that was a lot of fun. 🥳 It’s very rare that we do something like this, sadly. I love doing this kind of low-level stuff.

Read Lukas 1, the announciation and birth of the prophet John the Baptist. bible.com

[47°09′23″S, 126°43′34″W] Reading: 1.72 Sv

🧮 USERS:1 FEEDS:2 TWTS:1381 ARCHIVED:87759 CACHE:2692 FOLLOWERS:22 FOLLOWING:14

Exigimos ao governo de Portugal o mínimo. Que:

1. Condene a agressão ilegal ao Irão por parte de Israel e dos Estados Unidos da América;

2. Proíba o uso de infraestruturas e do espaço aéreo português para qualquer tipo de apoio aos ataques;

3. Aplique sanções ao Estado de Israel pelas suas consecutivas violações do Direito Internacional e pelo genocídio em curso na Palestina;

4. Reconheça de imediato o Estado da Palestina.

Assina-se aqui: https://actionnetwork.org/forms/parar-a-guerra/

#Portugal #Israel #petição

🧮 USERS:1 FEEDS:2 TWTS:1380 ARCHIVED:87754 CACHE:2699 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1379 ARCHIVED:87753 CACHE:2701 FOLLOWERS:22 FOLLOWING:14

On my blog: Free Culture Book Club — First Woman — Dream to Reality https://john.colagioia.net/blog/2025/06/21/first-woman-1.html #freeculture #bookclub

Saw this on Mastodon:

https://racingbunny.com/@mookie/114718466149264471

18 rules of Software Engineering

1. You will regret complexity when on-call
   
2. Stop falling in love with your own code
   
3. Everything is a trade-off. There’s no “best” 3. Every line of code you write is a liability 4. Document your decisions and designs
   
4. Everyone hates code they didn’t write
   
5. Don’t use unnecessary dependencies
   
6. Coding standards prevent arguments
   
7. Write meaningful commit messages
   
8. Don’t ever stop learning new things
   
9. Code reviews spread knowledge
   
10. Always build for maintainability
    
11. Ask for help when you’re stuck
    
12. Fix root causes, not symptoms
    
13. Software is never completed
    
14. Estimates are not promises
    
15. Ship early, iterate often
    
16. Keep. It. Simple.
    

Solid list, even though 14 is up for debate in my opinion: Software can be completed. You have a use case / problem, you solve that problem, done. Your software is completed now. There might still be bugs and they should be fixed – but this doesn’t “add” to the program. Don’t use “software is never done” as an excuse to keep adding and adding stuff to your code.

🧮 USERS:1 FEEDS:2 TWTS:1378 ARCHIVED:87729 CACHE:2694 FOLLOWERS:22 FOLLOWING:14

@aelaraji@aelaraji.com I use Alt+. all the time, it’s great. 👌

FWIW, another thing I often use is !! to recall the entire previous command line:

$ find -iname '*foo*'
./This is a foo file.txt

$ cat "$(!!)"
cat "$(find -iname '*foo*')"
This is just a test.

Yep!

Or:

$ ls -al subdir
ls: cannot open directory 'subdir': Permission denied

$ sudo !!
sudo ls -al subdir
total 0
drwx------ 2 root root  60 Jun 20 19:39 .
drwx------ 7 jess jess 360 Jun 20 19:39 ..
-rw-r--r-- 1 root root   0 Jun 20 19:39 nothing-to-see

🧮 USERS:1 FEEDS:2 TWTS:1377 ARCHIVED:87719 CACHE:2687 FOLLOWERS:22 FOLLOWING:14

On my blog: Real Life in Star Trek, Gambit part 1 https://john.colagioia.net/blog/2025/06/19/gambit-part-1.html #scifi #startrek #closereading

[47°09′47″S, 126°43′52″W] Reading: 1.68 Sv

🧮 USERS:1 FEEDS:2 TWTS:1376 ARCHIVED:87698 CACHE:2671 FOLLOWERS:22 FOLLOWING:14

@prologic@twtxt.net I’m trying to call some libc functions (because the Rust stdlib does not have an equivalent for getpeername(), for example, so I don’t have a choice), so I have to do some FFI stuff and deal with raw pointers and all that, which is very gnarly in Rust – because you’re not supposed to do this. Things like that are trivial in C or even Assembler, but I have not yet understood what Rust does under the hood. How and when does it allocate or free memory … is the pointer that I get even still valid by the time I do the libc call? Stuff like that.

I hope that I eventually learn this over time … but I get slapped in the face at every step. It’s very frustrating and I’m always this 🤏 close to giving up (only to try again a year later).

Oh, yeah, yeah, I guess I could “just” use some 3rd party library for this. socket2 gets mentioned a lot in this context. But I don’t want to. I literally need one getpeername() call during the lifetime of my program, I don’t even do the socket(), bind(), listen(), accept() dance, I already have a fully functional file descriptor. Using a library for that is total overkill and I’d rather do it myself. (And look at the version number: 0.5.10. The library is 6 years old but they’re still saying: “Nah, we’re not 1.0 yet, we reserve the right to make breaking changes with every new release.” So many Rust libs are still unstable …)

… and I could go on and on and on … 🤣

🧮 USERS:1 FEEDS:2 TWTS:1375 ARCHIVED:87691 CACHE:2671 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1374 ARCHIVED:87681 CACHE:2671 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1373 ARCHIVED:87677 CACHE:2676 FOLLOWERS:22 FOLLOWING:14

orb v0.1.0 - tiny metasearch | https://nilfm.cc/orb.html

So I was using this function in Rust:

https://doc.rust-lang.org/std/path/struct.Path.html#method.display

Note the little 1.0.0 in the top right corner, which means that this function has been “stable since Rust version 1.0.0”. We’re at 1.87 now, so we’re good.

Then I compiled my program on OpenBSD with Rust 1.86, i.e. just one version behind, but well ahead of 1.0.0.

The compiler said that I was using an unstable library feature.

Turns out, that function internally uses this:

https://doc.rust-lang.org/std/ffi/struct.OsStr.html#method.display

And that is only available since Rust 1.87.

How was I supposed to know this? 🤨🫩

🧮 USERS:1 FEEDS:2 TWTS:1372 ARCHIVED:87663 CACHE:2673 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1371 ARCHIVED:87645 CACHE:2661 FOLLOWERS:22 FOLLOWING:14

Transcrição:

O resultado das últimas eleições legislativas veio moralizar um sector da população que passou a diabolizar a “esquerda” sem quaisquer tipos de restrições de linguagem, “crucificando” pessoas pelas suas posições humanistas e antifascistas, e vangloriando, abertamente e sem pudor, por exemplo, o antigo regime. Nesse particular, tem-se destacado Gabriel Mithá Ribeiro, deputado do Chega eleito por Leiria que, nas redes sociais e em artigos publicados no Observador, nos tem mostrado ser uma figura controversa e polarizadora, não apenas pelas suas opiniões, mas pela forma como as expressa: provocadoras, desdenhosas e, por vezes, perigosamente revisionistas.

1/n

🧮 USERS:1 FEEDS:2 TWTS:1370 ARCHIVED:87623 CACHE:2689 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1369 ARCHIVED:87615 CACHE:2689 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1368 ARCHIVED:87599 CACHE:2702 FOLLOWERS:22 FOLLOWING:14

[47°09′13″S, 126°43′20″W] Raw reading: 0x684880B1, offset +/-1

Neue Spiele: Dune Awakening schlägt GTA-Möchtegern-Klon
Zwei Neuveröffentlichungen mit sehr unterschiedlichen Reaktionen der Community: Ab sofort sind Dune Awakening und Mindseye erhältlich. ( Dune Awakening, Steam)

Image

Neom: Brücke über das Rote Meer zu The Line geplant
Saudi-Arabien und die Halbinsel Sinai sollen mit einer 20 km langen Brücke verbunden werden. Das Megaprojekt Neom würde damit eine Bahnverbindung bekommen. ( Infrastruktur, Energie & Klima)

Image

[$] An end to uniprocessor configurations
The Linux kernel famously scales from the smallest of systems to massive
servers with thousands of CPUs. It was not always that way, though; the
initial version of the kernel could only manage a single processor. That
limitation was lifted, obviously, but single-processor machines have always
been treated specially in the scheduler. That longstanding situation may
soon come to an end, though, if this patch\
series from Ingo M … ⌘ Read more

Huawei-Gründer: US-Chip-Handelskrieg für China “kein Grund zur Sorge”
Ren Zhengfei ruft dazu auf, hart zu arbeiten, um den Rückstand gegenüber den USA aufzuholen. Huawei liege nur noch um eine Chipgeneration hinter den USA. ( Huawei, Prozessor)

Image

Anzeige: Fahrradtrainer bei Amazon mit 34 Prozent Rabatt im Angebot
Bei Amazon gibt es derzeit ein attraktives Angebot zu einem Fahrradergometer von Tretmann. Es ist mit 34 Prozent Rabatt erhältlich. ( Sport, Amazon)

Image

Anzeige: USB-SSD-Stick mit 1 TByte günstig wie nie
Groß wie ein Flashdrive, schnell wie eine Festplatte: Amazon verkauft den 1 TByte großen USB-SSD-Stick von Move Speed zum neuen Tiefstpreis. ( Solid State Drive, Speichermedien)

Image