Is it safe to get rid of slices allocated for /usr/src and /usr/obj if I'm not planning to build base system from source?
They are huge in default #OpenBSD layout, especially the latter, I'd rather redistribute the space between /usr/local and /home.

I might try building some software from ports later though, e.g. Rust 1.79 which was still building fine for i386 architechture, and maybe even Firefox 115 — old ESR version I use on my Linux boxes. But as far as I understand, it's supposed to be done under /usr/ports and I'd rather mount external storage for that.

This is what having no systemd in your system is like, when the system is idle — it's 99% idle.

Yep, I don't have a "modern browser" running, but the machine isn't a 56-core monster either, it's a Pentium-M machine from 20 years ago! But I can still have XMPP and Matrix chats using profanity and gomuks, browse Fedi, Gemini using Lagrange or amfora, read RSS feeds in newsraft, listen to music and watch HD videos with mpv and even browse some web using Netsurf or chawan — and I still have plenty of RAM left, like back in the day when this ThinkPad T43 was brand new. Except it's 2026 and OpenBSD 7.9 is still supported on this machine!

#snac2 with purge_static=true seems to have removed my avatar image aka pfp 😢

I suppose it could be somehow related to the fact that this instance is rather old and I have set that image as my avatar over a year ago and maybe it wasn't recorded as file that shouldn't be cleaned up.

I'll see what else got removed, I have backups…

OMG, Gajim 2.x for Windows is unusable! And mainly because of GTK4 — it doesn't respect system scaling and its own setting only goes up to 1.5x — everything is tiny! I can partially work this around with font setting in theming options, it works for chat logs, but not the contact list and other UI elements.
But what's even worse, GTK4 doesn't support Windows' rudimentary "tiling" window management features — it doesn't stick to screen edges, at all! You have to resize the window manually like in the old days.
I'm not making this up: https://dev.gajim.org/gajim/gajim/-/issues/12348
And corresponding GTK feature merge request is from 2021 (!): https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4252

Oh, and there is no main application menu — no button for it and no keyboard shortcut to make it visible, it's just gone! How do I browse services? How do I do anything at all, for which the main window has no button?
If I wasn't aware that 1.9.5 exists, I'd consider this port an early beta.

Losing to Qt as cross-platform UI toolkit makes sense like never before — even the few applications still relying on it, become impossible to use on switching to newer GTK version 😩

Russian bookseller fined for selling novels promoting ‘sexual anarchism’: https://novayagazeta.eu/articles/2026/01/10/russian-bookseller-fined-for-selling-novels-promoting-sexual-anarchism-en-news

Now WTF is sexual anarchism, are they organised and how can I join their ranks? 😊

Learning the fact that GOG Linux version only supports 32-bit systems made me think that using a 32-bit root to run it would be a crime and that this olde ThinkPad T43 is in fact the perfect computer to play this game on 👴

Pentium M forever!

Is Codeberg down? 🤔

This is the latest version of #Rust book, but is this indeed still true?
Having a Microsoft account to publish modules to public repo, for real?! 😲 This is even worse than requiring JavaScript to browse it.

Woah, JPEG XL is making a comeback in Chrome: https://windowsreport.com/google-revisits-jpeg-xl-in-chromium-after-earlier-removal/

Meanwhile Mozilla awaits for decoder to be re-implemented in Rust in order to bring it to Firefox: https://github.com/mozilla/standards-positions/pull/1064

All while current libjxl-based implementation works with a set of patches.
Google developer mentions animation support, with these patches all of the advanced features on JPEG XL test page work: advanced colour management, transparency, animations.

Forks of Firefox have these patches, Waterfox: https://github.com/BrowserWorks/waterfox/pull/2938
And Librewolf: https://codeberg.org/librewolf/source/src/branch/main/patches/JXL_improved_support.patch

Sadly, these fail to be applied cleanly to newer Firefox code base and no one seems to care enough to fix it.
It's not perfect, it might require some testing — and of course it would require porting to newer code base, but it does work!
See for yourself, here is my own build of old ESR (115): https://nosh0b10.m0xee.net/m0xEE/p/1763414039.727405
It also works on mobile: https://nosh0b10.m0xee.net/m0xEE/p/1762130588.104733
No, support for WebP is not broken — it's disabled on purpose, I have actually patched the about:config setting that made it optional back in after Mozilla for some reason (hehe 😏) removed it in version 119.

So this is what we could have today — without going the roundabout way with Rust. And Google claimed in the past that there is no interest for it — I'm interested, and we get support for AVIF, HEIF and WebP — in which I'm personally not interested in the slightest.
And libwebp, which Firefox uses for WebP support is not in Rust — but not only they are not waiting for Rust implementation, they make support for it non-optional right after critical vulnerability gets found in its code: https://thehackernews.com/2023/09/mozilla-rushes-to-patch-webp-critical.html
Vulnerability gets discovered in September, in October Mozilla releases Firefox 119: https://www.firefox.com/en-US/firefox/119.0/releasenotes/ removing image.webp.enabled from about:config making support for WebP non-optional. Support provided by exact same library affected by the vulnerability — albeit already patched.
No requirement for it being in Rust in sight!

Support for #WebP becomes mandatory, experimental incomplete support for JPEG XL can't even be enabled with image.jxl.enabled set to true in about:config — it can only be enabled at build time, by default it's only enabled in Nightly developer builds.

