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.)
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?
Uma boa colaboração é quando o resultado é melhor que a soma das partes... e assim é com o Altar que juntou Sunn O))) e Boris.
Um disco bom para ouvir com fones que gostem de graves, como se constata logo na primeira faixa do album, Etna:
https://youtu.be/rnsXA6xM5UE 
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. 🤓
#semcomentarios
Os #Caretos de Lazarim e o Carnaval de #Lazarim, em #Lamego, foram premiados nesta competição, pela qualidade e originalidade de 2 fantásticas imagens. Muitos parabéns aos autores Filipe Salgado e António Alves Tendim!
Vê todas as fotos vencedoras: https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Folklore_2025/Winners
#wikilovesfolklore2025
The Lazarim Carnival in Lamego’s village of Lazarim, Douro, is famed for its striking wooden masks and costumes by António Alves Tedim 
The Caretos de Lazarim carnival in Lamego, northern Portugal, is famous for its hand-carved wooden masks by Afsalgado
https://www.dn.pt/sociedade/viticultores-manifestam-se-na-r%C3%A9gua-deixam-carrinhas-e-tratores-e-a-p%C3%A9-bloqueiam-ponte-da-r%C3%A9gua
#douro
Foto de um cartaz numa manifestação, que diz "A falta de Liberdade de quem não pode estar aqui incomoda-me"
The first apples of 2025
> 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
😏
Tech is no longer interesting. I need to find a new field.
Elektro-Totós Vol I: corrente alternada
https://www.bitecode.dev/p/brett-cannon-on-python-humans-and
Recorte jornal. Diz: "Num contexto assim, pode-se, sim, falar de 《imigração desregulada》, mas apenas no sentido em que o Estado não consegue dar resposta aos direitos de quem está cá, de quem é mais explorado que os locais, trabalha, desconta, paga impostos, faz compras. A 《desregulação》 é do Estado, não das pessoas que migram."
https://www.publico.pt/2025/07/11/azul/opiniao/armas-mundo-chamas-2139779
#criseclimática
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.)
>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.
$ 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
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.
https://gist.github.com/villares/560e231da78cd1b8f5701c5a6897348f
captura de tela mostra na parte de cima uma planilha de Excel e na parte de baixo um documento de Word.
Quatro projectos votados na assembleia da república: os que pedem o reconhecimento do estado da Palestina, a independência da Palestina e uma solução de paz e respeito pelos direitos humanos foram chumbados, o que diz para não reconhecer a Palestina com estado soberano foi aprovado. O lado derrotado: L, PCP, BE, PAN, JPP O lado vencedor: PSD, CH, IL, CDS-PP Indecisos: PS
https://gist.github.com/villares/177c2323d424d5b2b0de49570fb4e2fd?permalink_comment_id=5673097#gistcomment-5673097
#ptpol 
#fridayreads #bookstodon 
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).
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.)
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.