@bender@twtxt.net That is a noble goal. We can talk about that â as long as it doesnât mean giving up essential freedoms like choosing which software you can run on your device (without having to ask someone for permission).
@prologic@twtxt.net Iâm not smart enough to answer that question. đ Certainly feels like unregulated capitalism. Governments being too slow and/or unwilling to intervene ⊠Itâs a mess.
@thecanine@twtxt.net I sure hope thereâs going to be push back. Is it going to happen, realistically? I donât know.
@prologic@twtxt.net Yes, this is another instance of restricting âpersonalâ computing. You wonât be able to install arbitrary software anymore (âsideloadingâ, as they call it).
Itâs not unique, itâs not new. Boiling the frog alive.
Weâre heading towards this: https://www.gnu.org/philosophy/right-to-read.html
RIP Android:
https://9to5google.com/2025/08/25/android-apps-developer-verification/
Since nobody is going to push back on this (I donât even know if that would be possible), this is going to be a reality on every platform sooner or later.
Iâd guess in 20, 30 years, there wonât be âPCsâ anymore. No more home computing, no more âI just write my own softwareâ. You wonât own devices anymore, itâll all be rented and the landlord will tell you what you can do with it.
I hope that Iâm wrong, but given where we are today, I donât think that I will be.
@prologic@twtxt.net Anything above a couple hundred Euros. đ The current Epson LX-350 appears to be not that pricey, though. đ€
I mean, what do you want to do with it? If you want to use this as an actual printer for daily use, Iâd get a laser printer instead, because theyâre very reliable and the print quality is top notch.
I got my dot matrix printer mostly for experiments and nostalgia, so I wouldnât want to pay something like 300-400⏠for it.
@prologic@twtxt.net Itâs quite similar to how escape sequences work in a terminal. ASCII text is printed as ASCII text and then an escape sequence can make it bold or underline and so on. Other escape sequences allow you to say âthe following $n
bytes are part of a bitmap imageâ, and then this gets printed at whatever the current position is (somewhat similar to SIXEL in a terminal).
Itâs just that the units are a bit weird, because this is all done in bloody inch. đ
@prologic@twtxt.net Hereâs one: https://github.com/vmykh/printer_labs/blob/master/escp2ref.pdf
@prologic@twtxt.net Yeah, those POS thingies are similar. Thereâs âESC/POSâ as a variant of âESC/Pâ, if Iâm not mistaken.
All I can say is, when I go to big stores like Amazon, then I have trouble finding âtraditionalâ dot matrix printers for use at home. đ Epson still sells them, but theyâre more expensive than my laser printer was. So yeah, they still exist, just expensive, by the looks of it.
@thecanine@twtxt.net Thatâs cute. đ (Why Clippy, though? đ )
@prologic@twtxt.net Hmm, good question. I havenât checked the market, I got mine from someone I know. But to be honest, Iâd suspect that buying a used one is actually your best shot, because there is virtually no market for these devices anymore, meaning new ones are very, very expensive. đ«€
FWIW, I have an OKI Microline 3390eco. Good thing is, you can still buy new cartridges for it.
If you want to buy a new device, check if it supports the âESC/Pâ standard. Thatâs very widely supported.
Should I go on a tour with these hot air balloons some day? Not sure if itâs scary as hell. đ
This is why I love tech from that era.
Write bytes to a parallel port and stuff happens. If itâs just ASCII bytes, then it will print ASCII text. Even the simplest programs can use a printer this way.
With a little bit of ESC/P, you can print images and other fancy stuff. Thatâs what I did this morning â never worked with ESC/P before, now I can print images. Itâs not that hard.
Hayes-compatible modems are similar: Write some AT commands to the serial port and the modem does things. This isnât even arcane knowledge, itâs explained in the printed manual.
Maybe Iâm wearing rose-tinted glasses here, but I think with all this old stuff, you get useful results very quickly and the manuals are usually actually helpful. Itâs so much easier to get started and to use this hardware to the full extent. Much less complexity than what we have today, not a ton of libraries and dependencies and SDKs and cloud services and what not.
@lyse@lyse.isobeef.org Aww, yeah. đ (Reminds me, I havenât paid attention to the sunset in quite a while âŠ)
@lyse@lyse.isobeef.org When/if I can pull it off, there will be videos! đ
I never used hardcopy terminals, either. We did have a dotmatrix printer, but that was just used as a regular printer.
Inkjets, I donât know. They were pretty fascinating and cool when they came out. A lot faster than dotmatrix and obviously quiter. They never gave me much trouble, actually. But I switched to a laser printer long before crap like DRMâed ink cartridges became a thing.
Hereâs an interesting thought/angle on this topic:
gemini://gemini.conman.org/boston/2025/08/21.1
A further check showed that all the network blocks are owned by one organizationâTencent [4]. Iâm seriously thinking that the CCP (Chinese Communist Party) encourage this with maybe the hope of externalizing the cost of the Great Firewall [5] to the rest of the world.
Sooooooooo, things happened, and I now have a dot matrix printer again. đđ
(One of the end goals is to simulate a hardcopy terminal on my old box. Iâm waiting for another cable to arrive, I donât have USB there. And then use ed(1)
like it was meant to be used! đ
)
@lyse@lyse.isobeef.org @prologic@twtxt.net Itâs too real, isnât it? đ€Ł
The GPG signatures of my software tarballs have been wrong for years (because Iâve been using rsync wrong, funny enough, it wasnât a GPG issue) and nobody ever noticed. (They still are wrong at the moment, because I havenât pushed the fix, yet.)
This confirms that this is just a total waste of time. Nobody ever checks this. Maybe this matters if youâre a distro, but why even bother as a single person âŠ
@thecanine@twtxt.net Wow. Iâm not an artist in any way, but I have tried to make icons for programs or fonts every now and then. Making something that is still recognizable at so few pixels is hard. Hats off!
Please enjoy this horrible madness: https://userinyerface.com/game.html
@lyse@lyse.isobeef.org Well, now that is pretty impressive. Upcycling ftw.
UNIX: A History and a Memoir by Brian Kernighan
https://www.youtube.com/watch?v=WEb_YL1K1Qg
I could listen to him all day.
Okay, often times, these âemployer gimmicksâ are just silly, but this one did make me laugh:
@lyse@lyse.isobeef.org Oh dear. đ So glad that WfH is a thing now. Imagine how utterly annoying it would be if they expected you to still come in despite this âŠ
Another wave of tens of thousands of hints by the same bot on the same file:
https://movq.de/v/61f8d39d2f/s.png
Thereâs probably a simple explanation for this: Maybe this bot was written with âAIâ and itâs simply complete garbage.
This isnât a serious threat for my low-profile website â yet. Canât wait for this to get worse âŠ
This genre is great for background music: https://www.youtube.com/watch?v=nâSX54AUZU
@eric@itsericwoodward.com I guess it is. đ
@bender@twtxt.net curl -s gopher://âŠ
does that for you.
Whatâs Missing from âRetroâ: gopher://midnight.pub/0/posts/2679
Hard to believe that this song is from 1985:
@prologic@twtxt.net They would know how to do that, but the issue was anything else, like switching workspaces or opening a terminal window or any window at all. đ
We did an experiment at work today: Do I even need to lock my laptop when Iâm gone or is nobody able to use it anyway?
It went as expected. đ€Ł
@prologic@twtxt.net Iâm so tired of this. (Thatâs the goal. They want to wear people down.)
@kat@yarn.girlonthemoon.xyz If youâre willing to ignore that itâs proprietary software, then Windows used to be pretty good. Like, 25 years ago. After Windows 2000 (or maybe XP) it went downhill fast. Kind of makes me sad, actually. đ
apt
manpage of Ubuntu recently, which, for some reason, uses blue text in one place:
Ah, so apparently they donât like writing manpages anymore and instead use XML:
https://salsa.debian.org/apt-team/apt/-/blob/main/doc/apt.8.xml
And then they use XSLT on top and what not:
https://salsa.debian.org/apt-team/apt/-/blob/main/doc/manpage-style.xsl.cmake.in
Itâs not even explicitly blue:
https://salsa.debian.org/apt-team/apt/-/blob/main/doc/apt.ent?ref_type=heads#L17
Abstractions upon abstractions upon abstractions.
@kat@yarn.girlonthemoon.xyz Oh no. đš Backups! We need more backups!
You can explicitly use colors in manpages. I saw this in the apt
manpage of Ubuntu recently, which, for some reason, uses blue text in one place:
https://movq.de/v/de5ab72016/s.png
Makes little sense to me. Iâm glad that most manpages donât do this. I wouldnât want unicorn vomit all over the place.
Using colors can be done using the low level commands \m
and \M
:
.TH foo_program 3
\m[blue]I'm blue\m[], da ba dee.
\m[red]\M[yellow]I'm red on yellow.\m[]\M[]
This is quite horrible.
Spiders are the only web developers that enjoy finding bugs.
@eldersnake@we.loveprivacy.club Yeah, itâs really the last thing we need. Iâd love to see X11 getting more attention â but not like this âŠ
In case you were blissfully unaware: https://utcc.utoronto.ca/~cks/space/blog/unix/XLibreIsExplicitlyPolitical
@bender@twtxt.net This should be a core feature, no configuration required. đ€
@kat@yarn.girlonthemoon.xyz On the one hand, all these programs have a very long history and the technology behind manpages is actually very powerful â you can use it to write books:
https://www.troff.org/pubs.html
I have two books from that list, for example âThe UNIX programming environmentâ:
https://movq.de/v/c3dab75c97/upe.jpg
Itâs a bit older, of course, but it looks and feels like a normal book, and it uses the same tech as manpages â which I think is really cool. đ
Itâs comparable to LaTeX (just harder/different to use) but much faster than LaTeX. You can also do stuff like render manpages as a PDF (man -Tpdf cp >cp.pdf
) or as an HTML file (man -Thtml cp >cp.html
). I think I once made slides for a talk this way.
On the other hand, traditional manpages (i.e., ones that are not written in mandoc) do not use semantic markup. They literally say, âthis text is bold, that text over here is italicsâ, and so on.
So when you run man foo
, it has no other choice but to show it in black, white, bold, underline â showing it in color would be wrong, because thatâs not what the source code of that manpage says.
Colorizing them is a hack, to be honest. Youâre not meant to do this. (The devs actually broke this by accident recently. They themselves arenât really aware that people use colors.)
If mandoc and semantic markup was more commonly used, I think it would be easier to convince the devs to add proper customizable colors.
(Just for fun, SuSE Linux 6.4 from ~25 years ago: https://movq.de/v/dc62d0256c/s.png )
@lyse@lyse.isobeef.org @kat@yarn.girlonthemoon.xyz Colorized manpages have been a thing for a very long time:
https://movq.de/v/81219d7f7a/s.png
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
Speaking of manpages:
âMan pages are great, man readers are the problemâ
https://whynothugo.nl/journal/2025/04/09/man-pages-are-great-man-readers-are-the-problem/
mandoc is nicer to read/write than the man
macro package and, most importantly, itâs semantic markup.
HTML output is a bit broken in GNU groff, though (OpenBSD on the left, GNU on the right):
https://movq.de/v/f1898e648f/s.png
đ€
Still, Iâm inclined to convert my manpages to mandoc.
@kat@yarn.girlonthemoon.xyz I still havenât tried it. đ€ Some day, perhaps âŠ
@kiwu@twtxt.net Hello. đ
In 1996, they came up with the X11 âSECURITYâ extension:
https://www.reddit.com/r/linux/comments/4w548u/what_is_up_with_the_x11_security_extension/
This is what could have (eventually) solved the security issues that weâre currently seeing with X11. Those issues are cited as one of the reasons for switching to Wayland.
That extension never took off. The person on reddit wonders why â I think itâs simple: Containers and sandboxes werenât a thing in 1996. It hardly mattered if X11 was âinsecureâ. If you could run an X11 client, you probably already had access to the machine and could just do all kinds of other nasty things.
Today, sandboxing is a thing. Today, this matters.
Iâve heard so many times that âX11 is beyond fixable, itâs hopeless.â I donât believe that. I believe that these problems are solveable with X11 and some devs have said âyeah, we could have kept working on itâ. Itâs that people donât want to do it:
Why not extend the X server?
Because for the first time we have a realistic chance of not having to do that.
https://wayland.freedesktop.org/faq.html
Iâm not in a position to judge the devs. Maybe the X.Org code really is so bad that you want to run away, screaming in horror. I donât know.
But all this was a choice. I donât buy the argument that we never would have gotten rid of things like core fonts.
All the toolkits and programs had to be ported to Wayland. A huge, still unfinished effort. If that was an acceptable thing to do, then it would have been acceptable to make an âX12â that keeps all the good things about X11, remains compatible where feasible, eliminates the problems, and requires some clients to be adjusted. (You could have still made âX11X12â like âXWaylandâ for actual legacy programs.)
I wasnât really aware until recently that programs canât choose their own windowâs position on Wayland. This is very weird to me, because this was not an issue on X11 to begin with: X11 programs can request a certain position and size, but the X11 WM ultimately decides if that request is being honored or not. And users can configure that.
But apparently, this whole thing is a heated debate in the Wayland world. đ€
âWayland Will Never Be Ready For Every X.Org Userâ
This is just the universe telling me to reduce my screen time.
@lyse@lyse.isobeef.org To be fair, I did first notice this a while ago. But no monitor I ever had showed burn-ins like this (be it TFT or CRT), so I didnât know that I should have sent it back. And then it got worse over time and now I see ghost images after 20-30 minutes. :(
@kat@yarn.girlonthemoon.xyz Ooooooohhhhh, nice đČ
Really, it wonât be long until I give the world the finger and move everything behind Gopher or Gemini. Itâll be a while until the bots find me there.
@prologic@twtxt.net Iâd expect a custom build like that to cost at least 50â000⏠here in Europe. Used campers with 100â000 - 200â000 km already on their clock are 20-40kâŹ, apparently. đ
gcr
thing running with debug logs enabled that print stuff like âsending secret exchange: âŠâ? Is this healthy?)
@lyse@lyse.isobeef.org Looks like it. đ€ Didnât dig deeper into this, just uninstalled it. đ„Ž
@lyse@lyse.isobeef.org 4 years. đ«€
Do I buy a new monitor or do I live with the burn-ins all the time? Itâs getting annoying. When I edit images in GIMP, I have to double check if something is a pixel or a burn-in.
@prologic@twtxt.net If anything looks expensive, then itâs that. đ
Stuff that nobody needs:
systemctl uses ANSI escape codes to underline text (\e[4m
) and then it also uses special escape codes â that Wikipedia classifies as ânot in the standardâ, but I havenât looked it up â to change the color of the underline. That color change is barely noticeable in the first place.
Some terminals donât support this and now my systemctl output is blinking because of that.
(Now why is that GNOME gcr
thing running with debug logs enabled that print stuff like âsending secret exchange: âŠâ? Is this healthy?)
You know youâre getting old when thereâs quite a few scripts in your ~/bin
that you use daily, but you havenât edited them once in well over 10 years âŠ
@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.)
@kat@yarn.girlonthemoon.xyz dmenu is such a great tool. So simple, yet so versatile.
@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. đ„Ž
@lyse@lyse.isobeef.org True, at least old versions of KDE had icons:
https://movq.de/v/0e4af6fea1/s.png
GNOME, on the other hand, didnât, at least to my old screenshots from 2007:
https://www.uninformativ.de/desktop/2007%2D05%2D25%2D%2Dgnome2%2Dlaptop.png
I switched to Linux in 2007 and no window manager I used since then had icons, apparently. Crazy. An icon-less existence for 18 years. (But yeah, everything is keyboard-driven here as well and there are no buttons here, either.)
Anyway, my draft is making progress:
https://movq.de/v/5b7767f245/s.png
I do like this look. đ
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:
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.
@lyse@lyse.isobeef.org So it might just be what the youngsters call a âskill issueâ? đ
@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.
I was drafting support for showing âapplication iconsâ in my window manager, i.e. the Firefox icon in the titlebar:
https://movq.de/v/0034cc1384/s.png
Then I realized: Wait a minute, lots of applications donât set an icon? And lots of other window managers donât show these icons, either? Openbox, pekwm, Xfce, fvwm, no icons.
Looks like macOS doesnât show them, either?!
Has this grown out of fashion? Is this purely a Windows / OS/2 thing?
@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.
/short/
if it's of this useless kind. Never thought that they ever actually will improve their Atom feeds. Thank you, much appreciated!
@lyse@lyse.isobeef.org I might need that script as well. đđ
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
âŠ
@lyse@lyse.isobeef.org The cynic in me says: âItâs not bleeding edge, itâs from 2008!â Thatâs not fair, though, looks like the issue only arose in libinput in 2019. And maybe these weird mice are super rare. Dunno.
@lyse@lyse.isobeef.org The underlines are a bit much, yes. It appears to be related to my font (Helvetica) ⊠Maybe they do some Unicode trickery these days, I donât know. đ«€
@lyse@lyse.isobeef.org Whatâs bleeding edge? The mouse? Yeah, maybe. đ I didnât buy that on purpose and didnât even know hi-res mouse wheels were a thing âŠ
Since Wayland compositors handle input devices on a lower level than X11 window managers, every compositor has to figure out on their own what a âmouse wheel clickâ is:
(I think âWayland compositorâ is a misnomer. They are full-blown display servers that also do compositing, plus Wayland window management, plus X11 window management.)
One can only hope that all this eventually gets moved into the wlroots library. (Iâm not sure if thatâs possible, nor if people would want that.)
I wore a Kubernetes shirt, in public, by accident, and now I feel dirty and ashamed. đą
@kat@yarn.girlonthemoon.xyz I kind of like XML because itâs mostly well-defined and easy for humans to read (unlike YAML, which is a complete mess, imho) ⊠and at the same time, it can get complicated really fast. đ«€ But at least itâs plain-text â thatâs the important part in this case. đ
Xfce does one thing very right: It stores its settings in plain-text XML files. This allows me to easily read, track, and maybe even distribute these settings to other machines.
(Unlike GNOMEâs dconf, which uses some binary file format. Fun fact: The older and now deprecated gconf also used XML files.)
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 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 âŠ
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. đą
@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
đ
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.
setpriv
on Linux supports Landlock.
@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.)