š§® USERS:1 FEEDS:2 TWTS:1439 ARCHIVED:89607 CACHE:2612 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1438 ARCHIVED:89599 CACHE:2610 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1437 ARCHIVED:89595 CACHE:2607 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1436 ARCHIVED:89590 CACHE:2613 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1435 ARCHIVED:89587 CACHE:2614 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1434 ARCHIVED:89577 CACHE:2615 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1433 ARCHIVED:89576 CACHE:2615 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1432 ARCHIVED:89571 CACHE:2612 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1431 ARCHIVED:89562 CACHE:2642 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1430 ARCHIVED:89185 CACHE:2622 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1429 ARCHIVED:89174 CACHE:2643 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1428 ARCHIVED:89170 CACHE:2645 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1427 ARCHIVED:89169 CACHE:2645 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1426 ARCHIVED:89109 CACHE:2646 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1425 ARCHIVED:89098 CACHE:2646 FOLLOWERS:22 FOLLOWING:14
@movq@www.uninformativ.de WE NEED MORE BACKUPS!!!!!!!!!!!1
š§® USERS:1 FEEDS:2 TWTS:1424 ARCHIVED:89083 CACHE:2639 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1423 ARCHIVED:89080 CACHE:2639 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1422 ARCHIVED:89079 CACHE:2639 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1421 ARCHIVED:89072 CACHE:2635 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1420 ARCHIVED:89069 CACHE:2633 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1419 ARCHIVED:89067 CACHE:2632 FOLLOWERS:22 FOLLOWING:14
How the 1% stole minimalism (then threw it away) ā Read more
ok i really like XLOV. 1&Only is a great song. so vibe-y and sensual. and they released it in pride month too they Get It https://www.youtube.com/watch?v=NBZgirj_C2Y
@lyse@lyse.isobeef.org @kat@yarn.girlonthemoon.xyz Colorized manpages have been a thing for a very long time:

Problem is, hardly anybody knows this, because you configure this by ⦠drumroll ⦠overwriting TERMCAP entries of less in your ~/.bashrc:
export LESS_TERMCAP_md=$'\e[38;5;3m' # Bold⨠export LESS_TERMCAP_me=$'\e[0m' # End Bold
export LESS_TERMCAP_us=$'\e[4;38;5;6m' # Underline⨠export LESS_TERMCAP_ue=$'\e[0m' # End Underline
export GROFF_NO_SGR=1 # Needed since groff 1.23
š§® USERS:1 FEEDS:2 TWTS:1418 ARCHIVED:89054 CACHE:2625 FOLLOWERS:22 FOLLOWING:14
š§® USERS:1 FEEDS:2 TWTS:1417 ARCHIVED:89028 CACHE:2602 FOLLOWERS:22 FOLLOWING:14
š§® 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:
š
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:
And GNOME used to have them, too:
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 (
) 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. :-DHereā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:
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 ā¦
š§® 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
š§® USERS:1 FEEDS:2 TWTS:1407 ARCHIVED:88509 CACHE:2521 FOLLOWERS:22 FOLLOWING:14
š§® 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
š§® 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