The build tool called 'just' is actually pretty nice for orchestrating more complex builds.

The feature that makes it nice are target parameters and parametrized dependencies. They give it suprisingly increased amount of robustness over GNU Make.

I use it together with Buildroot in couple of occasions.

Vim 9.2 :----) let's go...

The lightline theme called (drumroll) monochrome is the only theme I've ever made.

It's 2026 and still not aligning too well with phones having touch screens :-/

Hmm... not with phones for that matter...

Anthropic just announced Claude Design... and it tooks just few days to get a slop copy of the service Github :----)

It's a great demonstration how nobody is and neither will make any money with AI, and also well deserve, karma is a bitch etc.

If China restrictions were not active, Anthropic would be in bankcrupty. The company is only aritficially alive. There's now one model in par with Sonnet and other not that far away from Opus, and both cheap as dirt.

It's all shit.

What they call agents, are actually markdown documents dumped at the beginning of every context (🤦‍♀️), or at most gradually pulled from a skill set on demand.

And it’s a very disturbing topic overall. I mean all this role playing of imaginary characters as part of daily work life is just… I don’ t know…

For stuff that I do with AI, which right now is to create an O with local LLM focus, Pi saves me from all that bullshit.

My Pi setup has neither subagents nor MCP servers. They are both useless and impose a fixed cost for every new context.

When I initialize a context I might dump relevant data instead of descriptions of agents and their personas (nnnggh…. thinking of this feels as physical pain tbh).

And this is how task management works:

1. /fork: creates a new session.
2. /tree: lets you time-travel through the context history and create new branches into the past to continue from.
3. /merge: combines the running context with a session given as a parameter.
4. Background task creation: I just prompt to PI “spawn a new process with fresh a session and …” or something.

The 3rd feature is /merge, which comes from the extension npm:pi-session-merge.

GNOME 47 compiled from scratch!

Phew, that was hard BUT I learned a lot of legacy lore while doing it :-)

My current list of Buildroot packages in my BR2_EXTERNAL:

❯ ls -1 package
accountsservice
appstream
bootc
colord
colord-gtk
composefs
dconf
evolution-data-server
flatpak
gcr3
gdm
geoclue
geocode-glib
gjs
gnome-bluetooth
gnome-console
gnome-control-center
gnome-desktop
gnome-keyring
gnome-online-accounts
gnome-session
gnome-settings-daemon
gnome-shell
gsound
gweather-locations
iso-codes
libadwaita
libei
libgrapheme
libgtop
libgusb
libgweather
libnma
libnotify
libportal
librest
libwacom
mozjs128
mutter
ostree
puu-installer
python-zxcvbn
vte-gtk4
xdg-desktop-portal
xdg-desktop-portal-gnome

They say that world has moved to Wayland but still it seems that gnome-settings-daemon hard depends on X11 version of libgtk3.

Infosec community right now…

Another git setting I realized that I want to have:

❯ git push
fatal: You didn't specify any refspecs to push, and push.default is "nothing".

Helps to keep focus imho :-)

I guess in modern days you'd want to put /var to separate partition instead of /home (works better with bootc containers and ostree).

I've packaged GNOME for BuildRoot.

The deployment is orchestrated like this.

Image:

- gnome-console
- gnome-shell
- gnome-control-center
- gnome-disks
- gnome-session
- gdm

Flatpak is populated with:

- org.gnome.Nautilus (Files)
- org.gnome.Logs
- org.gnome.Snapshot (Camera)
- org.gnome.Decibels (Audio player)
- org.gnome.Clocks
- org.gnome.Weather
- org.gnome.Contacts
- org.gnome.Characters
- org.gnome.Papers (Document Viewer)
- org.gnome.baobab (Disk Usage Analyzer)
- org.gnome.FileRoller (Archive Manager)
- org.gnome.Calculator
- org.gnome.Calendar
- org.gnome.Loupe (Image Viewer)
- org.gnome.Maps
- org.gnome.TextEditor

Image builds themselves are bootc containers.

Git configuration is nice to keep in .config/git/config, as installation scripts and other tools tend to like write into ~/.gitconfig. They both are read when git starts.

I feel so much better of using Pi now as the reference client in my local infrastructure project Puu,:

https://mariozechner.at/posts/2026-03-25-thoughts-on-slowing-the-fuck-down/

For majority, I share his opinions.

I don't like AI. That's why I work on Puu.

There it is: the AI monster.

Grace Blackwell is the cultural icon of this decade delivering the slop.

has been a long time, at least two years, but making some music with bitwig. let's see what this turns into :-) just early drafting...

I like spreadsheets. They are a great help for figuring out stuff. For Google's services I use exactly the spreadsheet, Keep and YouTube, and that's it.

I've been wanting a TUI spreadsheet for a while but I only recently found sc-im. This is superb :-)

I need to figure out at some point how can I replicate something like GOOGLEFINANCE with Lua scripting capabilitie. I use it all the time in Google's spreadsheet.

You heard it here first: Mastodon 5.0 (eta Oct-Dec 2026) will introduce major improvements to the core user experience. We're making Mastodon the most human-centred software on the #SocialWeb.

That’s where you come in.

Discovery Week 🗓️ 11-15 May 2026

Join our Head of Design @imanijoy for a jam-packed 5 day sprint inviting stakeholders from within and beyond Mastodon to weigh in on the future of the product.

See how you can get involved and contribute: https://app.hi.events/events/6360/mastodon-design-team

Re-located from kernel.org to:

https://gitlab.com/tpm-protocol

And merge requests are allowed :D And issues too.

#rustlang

I'm developing my own ostree and BuildRoot based operatingy system:

- https://codeberg.org/puu
- There will be puu-desktop and puu-llm builds.
- puu-desktop uses ext4.
- puu-llm uses ext4 + xfs for the models.
- puu-llm hosts k3s, llm-d and generally very latest of stack for running local LLM modesl.
- GNOME build is tough and I'm working on it but I have plan how to make in happen on BuildRoot.
- Given being BR2_EXTERNAL, builds and configures with beloved kbuild :-)

Despite having puu-llm build this project disregards AI contributions.

That said. I don't see it as a crime that you generate some initial code with LLM.

I do that sometimes too especially when I need to get an idea of e.g. alien projec. However, usually I do also spend week or few applying hard manual labor to make the actual code change I want to do despite having some random slop that functionality fits the bill.

This is what I do accept but it is generally best just to say plain no in README.md as most people will likely not be able to do such weighting.

[The logo image artwork is copyrighted by me (drawn with Inkscape) and licensed with CA BY-SA 4.0]

.gitignore I always specify always specify for repositories that are cloned as part of directory tree (such as my root home directory):

/*