Today we are launching the GNOME Foundation’s 2026 end-of-year fundraiser, and we need your donations to help build a stronger, healthier GNOME ecosystem.
GNOME is an independent computing platform enjoyed by millions of people worldwide. What if a small fraction of them helped financially sustain it? Together, we could give GNOME the resources to accomplish so much more.
GNOME and the GNOME Foundation
GNOME is a Linux desktop environment and collection of apps intentionally designed to be elegant, intuitive, and privacy-respecting. It’s the default experience on many popular Linux distributions like Fedora, Ubuntu, Debian, and Zorin OS.
The GNOME Foundation is the organization working to sustain GNOME, but its resources are stretched thin. We are currently limited to a handful of paid team members, most of whom are part-time.
GNOME exists today thanks to a global community of volunteers sharing their time, talent, and passion to build software that benefits millions. They frequently juggle jobs, family, hobbies, and other commitments to accomplish this work. We see an opportunity to give some of these talented people the time, resources, and financial incentive to contribute more to GNOME.
The Fellowship is Making a Difference
And thanks to your generosity in 2025, we were able to launch the GNOME Fellowship program in April 2026. The Fellowship allows us to directly support two talented members of this community, who in turn spend dedicated time enhancing the long-term sustainability and health of the GNOME project.
These Fellows are already making noticeable quality-of-life enhancements to your everyday desktop experience, and the underlying technologies that power GNOME.
In their first three months, Fellows Peter and Sophie have modernized the file previewer, made substantial improvements to image handling, and fixed many problematic bugs — some of which have existed for years. And that’s only a small sampling of what they’ve accomplished.
With your help, we can raise an additional $60,000 to sustain the fellowship program throughout 2027. Donate today, and let’s continue supporting the vital work our Fellows are doing!
Your Donation Matters
GNOME isn’t just a desktop environment. It’s an alternative to a world where corporations decide how you should use your hardware, treat your personal data as a commodity, and disregard your privacy.
GNOME is a reflection of what we believe technology should be: open, empowering, and built to put the control back in your hands.
If you’re reading this, GNOME matters to you. And your donation matters to GNOME! Please give what you can today. Every single gift helps make a stronger, healthier GNOME possible.
This week's icon is for
Lars Windolf's project:
Liferea:
"Keep up with your feeds"
Check out all weekly app icons created so far in the gallery
and follow my icon creation adventures as they happen (including sketches) on
the Fediverse.
Need icons?
I love designing icons and am happy to contribute them
free of charge
when your project is Free and Open Source.
Join as a community sponsor to maintain
a steady supply of app icons to the Linux ecosystem
(every little helps!).
I’ve been following the world of synthesizers and drum machines for the last decade, since the first Akai MPC with a touchscreen appeared and I thought I’d have more fun making music on that than a laptop. (Which I was wrong about, in hindsight. But it opened the door to a lot of fun exploration in the space where music intersects with technology and human interface design.)
Music technology always involved proprietary platforms and locked-down devices. Macbooks everywhere. Copy protection schemes with hardware dongles (see: iLok). Copyright sting operations against small studios (see: Waves Audio. Read Markus Schmidt of Calf Audio’s story for how wild they go). People regularly call me crazy for making music using a Linux desktop. Even in the world of “creative coding”, where making custom instruments and tools in software is part of the musicians practice, the most popular environment is Max/MSP, a proprietary product that costs 400€ and runs on Windows and Mac only.
That’s before we get to hardware devices. There has been a huge boom in the last decade, it’s been a fun time, and is much better use for semiconductors compared to making drones. There are dedicated DSP chips available. Some devices manage to build an impressive amount of functionality in the DSP chip itself… checkout how many guitar pedals use the Spin FV-1 for example. Others have an ARM chip as the brain, usually running Linux, and usually completely closed to any kind of customisation. These machines are expensive. I still think of 600€ as a cheap price point for a synth. The most expensive MPC costs over 2 grand. You’re paying a premium for custom hardware being produced at relatively small scale, and the expectation that it will be rock solid — built to the quality of any other musical instrument. A guitar doesn’t randomly reboot to install a firmware update and neither do these devices. (The level of programming skill at music tech companies is waaaay above what I’ve seen anywhere else in the tech industry… but that’s a whole other blog post).
Open, hackable devices exist but have always been pretty niche. Have you been to a gig where someone played the Monome Norns? Or maybe an Organelle concert?
The year of our Lord 2026 is the year that changed. This month I’m being bombarded with videos about the MVAVE FM-1, a synth that costs 70€, and comes with an online IDE, and an open SDK. It’s arrived at a moment when LLM coding tools are heavily subsidized by the AI bubble, and at time of writing there are two hundred and nineteen alternative firmwaves available for this thing. There’s a website hosting them all. In fact there are multiple. People are making this box into all sorts of different instruments that suit different purposes, experimenting, learning, playing and abandoning them.
To put that in comparison, I have a Korg Minilogue synth, which has had an open plugin development platform since 2019. Korgs are one of the longest established and best selling synth makers in the world. In 7 years, the official list of plugins grown to about… 200 plugins, many of which are from pro plugin makers. By comparsion, the FM-1 was released in June of this year, that is, not even 7 months have passed yet.
While a lot of the music tech video sphere is hyping the FM-1, there are some more measured takes. Jeremy Blake a.k.a Red Means Recording made a video entitled “Vibecoding in Plato’s Cave (AI, Music Tech, and Star Trek)”, which in turn links to an editorial from audionewsroom.net under “Why the open source hardware revolution is a lie”. These both make some good points, which I won’t repeat as I think everyone who reads my blog already knows that Anthropic and OpenAI are malevolent forces and today’s vibe coding apps are optimized for addiction by the same people who designed slot machines and infinite scroll. I called this back in January 2026 in a post titled “AI predictions for 2026”.
Maybe I’m in an optimistic mood, especially as we might be seeing the first signs of the AI bubble bursting, thanks to Jensen Huang accidentally having sex with a Chinese spy, but I see this sudden boom in hackable music tech as a really cool thing. Musicians who wouldn’t feel comfortable writing “Hello World” in C are suddenly designing and deploying custom device firmwares with wacky interface ideas that they dreamed up themselves. Sure, most of them probably don’t work very well and are quickly abandoned, but people are learning. You learn by doing! I didn’t get into programming because I wanted to study programming — I wanted to do cool stuff with a computer, and learning to code was a byproduct of that. My first attempts at coding were terrible and it was a long, long road to becoming good. I didn’t exactly enjoy it, more than anything it was frustrating because I could never have the time or skill to build the things I wanted. Now I find coding fun, because I did it long enough to get good, but I really see it as a lucky coincidence that I had the time and circumstances to be able to practice and fail on hundreds of projects over many years to get to where I am today.
People who have spent a long time learning to code are worrying about the effect AI coding tools will have on our world. Which is reasonable; leaders in the software industry have mostly lost their minds, almost nobody is hiring and training junior engineers, everyone is getting hacked all the time, and so on. I’m sure you know all of this.
I think the booming FM-1 firmware scene shows that we are missing a bigger point. What effect do AI coding tools have for people who use computers but never felt empowered to hack them before ?
The FM-1 is a perfect playground for learning to hack. There are very few security concerns — it doesn’t even have a network interface, and there’s no private data to steal (unless maybe you’ve saved a really really good song). If you brick the device — and people are doing that — you get to learn how to fix it, and you probably only make that mistake once. In the absolute worst case, you lost 70€ and you have to go back to making music on the bagpipes instead, or whatever you did before.
We need to see this as an entirely new way to interface with a computer.
The oldest computers dealt with binary numbers, one bit at a time. Modern computers do exactly the same thing! They look unrecognizably different, because we have innovated so much in how we interface with them. First we mapped the numbers to a character set, and suddenly we could communicate with them in strings of text. Programming languages emerged only once that was possible. Then we learned to map numbers to pixels on a display. From there, we could build pointing devices and touch screens and eventually get to the modern desktop interface and smartphone.
LLMs map the numbers to tokens in a heavily compressed database of basically all the text that humans ever wrote down, which gives us another new way to communicate with computers. English words map to chunks of code, which get clumsily mangled into something that the computer can and will execute. Yes, that’s a terrible way to make systems software, but that’s not the only thing you can do with this new interface. The sudden fad for making FM-1 firmwares wouldn’t have happened if the device came out 5 years ago. We are looking at the most powerful interface for hacking computers and devices that has ever existed.
I got into the open source desktop world because I wanted to see computer use democratized. Apple and Microsoft promised to lock down and control what we could do with PCs, and Google is doing the same with smartphones now. The open source movement fought against this and we are winning! The Linux desktop is more popular than ever, and operating systems are increasingly a commodity.
But when we win this round, are we clear where to go next? It feels like our only proposition is to do the same thing as before, but also be really angry about AI. I don’t think that is going to work! I’m as angry as you about OpenAI stealing all our work. I’m angry about the climate crisis and the wealth inequality crisis, too, and those both seem a lot more pressing.
It is possible to define your community around rejecting new things but it leads to stagnation. And things don’t go away just because you want them to! As Armin Ronacher put it in his post Communities of Not: “Cars shape cities even for people who cycle”. (I hate cars, too, by the way, and avoided having one for years, but they have stubbornly refused to go away).
Like many of my posts, this is partly wondering out loud about where the GNOME project could go. Fifteen years ago, we did some radical design work, and made a bet that everyone would have GPU in their computer in future. At the time I thought that was a bad call, and actually I couldn’t use GNOME Shell for 5 or so years after the GNOME 3 release because of driver issues. It works great nowadays and it’s obvious now that GNOME Shell included a lot of good decisions that have kept GNOME at the forefront of desktop Linux ever since.
I’m not very excited if our bet for the future is “do the same as before but also argue a lot about AI use.” Now is the time to make some bets about the future of hackable, ethical, open computing that includes the 99% of the population who haven’t spent decades learning to write code with the same level of proficiency and control that Khn de Poitrine has at playing guitar.
GIMP has a lot of intertwined menus, dialogs and tools. When we change
a part of the interface, another may stop working and sometimes, the
problem can be missed until a user reports it.
To find these problems early, a new GUI testing platform was implemented. A typical GUI
test starts GIMP, clicks menus and buttons, and then checks the result.
These tests run automatically each time we merge contributor changes.
GIMP already has unit tests. A unit test checks one small part of the code,
for example how GIMP reads an XCF file. But our unit tests were not
opening a real window. So it coult not tell us if a dialog opens, or if a
menu item did its job.
Note that GIMP already had tests of GUI code, usually interacting directly
with the core code, and sometimes even simulating input devices’ events
(pointer movements, clicks, drags…). But nothing can beat interacting
with the real interface. Furthermore such legacy tests directly hijacking
core code come with their own problems, such as breaking all too often (and
not because they detected a bug), all while not being able to detect whole
categories of bugs.
UI tests check the program as a whole, in the same way as you use it.
Each test starts a real GIMP and does one small task. Then it reads the
result from GIMP. If the result is not correct, the test fails and tells us
what went wrong.
We have 13 tests at this time. They check that:
GIMP starts and shows its main window.
The Welcome dialog opens on the correct tab. It also stays hidden when you
turn off “Show on Start”.
File > New makes an image with the size you set.
File > Export As writes a correct PNG file.
Tools > Swap Colors swaps the foreground and background colors.
You can type a new foreground color in the Colors dialog.
You can add a layer and delete a layer.
Undo and Redo work.
Zoom In changes the zoom level.
A click on a tool button in the toolbox selects that tool. The test then
uses the Bucket Fill tool on the canvas.
A change in Preferences is saved when you click OK.
A menu action, Image > Flatten Image, does its job.
The tests do not need a screen. Each test starts a small, hidden desktop,
runs GIMP in it, and removes it at the end. Because of this, the tests can
run on our CI servers, where
no screen is available.
To find a button or a menu, the tests do not look at the pixels on the
screen. They use the accessibility information that GIMP gives to tools
such as screen readers. This has one more good result: when we make GIMP
easier to test, we also make it easier to use with a screen reader,
hence improve the software accessibility.
The tests use dogtail, a Python tool
for UI tests. To run GIMP on a server with no screen, dogtail needed a new
feature. We contributed this feature upstream, to dogtail itself, so
other projects can use it too.
At this time, the tests run only on Linux (both X11 and Wayland) since
dogtail does not support Windows or macOs.
Adding even these few simple tests considerably increases confidence
that the GIMP build has worked, and also shows the test infrastructure
is working and useful.
13 tests is a good start, but GIMP has many more dialogs and tools. If you
want to help, you can write a test for the part of GIMP that you use the most.
We wrote a guide that shows how to write a new test and how to find the
cause when a test fails:
UI tests on developer.gimp.org.
We hope this work will help us find bugs earlier and keep GIMP working well
for everyone.
Up early, Sade & H. off to see A. in Aldeburgh.
Sucked into E-mail, tried to work out what portrait,
wall-mounted solar panel fixings to order: a super
confusopoly.
Mowed the verge overhanging the resin drive -
to make way for cleaning the drive; filled the brown bin.
Helped J. a bit putting the garden furniture away.
Out to the People's Emergency Briefing -
don't think I've been so patronized in my life - a
loop of a short excerpt from a scientist saying
something scary about the environment, followed by
a lot of ignorant googlebox style watchers repeating
bits of it. Deeply nauseating.
One discovery: that the UK could be self sufficient in
calories if we all became vegan - otherwise nothing you
would not know if you read the business press.
Encouraged to hear from an economist there anyhow.
Still no-one promoting the one intervention that
really works, and avoids lots of political fiddling:
an real carbon tax. Also no-one pointing out that
UK electricity is 20% of the carbon intensity it was
15 years ago (though the price has more than doubled).
Back for a romantic steak dinner with J. to
restore balance in life.
I’ve been working on some more GTK macOS fixes, which were merged this week!
When a window is maximized (“zoomed”), its content now resizes smoothly along with the animation. Before, the content only updated once the animation had finished. (!10667)
When an app starts, it no longer briefly shows an empty window frame before the actual content appears. GTK now waits until the first frame has been drawn before putting the window on screen. (!10640)
Mouse back/forward buttons now work as expected. For example, pressing the back button in an app that uses AdwNavigationView now goes back, just like it does on Linux. (!10625)
GTK can now tell trackpad scrolling apart from a regular mouse wheel. Widgets that rely on touchpad swipes, for example the swipe-back gesture of AdwNavigationView now also works on macOS. (!10617)
Apps can now open links with their own custom URL schemes, for example a link that opens a specific app. Before, these links were silently ignored. (!10615)
Finally, I fixed a bug that caused some tooltips to be clipped. (!10614)
Bazaar 0.10.0 was released this Tuesday with many improvements: you can now install from user remotes in the Flatpak version, remove remotes from within the app, and the daily downloads graph got a redesign.
For the next release, I’ve also added a fancy new distro statistics graph, which should hopefully give app developers more insight into where their users come from.
A callgrind profile contains information about the cost of the functions in an executable.
It can be used to find bottlenecks in your code and speed up your program’s execution.
Klisi prioritises a simple interface, supports full keyboard navigation and touchpad gestures, and aims to cover as much ground as possible with regard to accessibility.
What’s more, it is not a typical GTK4/Adwaita application.
It is written in Clojure using the excellent java-gi bindings.
You can read more about the why and how in a blog post of mine from three months ago, written after the first release.
I hope you find this useful and I am looking forward to your feedback.
Last week, I released a new version of VidCom, a video archival utility. The new version is nothing big, but brings some nice improvements to the user experience.
Changes:
Better window sizing and side-panel collapsing
Various UI changes
Queue is visible and can be interacted with during encoding. This allows the user to add, remove or shuffle videos in the queue while the encoding is in progress. This becomes useful especially when encoding takes a long time to finish.
Bug fixes adressing app stability, threading, encoding and GUI
Fixes for AVC codec options, radio buttons and opening of output folders
Added confirmation dialog for overwriting existing files (both GUI and CLI) and an option to always overwrite files on conflict
I have two updates to share for Moose, a GTK and libadwaita app for chatting with local AI models through Ollama or connecting to cloud services!
Version 0.8.0 brings web search and a calculator to chats with compatible Ollama and Ollama Cloud models. Search uses DuckDuckGo by default, without needing a search account, and asks for permission first. Sources stay with the conversation, so you can come back and check them later. Choosing a model has also become easier: the redesigned Models view lets you browse by task and see estimated memory and storage needs before downloading. Longer Ollama replies can now be continued if they reach their length limit, and OpenRouter joins the supported providers, thanks to olumolu!
Version 0.8.5 adds a way to take your work out of the chat. With Create Document, you can describe what you need or turn an existing answer into a file: a report, a budget spreadsheet or a presentation, for example. Supported formats include PDF, Word, Excel, PowerPoint and OpenDocument. The files stay with the answer and appear alongside your uploads in Moose’s Files view, where you can search their contents, preview them or jump back to the conversation they came from.
You can try Moose on Flathub and find the code on GitHub. Feedback, bug reports and contributions are welcome!
Errands has been rewritten from Python to C. It was a 2-year effort and it’s finally here.
Many new features have been added, and many existing issues have been fixed.
Here is the short list of changes:
Much lower resources usage and memory consumption even with thousands of tasks
Era is a calendar app for mobile and desktop, designed to stay simple for everyday use while offering powerful tools when you need them. It syncs with most online calendar providers and works offline, too.
This release brings updated month and agenda views, with clearer time labels in the agenda and larger date headers in month view, making it easier to spot the start of each month as you scroll. You can now move events to another calendar, and Era remembers your last-used view when you reopen the app. The update also includes further performance improvements in month view.
Era is also available on GNOME Nightly for the latest features, bug fixes, and performance improvements.
That’s all for this week!
See you next week, and be sure to stop by #thisweek:gnome.org with updates on your own projects!
In 2017, I wanted a small tool to change my laptop’s screen brightness.
I found one that worked, but Fedora did not have an RPM package for it.
So I set out to package it myself.
Fedora Copr made that first attempt far less stressful.
I wrote up that first package at the time: How I created my first RPM package in Fedora.
Copr remains one of the most useful tools in the Fedora contribution ecosystem.
This post is the introduction I wish I had read before I started.
It explains what Copr is, why packagers and users rely on it, and why its sandbox-like design matters now.
Copr, short for Community Projects, is a build service.
You give it a source RPM (SRPM), and it builds the package and hosts the results in a DNF or YUM repository.
Copr runs on Fedora infrastructure.
You can use the public instance at copr.fedorainfracloud.org.
If you use Arch Linux, Copr is the closest parallel to the Arch User Repository (AUR).
Both are community spaces where people share packages for others to use.
The AUR shares build scripts, and you build the package on your own machine.
Copr goes a step further.
It builds the RPM for you and hosts the repository, so you enable it and install with DNF.
You need a Fedora Account System (FAS) login to create a project.
You do not need special approval.
You can build for several Fedora releases, EPEL releases, and other targets in one step.
One SRPM can produce packages for many releases and architectures.
When I started, my biggest question was whether my package would build on the releases I cared about.
Koji is Fedora’s official build system, and I used scratch builds there to test.
Copr solved a different problem.
It let me host the package, install it on my own machine, and share a repository with others before I submitted anything for review.
Koji scratch builds caught a Fedora 27 failure that I fixed before I submitted my package for review.
Copr is not a replacement for that process.
It is a place to test first.
Recently, I used Copr to package something new I was working on.
I packaged a set of Markdown files, each one an Agent Skill, from the Fedora Agent Skills Library into a single RPM.
I published it in the AI/ML SIG Copr project and started sharing it for testing and use.
My plan is to package agent-skills officially in Fedora.
Copr made that first step possible because it gave me the fastest path to get an RPM into users' hands.
Users got a semi-official channel to install the package now, and I got real feedback while the official process moves along.
Copr works well as a sandbox.
Several design choices make that true.
Projects are separate.
Packages in your Copr project do not enter Fedora’s official repositories.
Your experiments stay in your own repository.
Packaging rules are relaxed.
Copr packages do not have to follow the Fedora Packaging Guidelines.
The guidelines are still recommended, but you can test ideas before you meet every rule.
Projects can expire.
You can set a project to delete itself after a number of days.
This suits short tests and one-off experiments.
Old builds are removed.
By default, Copr keeps one build per package and deletes the others after 14 days.
Projects on the newer Pulp backend keep the five most recent successful builds per package instead, so test projects do not grow forever.
A sandbox does not mean anything goes.
Copr is Free Software, and its repositories are signed.
However, the Copr maintainers do not review every package.
Before you install a package from a Copr project, check who maintains it.
If you can, look at the SRPM and spec file.
Projects distributed in Copr must also follow Fedora’s license rules.
Fedora is discussing a Council proposal for an Innovation Lifecycle.
The proposal includes a "sandbox stage" for experimental work that is too large for a single change proposal.
One of its stated goals is to isolate risk.
Experiments should be able to break without affecting the main distribution or the people who depend on it.
The proposal also notes that it does not yet define standard sandbox infrastructure.
Copr is not part of that proposal.
It already shows what a low-risk space for experiments can look like.
Work stays separate from official releases, feedback comes quickly, and strong packages can follow a path into Fedora.
I hope we keep that spirit as the larger discussion moves forward.
Distribution methods will change over time.
Right now, RPM packaging works well.
It is tested, proven, and well understood by Fedora contributors and users.
When we do not know how to share something new, RPM packaging is a path we can always fall back on.
It provides versioning and a distribution mechanism for large varieties of software.
Copr makes that RPM packaging fallback fast.
Copr gave me a low-risk way to learn packaging, and it can do the same for you.
If you have a package that is too early for Fedora, build it in Copr, share it, and learn from the results.
Thank you to everyone who maintains Copr and helps packagers use it.
Featured image generated by LLM-gen-AI using the OpenAI image API.
Spooky season is over, let’s see what scary changes I made last month
Nautilus
I finally installed GNOME OS this month. It runs very smoothly on my machine and is a pleasant experience so far. But when I opened nautilus on this fresh setup, I realized that it sorts files and folders interleaved, something I assumed would no longer be the case as the default was changed 5(!) years ago. Obviously I had to find out what is going wrong and the culprit turned out to be nautilus trying to migrate legacy GTK3 settings on fresh setups. This no doubt made sense when António Fernandes gloriously ported to GTK4, but since that was almost 5 years ago, I now dropped considering GTK3 settings, meaning fresh setups will finally see folders sorted before files by default
Related to folder sorting, I was very excited to see Christian Hergert added sections to GtkGridView in GTK. I long thought that sections would be very useful to have, as it allows to show folders and files separate. I played around with them a bit, but still need to rework it before other maintainers are happy with it.
When testing the preferences dialog in another language which commonly uses longer words than English (yes, it was German) I noticed that the recently adopted AdwComboRow for the “Action to Open Items” doesn’t scale well to smaller sizes. After some feedback from Philipp Sauberzweig it now uses the new AdwActionRow:body property. Philipp also suggested more adjustments for the performance section combo rows, making the dialog now look this
I also had a call with GNOME designer Tobias Bernard for a live test session of the new app chooser and we adjusted the mockup to the constraints we are working with (and then some). I am optimistic that it will be finalized by next month
During writing last month’s blog post I noticed and fixed some graphical inconsistencies in the icon. I also made sure we only offer to copy error messages when we actually have any. Apart from that and a bug fix release, I mostly reviewed MRs from Tau Gärtli and Corey Berla.
There is one more thing that Tau and I hacked on together in person, but it’s not ready yet, so all I have is this teaser text and a rainbow selfie
libadwaita
I have once again stumbled upon issues with dialog sizing. Basically, what I expect dialogs to scale with their content. No problem, AdwDialog:follows-content-size has you covered. But what I also expect them to do, is to have a certain width when space allows for it. GTK calls this the “natural” size, the size a dialog/widget has, when it is not contstraint.
The issue now is that the dialog’s content is commonly made up of many nested widgets. It even commonly includes a clamping widget that assures nested widgets don’t grow too wide. The natural size of this composition of various widgets is not easy to define or predict. So, when using follows-content-size the dialog might often end up small, even in situations where that doesn’t really look all that great.
What I implented as a suggested workaround is to always strive for allocating at least the dialog’s content-width and content-height, even when follows-content-size is set. If the dialog’s content grows beyond those dimensions, then it is still resized accordingly.
Other
I fixed up a GTK MR from the previous month that adds gdk_keyval_is_alias, a check that builds on the mechanism of the recently introduced gdk_keyval_get_aliases which allows to check for keyval alternatives (merged), e.g. to cover alternative numpad keys
Fixed a GVariant leak that caused one of the many CI pipeline failures this month
The GNOME Fellowships are funded by our community. If you would like to help the GNOME project to stay sustainable, please consider donating.
AI Summary
On their way onward, the group decides that having their folders and proviant all mixed up together is not a particulary useful way of organizing their possessions. Someone suggests to have completely separate, but for now they agree on at least not mixing them. The group meets Adwy, the one and only giant tortoise in these lands. It is very content to meet them. Maybe that is because Autoar realized it is the 2020s and not the 1920s and stopped wearing a Fedora.
Important note: All statements in this blog are fictional.
Six statewide races featured a Republican against a Democrat. 10% of SF’s mail ballots (details
below) voted for the Republican in 5 or 6 of those races. It’s safe to call those voters actual, honest-to-god Republicans. The tables below show what those SF Republicans voted for in the other races.
To be utterly clear: this analysis does not mean, and does not claim, that voting for Connie Chan or voter ID makes you a
Republican (though Republicans did vote for Connie Chan, 57% to 43%, and overwhelmingly for voter
ID, 89% to 11%). All I’m saying in this post is that San Francisco Republicans voted for Connie Chan, voter ID, and a bunch of other things that the rest of the San Francisco electorate disagreed with them on, as well as some areas where the GOP and non-GOP voters agreed.
SF GOP voters = the 27,144 mail voters who meet the 5-of-6 test. Everyone else = the other
239,687 complete mail ballots. Both columns come from the same set of ballots, so each gap compares
two groups of voters directly. Each cell gives the majority side and its share of the voters who
voted on that item; blanks are excluded. Gap = the difference, in percentage points, between
the share of GOP voters and the share of everyone else who supported the item (for the two
candidate races: who chose Chan, or Kim). The disagreement table is sorted by the gap, largest first; the agreement table is sorted
smallest first. The Congress row counts only ballots from CA-11 voters.
#Where GOP voters and everyone else disagreed (22 items)
Three of the five agreements are parts of the mayor’s charter package (SF A, E and F); the other two (state Props 44 and
38) are measures that both GOP and non-GOP voters opposed.
San Francisco publishes a cast vote record: an anonymous file with one record per scanned ballot
card, showing every choice on that card. This analysis uses the release of November 8, 2026,
which holds 1,370,121 cards. The results are preliminary; the Department of Elections expects to
certify them on December 3.
San Francisco’s ballot had four cards, and the file does not say which cards came from the same
voter. For mail ballots, the four cards from one envelope are scanned one after another, so I
regrouped them by scan order, precinct and ballot style. That gave 266,831 complete mail ballots,
88% of the mail ballots in the file. The complete ballots match all mail cards to within 0.1
percentage points on every measure, so the ballots I could not regroup should not skew the sample.
I counted a voter as a “GOP voter” if they chose the Republican in at least 5 of the 6 statewide
races that had a Democrat and a Republican on the ballot (Governor, Lieutenant Governor,
Secretary of State, Controller, Treasurer, Attorney General). This is a definition by votes, not
by party registration. Most voters are at one end or the other: of the complete mail ballots,
80.1% chose no Republican, 8.3% chose all six, and 5.1% chose two to four. The rest chose exactly
one or exactly five. The 5-of-6 test gives 27,144 GOP voters, 10.2% of complete mail ballots.
All analysis code was written by Claude Code (mix of Opus and Fable), with an adversarial audit by GLM-5.3.
Limitations:
Mail ballots only. I cannot regroup Election Day ballots (about 11% of all ballots in the
file), because their scan order is scrambled. Election Day voters are somewhat more
Republican: 12.2% of Election Day cards with the statewide races meet the 5-of-6 test, against
10.2% of mail cards. So the GOP voters here are mail voters, and they may differ somewhat from Election
Day Republicans.
The House race had no Republican. 21% of GOP voters in the CA-11 district left the
Chan–Wiener race blank. The Congress row covers only the GOP voters who chose one of the two.
Regrouping can make mistakes. The method can occasionally merge the cards of two neighbors
from the same precinct into one ballot. A wrong merge mixes two voters, which makes the GOP
voters and everyone else look more alike. So any such errors shrink the gaps in the tables;
they cannot create them.
Small numbers redacted. The Department withheld the votes on 24 cards (6 ballots) in very
small batches. I left them out.
I’ve published another update on my work in GNOME Design and Community Management as part of my Sovereign Tech Fellowship. I’m especially excited about the progress on passkey support in GNOME and the libadwaita changes from the scale row standardization work. Check out the full blog post!
My first contributions to GTK were merged this week!
The first change fixes a rare edge case where GTK would wrongly detect a swipe gesture and start scrolling, even though the user hadn’t actually swiped.
The second merge request was originally meant to fix a bug where GTK’s text handles would ignore input in some cases (these are used to select text on touchscreens). While the bug was instead fixed in another patch, luckily I still found a small change I could make to improve code quality :)
Also, my first patch for Mutter was merged: It fixes an issue where the OSK (on-screen keyboard) would only appear after two taps on input fields in GTK apps. Now, you should only need to tap once for the OSK to appear!
This has actually been in the works for a long time, the awesome Carlos Garnacho worked on Wayland protocol support and more to make it happen. It seems there was just this small Mutter bugfix missing to get it working.
These changes are motivated by the goal of eventually being able to use a Linux phone with GNOME :)
Blueprint, the objectively best markup language for GNOME user interfaces, got even better this week.
Semicolons after {} and [] blocks are now optional! 🎆
This allows to change indentions of nested code without having to worry about placing semicolons in all the exactly right places.
If you are using Blueprint as a subproject, you can already use this by updating to the latest commit.
With its latest update, the Japanese-English dictionary app Kotoba now brings a kanji composer, making it easy to look up words even when you don’t know how they’re pronounced.
🎉 New Release Announcement: GstPipelineStudio v0.7.3 🎉
GstPipelineStudio version 0.7.3 is out! You can now drag elements and pipelines straight onto the graph, open a terminal next to your pipeline, and use GPS fully translated in six languages.
What’s new in 0.7.3:
Drag elements, favorites and pipelines from the lists onto the graph
Terminal tab in the bottom panel, toggled from View → Terminal (Linux and macOS)
GPS tells you in the window title when a newer release is available, in the AppImage and the Windows and macOS builds
Main window built on libadwaita
Finnish translation; Italian, French, Portuguese, German and Spanish translations completed
Space and s no longer steal keys from a focused text field
Highlights of the 0.7.x series:
New application icon
Nodes colored by type: source, transform, sink
Swap a node for an alternative element from its context menu
Tags tab listing tags from bus messages
Sortable columns in the element and pipeline lists
Suggestions reuse a compatible free element already in the graph
Space bar toggles play/pause, s stops the pipeline
Explicit properties are kept when importing a pipeline
Participants:
Stéphane Cerveau — maintainer and main contributor
Learn 6502 0.9.0 now runs on Linux, macOS, Windows and Android. Android is still experimental, but the basics already work. The image shows the app on GNOME Mobile 🐧 and Android 🤖.
It’s one TypeScript and Blueprint codebase. On Linux it’s a regular GJS app. On macOS and Windows it runs on Node.js with @gjsify/node-gi, which provides gi:// imports that behave like GJS, plus a bundled GTK. On Android it runs in NativeScript, where @gjsify/adwaita-nativescript turns the same Blueprint files into native Android views styled like libadwaita.
All of this comes from gjsify, an experimental framework that brings Node.js and Web APIs to GJS, and GJS to other runtimes. It can now also load native Node.js addons in GJS through its own Node-API implementation. The gjsify toolchain itself runs on GJS, so Node.js is an option, not a dependency.
How it works, and how AI fits into a project I started long before AI tools existed, is on my blog.
Get it on Flathub or download the app for Linux, Windows, macOS and Android from the app page.
word-sys PDF Editor v1.12.0 (“Sign & Protect”) has been released! Built with GTK4 and Libadwaita, this major update introduces an interactive AcroForms engine and form builder, PAdES digital signatures with PKCS#11 hardware token (smart card/USB HSM) support, permanent cryptographic redaction with automated PII detection, and a multi-threaded offline Tesseract OCR engine. It also adds continuous page scrolling, 4K/HiDPI fractional scaling improvements, measurement tools, AES-256 encryption, and a PDF target-size compression solver.
You can install word-sys PDF Editor from Flathub or check out the release on GitHub.
Accent Hold brings macOS-style press and hold to GNOME.
I switched from a Mac and missed typing accents by simply holding a key, so I built it. Hold a letter (e, a, c, o, n…) and its accented variants (é è ê ë, ç, ñ, ô…) pop up next to the text cursor. Pick one with its number, the arrow keys or the mouse. A quick tap still types the plain letter, and the held key doesn’t repeat.
Version 2.1 does everything inside the extension: no daemon, no root, nothing to configure. It works with any layout (AZERTY, QWERTZ…) on GNOME 45 to 50. For apps that don’t use the GNOME input method, a shortcut (Super+E) opens the same picker.
Many thanks to Manuele Conti for the discussions that shaped the press-and-hold design.
The oo7-daemon crate is now officially stable: a Rust implementation of the Secret Service that’s mature enough to ship in GNOME OS and Fedora 45 (and likely other distros soon).
GNOME will be present in Toulouse, France, on the 14th and 15th of November for the ‘Capitole du Libre’ event. It’s an event for the free software community living in France with many volunteers and students, conferences, and booths from the biggest free software projects (Debian, April, Mageia, Mozilla, OpenStreetMap…).
In case you’re interested in coming for one or two days, please contact me via #engagement:gnome.org so that we can get in touch!
To anyone interested, I will have GNOME t-shirts to sell to support the Foundation, supporting Foundation employees, contractors, and the Foundation’s missions!
Blog post collecting in one place some thoughts from social media (original post).
Armin Ronacher ran the same poll on Twitter, Bluesky, and Mastodon: “Do you still write more than 20% of code by hand?” The answers: 8.4% yes on Twitter, 26.3% on Bluesky, 65.1% on Mastodon. Obviously some caveats here, but still: same question, three very different worlds.
My reaction, roughly: sob. A lot of very, very good FOSS people — people whose hearts and pre-LLM skills are in exactly the right places — are on Mastodon, and on the 65% side of that poll.
In quoting Armin, I said I want to bring those folks “along for this ride”. Sumana asked the right question in reply: what ride, specifically? This post is an answer: what has me excited about user freedom, post-LLMs? where do I think we’re going? where do I want the hardest-core of hard-core FOSS zealots (complimentary) to come along?
Most important: I think we can get to a world where most users are actually empowered to take advantage of Freedom 1 — the freedom to study how a program works and change it to do what you want.
For forty years that freedom has been real in law but mostly theoretical in practice. You had it if you could also build the thing, navigate the codebase, and maintain a patch. Even with a CS degree, for anything but the most trivial changes, I basically never had that. Now my daily-driver desktop is a heavily customized GNOME, I read social through an aggressively forked phanpy, and probably others I’m forgetting. That’s the promise we always wanted and I’m living it right now.
#2. Higher quality, because best practices can become actual practices
A lot of FOSS best practices were always good in theory, but proved too expensive for volunteers (or really anyone) to implement comprehensively. Among those: test-driven development, accessibility testing, and especially formal methods. These kinds of things have stopped being impractical and have started becoming real.
The nature of collaboration is going to change. Lots of that may be for the worse in a variety of ways (about which some other day). But on the plus side, on a front I care a lot about: we now have a loooot of ways of bringing in the opinions (and skills and efforts!) of people who don’t code. Designers, writers, domain experts, the people who file the bug reports.
One thing I worry a lot about here: there was a golden era where open source got better, quickly, because we were much better about listening to our users though public issue trackers. That window closed. Now I fear it will go the other way: proprietary vendors are frantically building tools to help them synthesize user feedback and turn that into shipping code at lightning fast speed. If we don’t get there first, with open processes, we lose one of the few structural advantages open collaboration has left.
Half-joking, but: FOSS benefits a lot from having a clear antagonist, like Bill Gates in the old days. We have Bad Guys again, and they’re worse than the old ones: more concentrated, more capital-intensive, and more willing to take what’s open without giving back. That’s a reason to engage, not to opt out.
And yes, that means I’m advising using the tools the bad guys are giving us. We’ve done that before to advance our goals (emacs and gcc were written on proprietary kernels; Firefox on Windows was how we beat IE) and we are going to have to do it again. That’s not great — but that should motivate us to fight and win, not to quit.
Rewriting our decades of legacy, unsafe-by-design C and C++ in modern, safer languages is now a tractable task. That once seemed so impossible that Vernor Vinge, a computer science professor, made Unix-era buffer overflows still lurking in the year 8000 a plot point in A Deepness in the Sky. Vinge’s joke was that nobody would ever pay down that debt, even given 1,000 years. Now we can, making all our users more secure — and, if we’re serious about it, giving us a new generation of programmers who can work in our codebases.
None of these rides is guaranteed to happen, let alone to turn out well. They’re all possibilities — and that’s exactly why I want a big tent of people coming along to steer them, and to keep us honest.
Some details of the credentials portal mockup showing the passkey creation
Libadwaita
Inmylastblogpost,IwroteaboutstandardizingscalerowsinlibadwaitaandmentionedthatActionRowwouldlikelygetagenericbottomchildwidgettosupportthechange.ThishasnowlandedastheActionRow:bodyproperty,and the calendar app Eraalreadyusesittoimplementitsparticipantsrow.
Screenshot of the calendar app Era with a participants row based using the new ActionRow:body property
The new scale style has also already landed in the upcoming libadwaita version.
Screenshot of the new scale style with pill shaped knob
As usual, I’ve reviewed design changes across various projects and answered questions on Matrix and in issue threads. GNOME Circle reviews are also progressing well, and I’ll write more about them as the changes land.