Richard Hughes
I write free software. Firmware troublemaker.
Both #Dell and #Lenovo have agreed to be premier sponsors for the #LVFS as part of our new sustainability effort. Over 145 million firmware updates have been deployed now, from over a hundred different vendors to millions of different Linux devices.
With the industry support from Lenovo and Dell (and #Framework, OSFF, and of course both the Linux Foundation and Red Hat) we can build this ecosystem stronger and higher than before; we can continue the great work we've done long into the future.
There are two types of people: Those that understand why your audio stutters when deploying an efivar-based certificate update (e.g. dbx) and those that don't.
Both are interesting at parties, but never ask the first type to explain what they do as a job.
I'm at #PremDay at Paris and just walked past two people in the hallway I've never met in my life talking excitedly about #LVFS and #fwupd. I know it's an unusual niche open source project but it was a super proud moment for me.
Open source maintenance is 99% fixing bugs and little things like this make it all worthwhile. Thanks those 2 random people!
I've just released https://github.com/hughsie/libxmlb/releases/tag/0.3.29 and https://github.com/fwupd/fwupd/releases/tag/2.1.7 with lots of great fixes and a smattering of new functionality. Enjoy!
If anyone has an ideological problem with @whot@floss.social adding a rustc dep to #fwupd now is the time to squeak.
I've just tagged #fwupd 2.1.2, with lots of fixes, new hardware support and a few cool new features. See https://github.com/fwupd/fwupd/releases/tag/2.1.2 for the list. Enjoy!
Announcing #fwupd 2.1.1 -- a very big release with the usual bugfixes, new features and lots and lots of new hardware support: https://github.com/fwupd/fwupd/releases/tag/2.1.1
In less-awesome news somebody is now impersonating me on GitHub. If you see anything from "Richard Hughes jr" with an AI version of me as a profile photo -- it's obviously not me.
I'm certainly not promoting any kind of cryptocurrency and I'm certainly not a believer in NWO or the Illuminati of all things. I wish I was making all this up... and what a weird timeline we live in.
I've been (ab?)using Claude to find bugs in my software, and although it's found quite a few false positives, it's also found a lot of actual real bugs. Nothing CVE-worthy, but still important to fix. Releases include:
* passim: https://github.com/hughsie/passim/releases/tag/0.1.11
* libxmlb: https://github.com/hughsie/libxmlb/releases/tag/0.3.26
* libjcat: https://github.com/hughsie/libjcat/releases/tag/0.2.6
#fwupd will follow, when all ^^^ has hit the various build-roots. If anyone wants to polish the translations in the meantime, it's the normal place: https://hosted.weblate.org/projects/fwupd/fwupd/
I'm super impressed with the reviews from @coderabbitai@mastodon.social -- they're an order of magnitude better than Claude (and two orders of magnitude better than copilot) even with the latest models. And free for open source projects!
@coderabbitai@mastodon.social how do I refer to you in a commit? e.g. "Co-Authored-By: coderabbitai" perhaps? Claude uses "Co-Authored-By: Claude Sonnet 4.5 " if that helps.
What would you rather see in the output of fwupdmgr security?
I'm pondering some interesting talks I could suggest for #OSFC this year. Does anyone want me to talk about anything specific for firmware, #fwupd or LVFS topics?
I'm thinking doing a pretty aggressive FU aiming at some of the major hardware vendors, but I'm not sure my boss would approve. Other ideas welcome.
Hello again internet friends. What's the 2026 state of the art for syncing two folders on two different machines. e.g. like Dropbox used to be. It doesn't have to sync offline, but bonus points if it syncs to my Proton Drive too.
I want to be able to change and add content to folders on either machine. There's no need to recover previous versions as I already back up in a different way.
I used to use Unison for this a decade ago, but I wanted something that just works with GNOME. Ideas?
How is there no standard MiB constant of 1024*1024 in the C standard? What do other codebases do?