Why do these image formats get glaringly different treatment?

#jpegXL

This demonstrates quite well why low-effort image codecs are dead on arrival. And the explanation is quite simple — these aren't really image codecs, they were never designed to be that! These are video codecs applied to static images disguised as brand new image codecs: #WebP is VP9, HEIF is HEVC also known as H.265 and AVIF is AV1.
And indeed, for video even 8193x4320 leaves some headroom — not for photos, given how having a high-resolution camera system became a major selling point of high-end smartphones, even 16383x16383 might seem lacking tomorrow.

Or course this can be worked around as to a degree all of these are extensible, e.g. AVIF has advanced profile: https://en.wikipedia.org/wiki/AVIF#Profiles
According to Wikipedia:

Coded image items compliant to the AVIF Advanced profile may not have a total number of pixels greater than 35,651,584, a width greater than 16,384, or a height greater than 8,704. It is still possible to use the Advanced profile to create larger images using grid derivation.

Problem is — your existing software and even hardware might not support this advanced profile. WebPee has already already been extended to have the features listed in the table — and it is still severely limited.
So why bother supporting all this bestiary of formats, which are essentially gimmicks and not go all in with true image codec that has all the advantages and features and none of the limitations?
Hm-m-m… Indeed, why? 😏

#JPEG-XL

People on Fedi be like:

Yes, I'm thirty two, but I'm not sure I can call myself a computer programmer… 🥺
Oh, this? It's a vacuum cleaner I've built with Raspberry Pi, it uses 3 cameras to map the rooms and find paths around obstacles. It can also detect pets and greet them accordingly, depending whether it's a guinea pig or a rabbit. You can control it with this touch screen I've built on top of Arduino, and it has a Home Assistant module too! 🤩 And a Gemini interface — you can use any Gemini browser
There wasn't one that was comfortable to use on my Pinephone, so I had to make my own… 😅
But otherwise — yeah, I'm just a regular school teacher. 🤓 I teach orphanage kids simple sound design techniques using PureData and SuperCollider…

People outside Fedi are often like:

Yeah, I have some experience with web development — they have once tasked me with changing the font colour on our website from pink to red, and I did! 😎
They had to pay for Claude Code subscription though… Oh, and I've also used it to build this cool app — it creates calendar events for meetings it finds in my inbox, so I consider myself a mobile software developer too. It had deleted all my emails once and I don't know why… I'm still figuring this out! 😜

Does such a thing as transparent proxying still exist in the age of TLS pinning and needling? 🤔

Can I redirect outgoing connections to port 443 to my local proxy and tell Squid to expect such a development, so that fucking Android connected to my home router over WireGuard uses a proxy instead of rushing to the Internet directly?

There is iamb — a TUI Matrix client with support for SIXEL for images. Alacritty — the terminal emulator I use, doesn't have SIXEL support, but there is a fork of it that does. And these two work nicely together.
Well, almost — I have a laptop with only 8 gigabytes of RAM and I once noticed that while that combination was staying in the background for several days idling, almost everything else got swapped out — I started investigating and it turned out that Alacritty with iamb started occupying over 7 gigabytes, there is a leak somewhere.
Recently I've updated iamb and decided to check whether the issue is still there — Alacritty's memory usage when images are displayed seemed growing to a certain margin, but in a few minutes returning to normal limits. I've left it running on a laptop with 16 gigs, where it shouldn't be a problem and in a few days — he-he, still there: 39 gigabytes virtual memory size, 5 gigs resident.
Funny thing is: both projects are in that language, notorious for its memory safety. It's not really indicative of anything — I think the SIXEL fork is just low effort and has issues, but… Fedi LOVES such things: "A-ha, Rust software is leaky!"— so why not share it here? 😈

#snac2 allows for translations via .po files and on my instance I've used it to replace status action buttons' captions with colour emojis — makes the UI a bit nicer on a phone.
For favourite, boost and bookmark I've used the set that I already use in my BloatFE and the rest are just initial rough ideas — which, I have to admit, aren't perfect: crossed out speaker and crossed out bell, garbage bin and big red cross are a bit confusing as to what they might mean — we'll see if I can come up with something better.

And I've also brought back Mastodon's famous "toot" button. Yes, the one with the elephant 😏

@newt@stereophonic.space Look, man, it's like they've read all my Fedi posts and decided to make this even worse: https://www.apple.com/newsroom/2025/06/apple-introduces-a-delightful-and-elegant-new-software-design/

That's precisely what I was talking about — now everything has "volume", but they've got rid of the colours almost entirely. Now everything is just a reflection of your wallpaper — even more translucency, ya-ay!

It's like the new level of bad. Can't believe that this company was once pioneering UI design, this is just pure unadulterated unusable visual garbage!

Wow, the notifications in tut the TUI fedi client are now in correct order when using it with #snac2 instance! Probably has something to do with improvements to MastoAPI compatibility in SNAC.

Using software that doesn't require lots of resources gets more and more comfy 😁

Russian court rules Pepe the frog extremist for displaying symbolics of the "international LGBT movement": https://roskomsvoboda.org/ru/post/shtraf-pepe-lgbt/
❗WARNING❗: Cyrillic alphabet and other horrors ahead, wear a hazmat suit (and use Google translate)