Sebastian Krzyszkowiak @dos@librem.one

My work on mainlining the #Unisoc UMS9230 SoC has reached a point where the usability of most features is limited by proprietary firmware blobs running on other processors (the camera being a notable exception). I am wondering whether it makes sense to write kernel drivers for them at all or if it is better to work on an open-source reimplementation of the firmware.

Thankfully, the #Jolla C2 provides the freedom to replace most of the coprocessor firmware. 1/4

Kind of frustrating that serval gaming outlets are calling the Oct 28 release of Death by Scrolling a "Windows PC" release while totally ignoring (forgetting) it also includes the native Mac and Linux. We worked hard to fully support all three platforms.

To even build your own Android image you need to jump through a bunch of hoops, download hundreds of GB of source code and take >1 hour on even a beefy build machine with ~100GB of binary artifacts. There ARE benefits to having the entire OS source code locally IF you're building an OS the way Google do with many separate teams who work independently.

But this is never how healthy FOSS projects work, they rely on individuals showing up and working in harmony together, something which is just plain annoying to do with AOSP.
3/8

A little more than 2 months after Debian, we’re finally releasing Mobian Trixie as our new stable release! We’re also taking this opportunity to start rotating the PGP/GPG keys we’re using for signing both our images and package archive.

You can read more on our blog: https://blog.mobian.org/posts/2025/10/new-stable-rotating-keys/

phosh 0.50.0 is out 🚀📱:

We have some new features, quality of life improvements, (a bit more than usual) under the hood work and 🐛 fixes, check out the full release notes at
https://phosh.mobi/releases/rel-0.50.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #Librem5 #PinePhone #gtk #wlroots #gnome #linux #mobile #LinuxMobile

i love the alt text culture on fedi, because once in a while i'll browse other platforms and i see an image that i can't quite parse, in which case normally i would just look for alt text to get what i'm looking at, and instead i get the disappointment of no alt text

Significant props to @purism for the repairability on the #Librem5. Disassembly instructions were easy to find on the community wiki. There were relatively few fiddly bits, with nearly all pieces held in by a combination of screws (of a consistent size) and friction clips. Only the screen itself is glued into place, but it's to a metal frame that conducts heat from a hairdryer beautifully. The damaged screen came off with almost no fuss.

This is now the second major part on the phone that I've upgraded/repaired (the first being the power-hungry 1st gen wifi board).

I would say I'm a Wayland developer. I've had some hand in libwayland and the foundational protocols in the past years, and I still have a hand in some protocols today.

That is why, when someone publicly vents that Wayland makes the touchpad feel wrong, or Wayland breaks the picture on the TV, or Wayland uses wrong fonts, it feels like they are blaming me personally.

I understand how it is easy to come to the conclusion that Wayland is to blame. Despite reasoning otherwise, it still hurts.

Last weekend, we reached another milestone in our efforts to have all Debian packages versioned in Salsa (Debian's GitLab instance). Out of around 39000 packages, less than 2000 are not in Salsa! Check https://trends.debian.net/#vcs-hosting for some cool graphs #debian #salsa #09