Sebastian WickInstead of taking any part in the monthly wayland bashing bullshit, you could just read about how electron, one of the last X11 bastions, has adjusted to wayland. Super important work!
Jonas
@verdre
- 463 Followers
- 219 Following
- 161 Posts
Modal CollectiveThere's a schedule for #BoilingTheOcean 10 now 🥳
Join us on March 28 at Cultivation Space to discuss and hack on topics like mobile, local-first, GNOME app development, and more :)
As usual, you can sign up and add your topic and talk ideas on the pad: https://pad.gnome.org/szr80MP4QKuT3tpNHUb1rg
#berlin #localfirst #gnome #postmarketOS #linuxmobile #gtk #flatpak
postmarketOSNew blog post introducing the WIP Duranium project (immutable postmarketOS), some of its major features, and explaining why some design decisions were made. 
> Either the new image works, or the system falls back to the previous one automatically. No partially-applied state. No debugging audio when you need to make a phone call and no fussing with a broken web browser when you just want to doomscroll cat photos. It also means developers can reproduce the exact state of a user's device, making it much easier to track down and fix issues.
https://postmarketos.org/blog/2026/03/17/introducing-duranium/
Alice 
Ok, libadwaita 1.9 released. Read the blog post for details: https://nyaa.place/blog/libadwaita-1-9/
101LABWe are looking for a new member to join our DevOps team with these Skills:
* Linux administration
* LXC containers
* Prometheus + Grafana
Nice-to-haves:
* Orchestration / Ansible
* Nextcloud development / PHP
* Web app development / full-stack
Conditions:
* For now: mini-job 9.5 h / week
* From September: option to upgrade to 20-30 h / week
All creatures welcome! At equal qualifications, FLINTA* are preferred.
Apply at [email protected] (EN/DE)
zramctl shows 20 GB compressed down to 4.7 GB, and this is not testing with flooding memory with zeros, this is my actual Firefox session with tons of different tabs.
Doubling down on my point from yesterday that we don't care enough about proper OOM management.
I just played around with a giant zram device just see if we can make way more use of compressed memory.
Turns out yes, suddenly my Firefox on Linux holds 250 tabs in memory without any disk-backed swap.
Kinda makes the point that having a fixed-size zram device is a bad idea, and the kernel should just compress as much memory as possible?
All of this without one tab getting unloaded by Firefox, or one app getting killed without user consent.
So OOM conditions *can* be handled without losing people's data. Don't let kernel developers fool you into believing this is an impossible problem to solve.
(4/4)
With about 200 MB of disk space left, Firefox froze completely, and at the same time a window popped up telling me that Firefox and a few other apps were frozen (not killed!!!) by the system.
The window prompted to either kill the app or resume it. Pressing resume, Firefox continued running smoothly for a few seconds, until it got frozen again. Pressing resume again, I could quickly close a few tabs, and things worked fine again.
(3/4)
Once my 16 GB of memory were filled up, with a good extra amount saved thanks to compression, macOS just started creating swapfiles. Memory pressure went from the green to the yellow area, things got a little bit sluggish when switching to the oldest tabs, but no major slowdowns or freezes of multiple seconds.
The more tabs were open, the more swap files got created. At some point the disk would fill up though.
(2/4)
