<?xml version='1.0' encoding='UTF-8'?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Planet GNOME</title>
    <link>https://planet.gnome.org/atom.xml</link>
    <description>Planet GNOME - https://planet.gnome.org/</description>
    <atom:link href="https://planet.gnome.org/atom.xml" rel="self"/>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 12:17:54 +0000</lastBuildDate>
    <item>
      <title>GIMP: Interview with Liam Quin</title>
      <link>https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/</link>
      <description>&lt;p&gt;&lt;span class="caps"&gt;GIMP&lt;/span&gt; is &lt;a href="https://www.gnu.org/philosophy/free-sw.html"&gt;Free and Libre Open Source Software&lt;/a&gt;, but none of it is possible without
the people who create with and contribute to it. Our project maintainer &lt;strong&gt;Jehan&lt;/strong&gt; wanted to interview the volunteers
who make &lt;span class="caps"&gt;GIMP&lt;/span&gt; what it is, and share their stories so you can learn more about the awesome people behind &lt;span class="caps"&gt;GIMP&lt;/span&gt;!&lt;/p&gt;
&lt;p&gt;After the first &lt;a href="https://www.gimp.org/news/2017/01/18/wilberweek-2017-announced/"&gt;Wilber Week&lt;/a&gt; in 2017, 
we published interviews with
&lt;a href="https://www.gimp.org/news/2017/03/01/an-interview-with-michael-natterer-gimp-maintainer/"&gt;Michael Natterer&lt;/a&gt;
and &lt;a href="https://www.gimp.org/news/2017/05/15/an-interview-with-michael-schumacher-gimp-administrator/"&gt;Michael Schumacher&lt;/a&gt;.
Many years later, the remaining interviews with &lt;a href="https://www.gimp.org/news/2025/11/01/simon-budig-interview-ww2017/"&gt;Simon Budig&lt;/a&gt; 
and &lt;a href="https://www.gimp.org/news/2026/02/22/oyvind-kolas-interview-ww2017/"&gt;Øyvind Kolås&lt;/a&gt; were unearthed and shared.&lt;/p&gt;
&lt;p&gt;The second set of interviews were conducted in Rio de Janeiro, Brazil during the
&lt;a href="https://libregraphicsmeeting.org/2017/"&gt;2017 Libre Graphics Meeting&lt;/a&gt;. The first one shared was with Brazilian artist
and free software advocate &lt;a href="https://www.gimp.org/news/2026/07/10/nara-oliveira-interview-lgm2017/"&gt;Nara Oliveira&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The next subject of the &lt;span class="caps"&gt;LGM&lt;/span&gt; interviews was &lt;strong&gt;Liam Quin&lt;/strong&gt;. Liam is a multi-talented individual whose impact is difficult
to sum up in a single sentence - but which includes their involvement with creating &lt;span class="caps"&gt;XML&lt;/span&gt;, their award-winning typography
work, and their efforts to improve accessibility and the text tool in &lt;span class="caps"&gt;GIMP&lt;/span&gt;!&lt;/p&gt;
&lt;p&gt;This interview took place during April 21 - 23, 2017. In addition to &lt;strong&gt;Jehan&lt;/strong&gt; and &lt;strong&gt;Liam&lt;/strong&gt;, &lt;strong&gt;Simon Budig&lt;/strong&gt;,
&lt;strong&gt;Aryeom Han&lt;/strong&gt;, and &lt;strong&gt;Americo Gobbo&lt;/strong&gt; were also involved and asked questions.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Liam Quin, CC-BY-SA" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/Liam_Quin.jpg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;Liam Quin, by Simon Budig (taken during photo-walk organized by Pat David in &lt;span class="caps"&gt;LGM&lt;/span&gt; 2016, London), &lt;span class="caps"&gt;CC&lt;/span&gt;-&lt;span class="caps"&gt;BY&lt;/span&gt;-&lt;span class="caps"&gt;SA&lt;/span&gt;&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;hr/&gt;
&lt;p&gt;&lt;em&gt;Jehan: Hello Liam!&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Good evening.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: First of all, could you introduce yourself?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: My name is Liam Quin. What do you want to know about me? I’ve been using &lt;span class="caps"&gt;GIMP&lt;/span&gt; for over 300 years,
since 1997 or 1998. I’m not sure – ‘98 I think.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan [laughing]: Not very good with mathematics.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Not very good with mathematics, numbers, no - I’ve heard of them. Computer science, got that – don’t need
to be very good at maths to get a degree in computer science. Although I should have specialized in maths – and digital
typography is my background, and I think my first love.&lt;/p&gt;
&lt;p&gt;I &lt;a href="https://www.w3.org/People/Quin/"&gt;work today&lt;/a&gt; for the World Wide Web Consortium, &lt;a href="https://www.w3.org/"&gt;the &lt;span class="caps"&gt;W3C&lt;/span&gt;&lt;/a&gt;,
where I’ve been in charge of our &lt;a href="https://www.xml.com/authors/liam-r-e-quin/"&gt;&lt;span class="caps"&gt;XML&lt;/span&gt; work&lt;/a&gt;.
Now I do &lt;span class="caps"&gt;CSS&lt;/span&gt; and accessibility and some payment stuff and some &lt;span class="caps"&gt;SVG&lt;/span&gt; stuff, all sorts of things.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;[&lt;strong&gt;Editor’s note&lt;/strong&gt;: Since this interview, Liam has left &lt;span class="caps"&gt;W3C&lt;/span&gt; and founded &lt;a href="https://delightfulcomputing.com"&gt;Delightful Computing&lt;/a&gt;]&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Okay, so what has been your involvement with &lt;span class="caps"&gt;GIMP&lt;/span&gt;?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I’m just a hanger-on, a time-waster. I throw bricks from the side, I make suggestions.
For a while I was the
&lt;a href="https://web.archive.org/web/20020203030758/http://foundation.gnome.org/membership-list.html#:~:text=liam,guidance"&gt;official spiritual advisor&lt;/a&gt; to the &lt;span class="caps"&gt;GNOME&lt;/span&gt; project, but I believe I had to give that
up when Bush was elected. I was, actually, if you look at the foundation page you’ll see me there.
I just met the people at a &lt;span class="caps"&gt;GNOME&lt;/span&gt; &lt;span class="caps"&gt;GUADEC&lt;/span&gt; conference years ago, and decided they were really good people.&lt;/p&gt;
&lt;p&gt;I’ve been using &lt;span class="caps"&gt;GIMP&lt;/span&gt; professionally. I run a small &lt;a href="https://www.fromoldbooks.org/"&gt;stock image company&lt;/a&gt;
and the images, both photographs and scanned images from old books, I clean them up with &lt;span class="caps"&gt;GIMP&lt;/span&gt; and do
creative work with them and sell them. The &lt;span class="caps"&gt;GIMP&lt;/span&gt; team has been responsive when I needed changes or when
I wanted changes, and very occasionally I’ve even made some patches, although not very many.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Maybe you can tell us what you like about &lt;span class="caps"&gt;GIMP&lt;/span&gt;, what you don’t like about &lt;span class="caps"&gt;GIMP&lt;/span&gt;?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: What I like least about &lt;span class="caps"&gt;GIMP&lt;/span&gt; is the name, because I work in accessibility. So for example,
I can’t wear the &lt;span class="caps"&gt;GIMP&lt;/span&gt; shirt at work because there will be people who are upset.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;[&lt;strong&gt;Editor’s note&lt;/strong&gt;: &lt;a href="https://www.gimp.org/docs/userfaq.html#i-dont-like-the-name-gimp-will-you-change-it"&gt;More information about the name and where things currently stand&lt;/a&gt;]&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;But what I like most about it is that is Free Software. That I have a right to change the code, or to pay
someone else to change the code if I can’t. That it runs on free platforms, such as &lt;span class="caps"&gt;GNU&lt;/span&gt;/Linux systems.
I like that it’s in a language I can read. I particularly like that it’s got a lot of functions,
it does a lot. It does pretty much everything I need. I can imagine it doing more, I can imagine a
program that I would just say, “Scan this image and clean it up for me”, but we’re not there yet.
I actually have to do work, including creative work, to repair image. &lt;span class="caps"&gt;GIMP&lt;/span&gt; is actually the best program
I have used for that, and I’ve used both commercial and other free software – free in both senses.
I’ve found that &lt;span class="caps"&gt;GIMP&lt;/span&gt; has features that are really good for cleaning up scanned images.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="The Haunted Chest of Drawers from La Vie Parisienne, scanned and restored by Liam Quin, CC-BY-SA" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/the-sneezing-chest-of-drawers.jpg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;&lt;a href="https://www.fromoldbooks.org/Marcelin-LaVieParisienne-1863/pages/572-the-sneezing-chest-of-drawers/"&gt;
The Haunted Chest of Drawers&lt;/a&gt; from La Vie Parisienne (1863), scanned and restored by Liam Quin, &lt;span class="caps"&gt;CC&lt;/span&gt;-&lt;span class="caps"&gt;BY&lt;/span&gt;-&lt;span class="caps"&gt;SA&lt;/span&gt;&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;em&gt;Americo: What do you think about artists using &lt;span class="caps"&gt;GIMP&lt;/span&gt;?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I think artists, people approach art from all sorts of different angles and direction.
And some people want something very immediate, which you might find in
&lt;a href="https://www.mypaint.app/en/"&gt;MyPaint&lt;/a&gt; for example, where you open MyPaint and you don’t even have
to do &lt;code&gt;File&lt;/code&gt; → &lt;code&gt;New&lt;/code&gt;, it’s just there, and you can start drawing.&lt;/p&gt;
&lt;p&gt;And at the other extreme, there are people who plan a drawing for a long time, maybe draw careful
pencil sketches and build something up over a period of hours, days, months, even years. And within
those, there’s people who are very precise, work with numerical angles, will write a little programming
script to create a particular effect – and there’s other people who will want to do lots of experiments
and choose the one that works best.&lt;/p&gt;
&lt;p&gt;I think what we’ve been seeing is that the user interface of &lt;span class="caps"&gt;GIMP&lt;/span&gt; has been changing. There’s been a move
towards supporting the spontaneity a lot more. The early &lt;span class="caps"&gt;GIMP&lt;/span&gt; was really aimed at the people who thought
about their art more than – as I see it – more than just sitting down and painting. That’s actually why I
think my husband would prefer MyPaint to &lt;span class="caps"&gt;GIMP&lt;/span&gt;. He said he hated &lt;span class="caps"&gt;GIMP&lt;/span&gt;, and part of that was because he was
taught Photoshop at university. Universities shouldn’t be teaching specific programs, they should be
teaching the underlying skills, they should teach image editing, not a particular version of a particular
program. But you spend so long learning one program that you get really tied to it.&lt;/p&gt;
&lt;p&gt;But we also have the fact that &lt;span class="caps"&gt;GIMP&lt;/span&gt; has been more – um, people have this left-brain, right-brain
categorization which turns out to not have much basis in reality, our brains don’t actually work
that way – but &lt;span class="caps"&gt;GIMP&lt;/span&gt; is more “left-brain” than “right-brain”. Not as extreme as Inkscape or
Illustrator for example, where you can’t even do a brush stroke, you do an outline really,
unless you fight the tool.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;[&lt;strong&gt;Editor’s note&lt;/strong&gt;: While not quite the same as a raster tool, Inkscape has brush-like features such as the &lt;a href="https://inkscape-manuals.readthedocs.io/en/latest/calligraphy-tool.html"&gt;Calligraphy Tool&lt;/a&gt;, no fighting required!]&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;So there’s people doing fabulous, professional artwork - really good quality artwork with &lt;span class="caps"&gt;GIMP&lt;/span&gt;.
It doesn’t suit everyone, but if it does suit you, it’s absolutely awesome. It’s got lots of features.
I don’t know of any other art program where you can control the brush size with a &lt;span class="caps"&gt;MIDI&lt;/span&gt; keyboard, right.
That might sound really weird, and yet, I can imagine holding a &lt;span class="caps"&gt;MIDI&lt;/span&gt; device in one hand, or using one
foot to control a &lt;span class="caps"&gt;MIDI&lt;/span&gt; device, because it exists, a pedal for example, and wiring that to brush size
and that could be really interesting.&lt;/p&gt;
&lt;p&gt;So yeah, &lt;span class="caps"&gt;GIMP&lt;/span&gt; is fine for doing professional art, but as an artist you’ve got to figure out which
tools you’re going to use. When you walk into a gallery and you see paintings by the old masters,
you look at them and they stand out. They’re called masters because they’ve mastered the technique,
and they think about what they want to do, and the technique becomes – as far as the observer is
concerned, watching them work – they’re not thinking about how to achieve the effect they want,
it just happens. In actual fact, some of them probably spent a long time thinking about the effect they want,
but it doesn’t seem that way.&lt;/p&gt;
&lt;p&gt;Some people say it takes about 10,000 hours of work to become a master in something if you practice it.
I think you can become a master in digital painting, in multiple tools, and &lt;span class="caps"&gt;GIMP&lt;/span&gt; is one of them. It’s
a strong one, but it doesn’t have to be the end of it.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Does your work in &lt;span class="caps"&gt;W3C&lt;/span&gt; have maybe any relationship or link with &lt;span class="caps"&gt;GIMP&lt;/span&gt;?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: We have stronger links to &lt;a href="https://inkscape.org/"&gt;Inkscape&lt;/a&gt; actually. The strongest link to
&lt;span class="caps"&gt;GIMP&lt;/span&gt; a long time ago was the &lt;span class="caps"&gt;PNG&lt;/span&gt; support, because the &lt;span class="caps"&gt;PNG&lt;/span&gt; image format was jointly developed with &lt;span class="caps"&gt;W3C&lt;/span&gt;
and &lt;span class="caps"&gt;IETF&lt;/span&gt;. The Inkscape work, &lt;span class="caps"&gt;SVG&lt;/span&gt;, is on-going, and even though it hasn’t been implemented the same way
in all programs, it’s already pretty useful. But there have been other overlaps such as color management
and compositing, for example.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Liam Quin (right) in costume at W3C conference, CC-BY-SA" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/liam-at-event.jpg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;Liam Quin (right) in costume at &lt;span class="caps"&gt;W3C&lt;/span&gt; conference, &lt;span class="caps"&gt;CC&lt;/span&gt;-&lt;span class="caps"&gt;BY&lt;/span&gt;-&lt;span class="caps"&gt;SA&lt;/span&gt;&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;At one point I reached out to someone from Adobe who was working on &lt;span class="caps"&gt;CSS&lt;/span&gt; compositing, and who knew about
the internals of Photoshop, and he came and joined the &lt;span class="caps"&gt;GIMP&lt;/span&gt; &lt;span class="caps"&gt;IRC&lt;/span&gt; channel and talked with people there about
color models and compositing. So in some ways I’ve tried to encourage communication. And I think the culture
of the web, the web has really done a lot for free and open source software. More people are using free
software now than ever before, because of free web browser and free web tools. So the work that we’re doing
at &lt;span class="caps"&gt;W3C&lt;/span&gt; certainly relates to the &lt;span class="caps"&gt;GNU&lt;/span&gt; project, the &lt;span class="caps"&gt;GNOME&lt;/span&gt; project, the &lt;span class="caps"&gt;GIMP&lt;/span&gt; project – both technically, legally,
socially. So there’s links in that kind of way. But I don’t think we have a whole lot of direct contact.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: What do you see in the future of &lt;span class="caps"&gt;GIMP&lt;/span&gt;?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I suspect that the long term future of &lt;span class="caps"&gt;GIMP&lt;/span&gt; is that these native toolkits are going to get replaced
with webpages and Javascript.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: So you mean &lt;span class="caps"&gt;GTK&lt;/span&gt;+?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I expect eventually there will be a Javascript to replace &lt;span class="caps"&gt;GTK&lt;/span&gt;. In ten years time, I think &lt;span class="caps"&gt;GIMP&lt;/span&gt;
will be running in a web browser as a web app in some way.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan [laughing]: Seriously, or is that a joke?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: No, I was completely serious. And the reason I think that is, what the web has done is it’s
assimilated – like the famous Borg – it’s taken over all sorts of things. Native clients for particular
applications have gone away whenever it was feasible to replace them with a web app. 25 years ago –
can that be right? In 1995, how long ago was that? 22 years ago… I was in a conference in Ottawa, for
document management systems. And these all had proprietary desktop clients that were basically GitHub.
That you loaded a proprietary client, and it had a button to check out a file, another one to check it
back in, open it in editor, show differences.&lt;/p&gt;
&lt;p&gt;And there still are proprietary clients for git and &lt;span class="caps"&gt;CVS&lt;/span&gt; on Windows, for example, there’s
&lt;a href="https://en.wikipedia.org/wiki/TortoiseCVS"&gt;TortoiseCVS&lt;/a&gt; and friends, but I wouldn’t want to bet my
business on something like that today. Because someone else would come along and make a web-based one,
and it would work almost as well as mine, as best as I could do. And it would cost them a tenth a cost
to develop it. They could sell it for much less than I could sell mine, it would be easier to support –
I’d be out of business. And in fact, almost all of those document management companies have gone out of
business. I think there’s two left of the ones that was at that show, and one of them has been bought by
AutoCAD. So, I think we’re going to be replaced – the question is when, not whether.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: So we will be replaced, or &lt;span class="caps"&gt;GIMP&lt;/span&gt; will go to that format?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: One way or another. That will depend on the people, whether the people are willing to do
that change, and they’re around when it happens.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: And so &lt;span class="caps"&gt;GIMP&lt;/span&gt; would run remotely on some server?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: It’ll run in your web browser.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: So still locally, but on your web browser?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Yeah, I think so.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Serpentin-Tanzerin, from Moderne Kunst in Meister-Holzschnitten Band XV, scanned and restored by Liam Quin, CC-BY-SA" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/tangerine-angel.jpg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;&lt;a href="https://www.fromoldbooks.org/ModerneKunst-15/pages/133-tangerine-angel/"&gt;Serpentin-Tanzerin&lt;/a&gt;, 
from Moderne Kunst in Meister-Holzschnitten Band &lt;span class="caps"&gt;XV&lt;/span&gt; (1901), scanned and restored by Liam Quin, &lt;span class="caps"&gt;CC&lt;/span&gt;-&lt;span class="caps"&gt;BY&lt;/span&gt;-&lt;span class="caps"&gt;SA&lt;/span&gt;&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;em&gt;Simon: So this is my question. When you say Web page or Web browser, you’re not talking about&lt;/em&gt;
&lt;em&gt;Software as a Service.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: No, I’m actually talking about a program written in Javascript or something that compiles
into Javascript, more likely. What they call a transpiler these days.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Simon: But users doesn’t necessarily have to realize it’s doing this, right?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: No, correct. They’d look identical for all we know, because every &lt;span class="caps"&gt;GIMP&lt;/span&gt; window would just
be a browser window.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: It’s funny because Mitch had basically a question about this. Did you read Mitch’s message?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Yes I did.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: He had &lt;a href="https://www.gimp.org/news/2017/03/01/an-interview-with-michael-natterer-gimp-maintainer/#gimp-future:~:text=Yes%20but%20in%20the%20past%20people%20wanted%20to%20use%20JavaScript"&gt;a question about Javascript&lt;/a&gt;, and we kind of laughed about it.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Simon: Yeah, but this was a different Javascript approach.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Javascript for the &lt;span class="caps"&gt;UI&lt;/span&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Simon: Yes, but not necessarily via a browser.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I’m expecting gegl.js to happen, let’s put it that way.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Simon: In some ways I think it’s even already happened.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: It has already, because people have done the automatic translation. But what you really
want is something written to take advantage of the browser’s own image processing capabilities
whereever it can, so it actually goes fast.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Simon: And, for example, having a WebGL backend or something.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Yeah. I mean, things written in the browser, in Javascript, can actually be reasonably
performant now, they can go reasonably fast. I just think it will happen. If it doesn’t happen,
what will happen is someone will write – people are already writing – one of the many photo-editing
applications and art applications that are happening as web apps now, will take over. Because there
will be 20 million users of the one, and 5,000 users of the other, probably. But that would be sad
because there’s so much work that’s gone into &lt;span class="caps"&gt;GIMP&lt;/span&gt;. I would like to see it carry on, but I just
think that the future may be running in web browsers.&lt;/p&gt;
&lt;p&gt;I don’t know for sure. I mean I’m not sure I like it. I’m not saying drop everything and do this
now, but I am saying
“&lt;em title="Mark 13:33"&gt;keep your sword at your side, for you know not when the hour will come&lt;/em&gt;”.
That’s a Biblical quote – they’re actually referring to the end of the world &lt;em&gt;[laughing]&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Is there something regarding your work with &lt;span class="caps"&gt;GIMP&lt;/span&gt;, for your stock image company - is there
anything in &lt;span class="caps"&gt;GIMP&lt;/span&gt; that you’re really looking forward to? A feature or planned change, to really
help your daily work?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Yeah, actually. I think that non-destructive editing when that happens will really help me.
Because the ability to go back and conceptually edit the graph, for example, to have a check box –
not saying you’d do it this way – but imagine having a checkbox by each entry in the undo history,
and being able to deselect one of them and see what the image would be like if I didn’t do this.
You can’t actually implement it like that inside &lt;span class="caps"&gt;GIMP&lt;/span&gt;, but that’s a way of thinking about how it
might look.&lt;/p&gt;
&lt;p&gt;Because quite often I would do something like a 10, 15, 20 pixel radius blur to get rid of screening
artifacts, and then I have to do several other operations and scale the image down and sharpen
before I get an image I can sell. I can’t sell a blurry image, but I can’t sell one that’s made
up of lots of dots either. So I have to get rid of the dots and I do that either by blurring or
&lt;a href="https://docs.gimp.org/3.2/en/plug-in-wavelet-decompose.html"&gt;wavelet decompose&lt;/a&gt; or something like
that. And then I do other operations, and I discover some time later that I didn’t use the right radius
for my blur, because the challenge is to use the smallest radius that gets rid of all the dots. If I use
too big a radius, I get an image that’s too blurry to sell. If I use too small a radius, when I scale the
image down, the dots come back when I sharpen it. So I can imagine being able to go back and just change
that radius, and have &lt;span class="caps"&gt;GIMP&lt;/span&gt; show me the result of the scaled down image, and I can see “Yes, great, that
was the right number!”.&lt;/p&gt;
&lt;p&gt;So the non-destructive editing will be a big plus for me.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;[&lt;strong&gt;Editor’s note&lt;/strong&gt;: Non-destructive editing was added in &lt;span class="caps"&gt;GIMP&lt;/span&gt; 2.99.18, and officially released in &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.0 in 2025!]&lt;/em&gt;&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Grose: Antique Books, photographed by Liam Quin, CC-BY-SA" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/grose-antique-books.jpg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;Image of
&lt;a href="https://www.fromoldbooks.org/pictures-of-old-books/pages/p7110009-grose-antique-books-with-candle/"&gt;Grose: Antique Books&lt;/a&gt;, photographed by Liam Quin, &lt;span class="caps"&gt;CC&lt;/span&gt;-&lt;span class="caps"&gt;BY&lt;/span&gt;-&lt;span class="caps"&gt;SA&lt;/span&gt;&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;em&gt;Jehan: You also have a very interesting use case, which is that you work on very, very big images.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I hear that a lot from &lt;span class="caps"&gt;GIMP&lt;/span&gt; people. I hear it a lot from photography people. I never hear
it from print people. People doing graphic design with print, are not surprised if an image says it
takes a gigabyte of memory for one layer. &lt;/p&gt;
&lt;p&gt;&lt;em&gt;[Audible gasp of shock from the audience]&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We have people who come to the &lt;span class="caps"&gt;GIMP&lt;/span&gt; &lt;span class="caps"&gt;IRC&lt;/span&gt; channel, say they do work for print, and they’re editing
a 20,000 by 15,000 pixel image in &lt;span class="caps"&gt;RGB&lt;/span&gt; mode and it’s going a bit slowly, and what should they do
about this?&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Yes, of course you always have people who have bigger images, but what is a typical size for you?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Well, that &lt;em&gt;is&lt;/em&gt; a typical size. I was editing one yesterday that was 3.6 gigabytes when I first
opened it, just one layer. And I scan in high resolution because people typically want a detail of an
image at large size, and also because I can produce higher quality images than most other people. And
if you’re a small company, you’ve got to have an advantage over the big companies. The big companies
have millions of mediocre images and I’ve got thousands of really good ones, so people come to me.
And it works.&lt;/p&gt;
&lt;p&gt;There are some issues with &lt;span class="caps"&gt;GIMP&lt;/span&gt;. I mean, 16 gigabytes of memory is a minimum. My laptop’s not really
good enough for the larger images, it has 8 gigabytes. My desktop has 32 gigabytes and that’s okay,
as long as you don’t use multiple layers. You start using too many layers then you have to be careful.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Do you think that &lt;span class="caps"&gt;GIMP&lt;/span&gt; handles the images well?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Pretty well. I understand that compared to two or three other image editors that I’ve use,
it seems very slow with these images. An example is if I do
&lt;a href="https://docs.gimp.org/3.2/en/gimp-tool-curves.html"&gt;Curves&lt;/a&gt;, after pressing Okay I might
have to wait 5 minutes, whereas in the other editors I don’t have to wait at all.&lt;/p&gt;
&lt;p&gt;The reason for that though is that they’re doing the work in the background, and they’re just showing
me the preview image, what I can see on the screen, and then they’re applying curves in the background
to the full image. And every now and again you catch up and the program tells you to wait for no
obvious reason, so it’s a trade-off.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: So do you think it’s better what we’re doing, or do you think…?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I actually think in most cases it’s better to do the work in the background, because after
I’ve done Curves, I probably want to look at the image and think for a minute about what to do next,
and the program could make use of that time. But I’m also aware that there’s a lot of optimizations
that has not been done to &lt;span class="caps"&gt;GEGL&lt;/span&gt; yet, and it could well be that the bottlenecks could be improved a lot.
So I’m not too worried about it right now. It’s usable, there are places where it’s slow, and I’m not
too worried.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Aryeom: I want to hear about your typography.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Yeah, I have a background in typography.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Requiem by Liam Quin, CC-BY-SA" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/calligraphy.jpg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;&lt;a href="https://www.deviantart.com/barefootliam/art/Requiem-6452203"&gt;Requiem&lt;/a&gt; by Liam Quin, &lt;span class="caps"&gt;CC&lt;/span&gt;-&lt;span class="caps"&gt;BY&lt;/span&gt;-&lt;span class="caps"&gt;SA&lt;/span&gt;&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;em&gt;Aryeom: And you have another art style.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I do, I’ve done other art, yes. I do calligraphy as well. But the calligraphy I do is
done with pen and ink and gouache and paper. That’s partly because I don’t have a tablet. So
this week I actually got to try graphics tablets, thank you, although I discovered it didn’t
work with &lt;span class="caps"&gt;GIMP&lt;/span&gt; 2.9 properly, the preview version. It did work with 2.8, and I think I could
get use to drawing with a tablet. So that was quite interesting – I wasn’t sure before. And
it would be quite interesting to do some calligraphy with a tablet. But with calligraphy I’m
use to looking at the pen, positioning it between pencil lines and thinking about each stroke.
I think working with a tablet would be more like brush calligraphy than paint calligraphy, but
I don’t know.&lt;/p&gt;
&lt;p&gt;The hardest thing I’ve found is that the tablet’s surface is too smooth. So the bite of the paper,
as they call it, which slows you down when you’re drawing, is an important part of calligraphy.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Someone was telling me about Wacom tablets, and other tablets I think, where you can put
paper on the tablet and you actually draw on it. Have you seen that kind of stuff?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I see! I hadn’t thought of that, that would be really interesting. And the computer
would record the drawing while I made it.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: You can even do it while the tablet is unplugged, because it will record it and then
later you can plug it in.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Aryeom: Yes, but it’s vector.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: Maybe vector, yeah.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Aryeom: Can you send us your work?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Yes I can. I can send you some pictures, yeah. Some of it has been published so
that’s quite nice. I had a calligraphy piece that was used on the front cover of Time magazine,
so that was quite nice. I don’t often get phone calls from the art director of Time magazine,
so that was a surprise.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Front Cover of Time Magazine, featuring calligraphy by Liam Quin" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/liam-time-magazine.webp"/&gt;
&lt;figcaption&gt;
&lt;em&gt;Front cover of
&lt;a href="https://time.com/magazine/us/3570705/april-24th-2006-vol-167-no-17-u-s/"&gt;Time Magazine&lt;/a&gt;, 
featuring calligraphy by Liam Quin&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;em&gt;Americo: I have a question. Do you have any advice for users, artists, photographers who think
about or consider using &lt;span class="caps"&gt;GIMP&lt;/span&gt;? Do you have any advice on how we should approach it?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I suppose it depends on what you’re trying to achieve and your personality. So if
your personality is that you just like to go and do things quickly, as I said earlier. If you
want the MyPaint style where you just go and do, but you want more richness, which &lt;span class="caps"&gt;GIMP&lt;/span&gt; gives you.
For example, you might make a set of images which are blank or mostly blank, and basically use them
like templates. You just double-click on an image and &lt;span class="caps"&gt;GIMP&lt;/span&gt; comes up with that blank image, and then
you start. Which is much easier than doing &lt;code&gt;File&lt;/code&gt; → &lt;code&gt;New&lt;/code&gt; and
&lt;a href="https://docs.gimp.org/3.2/en/gimp-file-create-template.html"&gt;using a &lt;span class="caps"&gt;GIMP&lt;/span&gt; template&lt;/a&gt;. Then you can just
start painting.&lt;/p&gt;
&lt;p&gt;I mean you could ask people who paint. We have people like Americo here, who is doing fabulous
stuff with making his own brushes from patterns in the clipboard and with paint dynamics, and
really spending a lot of thought into exploring the tool and what it can do.&lt;/p&gt;
&lt;p&gt;And you have other people who say, “All I want is something like a charcoal stick with undo”.
Or you have people who want things more like an engineering drawing. I occasionally do text-based
art with &lt;span class="caps"&gt;GIMP&lt;/span&gt;. I’m more likely to use Inkscape because it has slightly better typography. And
these days I’m more likely to use a web browser and &lt;span class="caps"&gt;CSS&lt;/span&gt;, because I can get the OpenType features
which I can’t in &lt;span class="caps"&gt;GIMP&lt;/span&gt; or Inkscape. If you’re a typographer, being able to use the font properly
is important to you. &lt;span class="caps"&gt;GIMP&lt;/span&gt; is very, very limited at this time, it really is. But it has it, and
it’s the only thing you can go back and edit afterwards. So from that point of view… &lt;em&gt;[laughing]&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I think the biggest two problems I hear with people using &lt;span class="caps"&gt;GIMP&lt;/span&gt;, one of them is they haven’t found
Single Window Mode. If you’re not someone who grew up with the X Window System and applications
having 25 windows, you might find it really cluttered and difficult to manage. So then you get switched
to Single Window Mode, which I use. Even though I used the X Window System as early as 1988 I think.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Simon: It’s the default now, at least for 2.9.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I’m glad it’s the default. It’s not perfect, it was never finished, but it’s more approachable.&lt;/p&gt;
&lt;p&gt;The other default that people often have to change is the
&lt;a href="https://docs.gimp.org/2.10/en/gimp-using-setup-tile-cache.html"&gt;tile cache size&lt;/a&gt;. If you’re working with
print images especially, then you need to change the tile cache size to be three-quarters of your
physical memory or maybe more, depending on what else you’ve got running. You want as much in memory
as possible without crashing your system, and it can be a hard trade-off.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Americo: Something I often discover is that people try to “get” &lt;span class="caps"&gt;GIMP&lt;/span&gt; by trial and error, and I’m not&lt;/em&gt;
&lt;em&gt;sure if this is the right approach to software as complex as &lt;span class="caps"&gt;GIMP&lt;/span&gt;. I’ve tried this with Paint Shop Pro&lt;/em&gt;
&lt;em&gt;and also Photoshop, and I didn’t get far either. I always have to turn to the manual.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I believe it’s deliberate that you can’t in Photoshop. Paint Shop Pro I don’t know about,
it’s been years since I used it. But I suspected – don’t know this for sure – I suspect that in
Photoshop, what they’re trying to do – you use to get this from the Debian community as well –
the idea is to make something hard enough, it’s a trial by fire. You make something hard enough,
that people have to put real emotional effort into learning it. And then they’ll stick with it
through thick and thin. Because they’ve put so much emotional effort into learning something so hard.&lt;/p&gt;
&lt;p&gt;Photoshop and Illustrator have an interface where there’s hidden buttons in the toolbox. You
hold down the mouse pointer over one of the little squares in the toolbox and eventually a
hidden secret drawer opens and more tools appear. There’s no way you would discover something
like that, right, it’s not discoverable. The way that you find it is the manual or a tutorial.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;[&lt;strong&gt;Editor’s note&lt;/strong&gt;: In &lt;span class="caps"&gt;GIMP&lt;/span&gt; 2.10, we ended up adding an option for these “hidden buttons”, known as &lt;a href="https://docs.gimp.org/3.2/en/gimp-tools.html#:~:text=grouped%20by%20default.-,Tool%20groups,-are%20marked%20with"&gt;tool groups&lt;/a&gt;]&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;So for &lt;span class="caps"&gt;GIMP&lt;/span&gt;, probably the best of the books I’ve seen for learning &lt;span class="caps"&gt;GIMP&lt;/span&gt; is called
“&lt;a href="https://nostarch.com/gimp2"&gt;The Artist’s Guide to &lt;span class="caps"&gt;GIMP&lt;/span&gt;&lt;/a&gt;”,
and I love that guy’s tutorials. He says things like, “To start with, press &lt;kbd&gt;D&lt;/kbd&gt; on the
keyboard to get the black and white default colors. Now press  &lt;kbd&gt;X&lt;/kbd&gt; to exchange them.
Now you’re drawing with white.”. And telling you things like that, mean that the tutorial will
work regardless of your previous settings. He’s teaching you a way of using &lt;span class="caps"&gt;GIMP&lt;/span&gt; where you
don’t mess yourself up, and if you don’t mess yourself up, you have much more confidence to explore.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Cover of The Artist's Guide to GIMP, Michael Hammel" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/artist-guide-to-gimp.jpg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;Cover of ‘The Artist’s Guide to &lt;span class="caps"&gt;GIMP&lt;/span&gt;’, by Michael Hammel&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;So I really love his tutorials. He explains, he says how you can do things by clicking, or by
using the keystroke or by using the menu. It’s really, really well done. So that’s what I have
suggested to people who want to learn &lt;span class="caps"&gt;GIMP&lt;/span&gt;, is that particular book. But other people prefer
video tutorials. I don’t have patience for video tutorials – just tell me! But a lot of other
people like them.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Aryeom: If I want to make a tutorial, is there any advice on the best way?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I’ve done some tutorials that people didn’t like, and some that they really did like.
And the tutorials that people really did like are the ones where you’re teaching, and at the
same time you’re not assuming. So you don’t assume that people know jargon, you don’t assume
that people know special names. If you start off in a tutorial saying “The first thing you’ve
got to do is add an alpha channel to your image, and then divide the hypotenuse by the cosine
of the vertex”, you’ve lost three-quarters of your audience.&lt;/p&gt;
&lt;p&gt;If instead you say, “We need our layer to be transparent so that we can see things in the
lower layers through it, and to do this, we have to use a menu item called &lt;code&gt;Add Alpha Channel&lt;/code&gt;”,
then what you’ve done is you’ve taught someone what alpha channel means and why they want to use
it. So instead of just saying “Do this, do this, do this”, if you teach people a little while,
you’re also writing a tutorial that’s more robust. Because it might be that in a future version
of &lt;span class="caps"&gt;GIMP&lt;/span&gt;, the menu moves. So you can build in notes. You can do things like say, “If you can’t
find this, you can use the slash key to search for things in the new release. This is how you do
that”. And then you might make a tutorial that’s robust and that people follow. Because people get
really upset if they find a tutorial for &lt;span class="caps"&gt;GIMP&lt;/span&gt; version 1.2 and they try to follow it and it doesn’t
work. So then they find a tutorial for some other image editor and they try to follow that and it
doesn’t work, obviously. And they get angry and swear at us, and maybe they come to &lt;span class="caps"&gt;IRC&lt;/span&gt; and say
your program is full of worms and your mother was a raspberry tart! And we say, “Why are you saying this?”
and they say this tutorial doesn’t work!&lt;/p&gt;
&lt;p&gt;You can’t write something that’s going to be proof against future completely, but you can write
something that’s going to be a little bit robust, and that teaches people and keeps the sense of
delight and fun. And if you do that, people will enjoy using your tutorial and learn from it,
and you’ll have fun.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Aryeom: Thank you for the advice!&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I’m hoping to do some tutorials this year for scanning images, working on scanning
images from books, old books, published, printed books.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: That’s good – for gimp.org?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Yeah, I hope so. One of the things I’m really hoping for is the
&lt;a href="https://en.wikipedia.org/wiki/Scanner_Access_Now_Easy"&gt;XSane project&lt;/a&gt; makes a version of their
&lt;span class="caps"&gt;GIMP&lt;/span&gt; plug-in that works with the new release, with 2.9, to do high bit depth images. Right now it’s
restricted to 8 bits per channel. My scanner can do 16 bits per channel, &lt;span class="caps"&gt;RGB&lt;/span&gt;, it’s A4 or Tabloid size.
But in fact XSane crashes if I try to do that.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: So you scan with another software?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I scan with XSane, but I have to save it to a file and then I have to open the file in &lt;span class="caps"&gt;GIMP&lt;/span&gt;.
And that’s actually a pain for me, because the point at which I choose the file name, the book is still
on the scanner, and my file names are usually the page number in the book and the caption as the file name.
But if the book is on the scanner then I can’t see what page number it’s on, so I have to remember beforehand
to write down the page name, so it’s a pain. So if I’m scanning six images or something at once with the
plug-in, it arrives one after the other in &lt;span class="caps"&gt;GIMP&lt;/span&gt;. And a fabulous &lt;span class="caps"&gt;GIMP&lt;/span&gt; feature, not in any of the other
software I’ve used, is that I can be scanning one image with a progress bar going along, cleaning up
another one, and saving a third one, all at the same time. And that’s three times the throughput that I
get with other software.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Happy New Year from Moderne Kunst in Meister-Holzschnitten Band XIII, scanned and restored by Liam Quin" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/happy-new-year.jpg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;&lt;a href="https://www.fromoldbooks.org/ModerneKunst-13/pages/133-monkey/"&gt;Happy New Year&lt;/a&gt; 
from Moderne Kunst in Meister-Holzschnitten Band &lt;span class="caps"&gt;XIII&lt;/span&gt; (1897), scanned and restored by Liam Quin&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;I’ve been to places where they’re scanning books professionally, and they have three, four, five computers
in a row, with multiple scanners. So you start scanning on one, then you move to the next one, start
scanning on that, go back to the first one, start cleaning it up, go to the next one, start that one
scanning, go this one, start saving the image – because that other proprietary software could only do
one of those things at a time. That’s still true today.&lt;/p&gt;
&lt;p&gt;So by using the plug-in I get much more throughput, so I can have the scanner going – and it can take
up to 20 minutes to scan an image, and it can take up to 5 or 10 minutes to save an image. For &lt;span class="caps"&gt;GIMP&lt;/span&gt; to
export an image to &lt;span class="caps"&gt;PNG&lt;/span&gt; for example, can take 5 or 10 minutes if it’s a several gigabyte image going to
a hard drive. So, it’s really nice to be able to work effectively with multiple threads. I like that.&lt;/p&gt;
&lt;p&gt;So I should write some tutorials because &lt;span class="caps"&gt;GIMP&lt;/span&gt; really is better than anything else I’ve used.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Aryeom: I will translate it to Korean because I’ve seen someone on a Korean website asking how to&lt;/em&gt;
&lt;em&gt;scan in &lt;span class="caps"&gt;GIMP&lt;/span&gt; like this.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Okay! Maybe they’ve already written a better tutorial than I will, we’ll see. I’ve been doing it
for more than ten years. 1999, I think, I started my website,
&lt;a href="https://www.fromoldbooks.org/"&gt;fromoldbooks.org&lt;/a&gt;. So it’s going to be coming
up to 20 years old before too long. Some of the books are 500 years old.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: And you’ve been using &lt;span class="caps"&gt;GIMP&lt;/span&gt; since the beginning?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I used &lt;span class="caps"&gt;GIMP&lt;/span&gt; early on. I had a period when I was writing a book and the publisher required me to
use Microsoft Office, so I was on Windows. For a lot of that time I was using other software. I actually
end up using Paint Shop Pro because it had something like, what &lt;span class="caps"&gt;GIMP&lt;/span&gt; calls a corrective or reverse transformation.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: And &lt;span class="caps"&gt;GIMP&lt;/span&gt; did not have it?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: &lt;span class="caps"&gt;GIMP&lt;/span&gt; had it, but &lt;span class="caps"&gt;GIMP&lt;/span&gt; wasn’t doing well on Windows at the time. And the other software I had,
Photoshop, did not have anything like a corrective mode that was as useful. &lt;span class="caps"&gt;GIMP&lt;/span&gt;’s corrective mode is
actually better because it’s a grid and not just a line. The Photoshop one, as I recall, you draw a line
on something that should be horizontal or vertical. But in most scanned images I’ve got, they’re
hand-made engravings, there isn’t going to be a definite horizontal or vertical, because it’s an
artist’s sketch. So I have to choose what looks best. I start out by getting the grid roughly right,
clicking rotate and seeing what happens. Flatten the image to get rid of the corner artifacts and
seeing what it looks like. And if it looks okay – with experience you can most of the time do it
first time.&lt;/p&gt;
&lt;p&gt;One of my few patches to &lt;span class="caps"&gt;GIMP&lt;/span&gt; in fact, was to change the undo history to say what the angle was.
This way, I can do an undo, even half an hour later, I can see what the angle was and I can say,
“Well, that was just a bit too much, I’ll try reducing it just a bit and try again”, and usually
second go I get it right. And that’s an example of it being an open source free/libre software.
I was able to contribute a patch, which Mitch kindly rejected, and I was able to redo it, and
get it in the right format. And he incorporated it – and then I think he wrote it even more.
Looking at the code yesterday I discovered – it’s a year or two since I did the patch – I looked
at the patch and discovered it’d been rewritten even more, which is good. But that simple patch
has saved me, cumulatively, hours and hours of work, just knowing that information. Because I
might do two or three rotations in a sequence, then go back and undo them and do a single
rotation, because you degrade the image slightly when you rotate it. And if it takes 10, 15
minutes to do a rotate of a large image, then saving two or three attempts at rotation everyday
has saved me a lot of time, you know.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Screenshot of Undo History with Rotation Angles shown, from Liam's patch" src="https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/undo-history-rotation-angles.png"/&gt;
&lt;figcaption&gt;
&lt;em&gt;Screenshot of Undo History with Rotation Angles shown, from Liam’s patch&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;So that’s all part of why &lt;span class="caps"&gt;GIMP&lt;/span&gt; is so fabulous. That, and being able to come onto the &lt;span class="caps"&gt;IRC&lt;/span&gt;
channel and say a particular thing is really slow. The first time I did that, it was Sven
at the time years ago, he couldn’t believe it was taking me 20, 25 minutes to rotate an image.
He looked at the code, and he had me do some profiling, and then he said “Oh”, and made a one
line fix. And it went down from 20 minutes to 2 minutes the next time I recompiled &lt;span class="caps"&gt;GIMP&lt;/span&gt;, ten
minutes later. Same day! A fix on the same day. In the libre graphics world, in the free software
world, that’s not unusual. In the “I’ll make a support ticket with my vendor” world, it’s not
unheard of but it’s pretty rare. So that’s been a real plus.&lt;/p&gt;
&lt;p&gt;Sometimes the developers will say “No, we can’t make that faster because…”, or “We won’t,
because we’re going to replace it”. But there’s been a few occasions when &lt;span class="caps"&gt;GIMP&lt;/span&gt; has been
faster because I’ve gone into the &lt;span class="caps"&gt;IRC&lt;/span&gt; channel and said I profiled this, or here’s a patch,
or can someone fix that. So it’s been fabulous.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Jehan: I think we’ve asked most questions. Is there anything you’d like to say that we didn’t ask you?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: Yeah. The biggest thing I think we have to do, is get a message out to the world
that &lt;span class="caps"&gt;GIMP&lt;/span&gt; is perfectly suitable for professional use. It’s aimed at professional use, and
people are using it professionally, successfully. It’s not a second choice, it’s a first
choice. It’s not because I can’t afford this other program, or because my principles say
I don’t eat meat, or I don’t use programs beginning with P. It’s a first choice – it’s
actually better for what I’m doing then any other program I’ve used, and I’ve used a lot.&lt;/p&gt;
&lt;p&gt;So we need to get that message out a lot more, and we need to have more confidence in
talking about &lt;span class="caps"&gt;GIMP&lt;/span&gt;. We’re close to it, we see all the problems, we have visions that
we know are not happening, and yet, we forget sometimes that we’ve got something really
really good there. And we need not be ashamed to say that.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Aryeom: Why do you think people are sometimes ashamed or don’t have confidence to use &lt;span class="caps"&gt;GIMP&lt;/span&gt;?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Liam&lt;/strong&gt;: I knew a chemist once who worked in a jam factory, where they made marmalade and jam.
And he saw what the jam did to the steel containers where they mixed it. And they had huge steel
vats like the size of a small building, like a big mixing bowl. And the jam is highly acidic,
and it would eat the steel. And he said he would never eat jam again, after seeing how jam was
made. But you know, if you make jam at home it’s no better. It’s no better than any other food,
or worse – alright, it may have too much sugar in it. Or it’s like the sausage maker who knows
what goes in the sausage.&lt;/p&gt;
&lt;p&gt;We’re aware of all the problems, and we’re aware that we have visions of how &lt;span class="caps"&gt;GIMP&lt;/span&gt; could be in
some other universe, and it isn’t. But that’s okay, it’s what it is. The fact we can say, the
text tool could be improved so that after you scale the image, text is still text for example.
We can look at that and say “Yeah, that’d be fairly easy to fix but we’re busy”. But we still
have a better text tool than a lot of other programs, you know, even without making any other
changes. We’re too busy to go look at other programs – and perhaps worried too about intellectual
property, about using someone else’s design. But the truth is, &lt;span class="caps"&gt;GIMP&lt;/span&gt; is better than, in many ways –
not perfect, not saying that – but it’s better in many ways than we realize.&lt;/p&gt;
&lt;hr/&gt;
&lt;p&gt;&lt;strong&gt;Links&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://delightfulcomputing.com"&gt;Liam’s company, Delightful Computing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.fromoldbooks.org/"&gt;Liam’s other company, From Old Books&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description>
      <guid isPermaLink="false">https://www.gimp.org/news/2026/10/01/liam-quin-interview-lgm2017/</guid>
      <pubDate>Wed, 30 Sep 2026 22:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Michael Catanzaro: How to Request a CVE</title>
      <link>https://blogs.gnome.org/mcatanzaro/2026/10/02/how-to-request-a-cve/</link>
      <description>&lt;p class="wp-block-paragraph"&gt;As &lt;a href="https://blogs.gnome.org/mcatanzaro/2026/08/27/change-in-timeline-to-some-changes-to-gnome-security-tracking/"&gt;previously announced&lt;/a&gt;, I have discontinued my tracking of GNOME security issues. Nobody else has volunteered to continue that work, so it has concluded (except for issues reported during September 2026, which I will keep an eye on until the end of this month).&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Maintainers, I encourage you to request your own CVEs by writing to &lt;a class="external" href="https://access.redhat.com/security/team/contact"&gt;Red Hat Product Security&lt;/a&gt;. Red Hat is an ideal CNA (CVE Numbering Authority) to use for GNOME CVEs because you will receive timely responses. Ignore Red Hat’s suggestions to encrypt your mail using GPG, and use the following email template:&lt;/p&gt;
&lt;pre class="wp-block-code"&gt;&lt;code&gt;Hi, I request a CVE for:

Summary:
Requirements to exploit:
Component affected:
Version affected: All versions &amp;lt;-- change this if needed
Patch available: Yes/No
Version fixed (if any already):
Upstream coordination: See issue report (below)
CVSS (optional):
Impact (optional):
Embargo: No
Acknowledgment:
Steps to reproduce if available: see issue report
Mitigation if available: &amp;lt;-- it's OK to write "None"
Original report:&lt;/code&gt;&lt;/pre&gt;
&lt;p class="wp-block-paragraph"&gt;Request a CVE after making your issue report public. It’s possible to reserve a CVE in advance, but this requires twice as many steps, so I recommend making it public first, then request a CVE second. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;GNOME and Fedora maintainers should feel free to get in touch with me if you have questions.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/mcatanzaro/2026/10/02/how-to-request-a-cve/</guid>
      <pubDate>Fri, 02 Oct 2026 15:00:15 +0000</pubDate>
    </item>
    <item>
      <title>Michael Catanzaro: The Era of Software Quality, or the Era of Ostriches?</title>
      <link>https://blogs.gnome.org/mcatanzaro/2026/10/02/the-era-of-software-quality-or-the-era-of-ostriches/</link>
      <description>&lt;p class="wp-block-paragraph"&gt;Humans are bad at writing secure code, and GNOME developers are no exception. GNOME is primarily written using unsafe programming languages where &lt;a class="external" href="https://wingolog.org/archives/2011/10/13/whats-your-c-migration-plan"&gt;simple mistakes in our code lead to devastating consequences for our users&lt;/a&gt;, and &lt;a href="https://blogs.gnome.org/mcatanzaro/2022/07/27/common-glib-programming-errors/"&gt;we make these mistakes all the time&lt;/a&gt;. No matter how much we try, GNOME developers will fail write secure code when using unsafe languages like C, C++, or Vala: it’s just too hard for even experienced developers to do properly.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;The above paragraph is taken from the abstracts of my GUADEC 2024 and 2025 talks. At the time, I thought failure was inevitable: we humans were so bad at writing software that we had no chance to do it properly, and I certainly would not have trusted an AI to do better than a human. But the landscape today is completely different than last year. AI has improved considerably, and offers a magic fairy wand solution to this problem: we can now simply ask a language model to look for vulnerabilities in our software. &lt;a class="external" href="https://github.com/fwupd/fwupd/releases/tag/2.0.21"&gt;They are quite good at this.&lt;/a&gt;&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;&lt;strong&gt;There is zero hope of maintaining quality software in 2026 without AI vulnerability scanning.&lt;/strong&gt; Any claims to the contrary are unserious and delusional. The tremendous quantity of bugs found in our best-maintained projects, like GLib and fwupd, should speak for itself. Failure to scan our projects is an unfair disservice to our users. If we don’t find the vulnerabilities by scanning projects ourselves, attackers certainly will, because the Linux user base has increased to the point that Linux users are finally numerous enough to be worth targeting. Meanwhile, AI has made it easier than ever to build &lt;a href="https://blogs.gnome.org/mcatanzaro/2026/05/21/single-click-code-execution-exploit-for-evince-atril-and-xreader/"&gt;working exploits&lt;/a&gt;, which was previously unheard of.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Already resolved all the detectable vulnerabilities? Then ask the AI to look for non-security bugs as well, to further improve quality. GNOME code is generally much better than it used to be, but there remains considerable room for improvement. For the first time in history, we now have the opportunity to improve software quality to a degree that was never realistic before.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Have you heard that most AI bug reports are “slop?” Not so in 2026. That was true for most of 2025, but the quality of AI-generated vulnerability reports has drastically improved. That is not to say that we no longer have problems with bad vulnerability reports, but in general, nowadays most of them are pretty good. (&lt;a class="external" href="https://daniel.haxx.se/blog/2026/04/22/high-quality-chaos/"&gt;Daniel Stenberg reports the same pattern for curl.&lt;/a&gt;)&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;AI-generated vulnerability reports have nevertheless introduced many undesirable impacts on GNOME maintainers. They are usually annoyingly verbose and unnecessarily detailed. They often exaggerate the severity of the problem, or make misleading or irrelevant claims. They are occasionally incorrect. Sometimes they include outright fabricated data, such as &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gegl/-/issues/477#note_2881273"&gt;fake stack traces&lt;/a&gt; (which is not the norm, but sadly also not uncommon). A good human reviewer will notice and resolve most of the above problems before creating a bug report on your issue tracker, but often problems are reported by inexperienced humans who do not actually know what they are looking at and simply copy/paste everything blindly. Even when the generated issue report is good and avoids all of the above problems (which is rare), good vulnerability reports in sufficiently high quantity can still overwhelm volunteer maintainers. And even if reporters submit a merge request to resolve the problem so maintainers don’t have to (which is also rare), reviewing those merge requests is itself more unwelcome work for overworked maintainers.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;That all is to say: I understand the pain caused by the current wave of AI-generated issue reports. Nevertheless, they are essential and unavoidable. We have to learn to accept and deal with them, not stick our heads in the sand and ignore them.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Some GNOME maintainers have adopted a policy prohibiting AI-generated content in issue reports. Do not do this. Nowadays, the overwhelming majority of vulnerability reports are AI-generated. Projects that choose to ban AI-generated content in issue reports might as well ban all vulnerability reports; the effect will be approximately the same.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I propose the following:&lt;/p&gt;
&lt;ul class="wp-block-list"&gt;
&lt;li&gt;GNOME maintainers should rewrite their AI contribution policies to permit AI-generated vulnerability reports, &lt;a href="https://blogs.gnome.org/mcatanzaro/2026/06/08/please-do-not-ban-ai-assisted-issue-reports/"&gt;as I previously requested four months ago&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Projects that continue to prohibit AI-generated vulnerability reports are no longer suitable dependencies for GNOME, and should be developed someplace other than GNOME GitLab.&lt;/li&gt;
&lt;/ul&gt;
&lt;p class="wp-block-paragraph"&gt;We don’t have to tolerate &lt;em&gt;bad&lt;/em&gt; issue reports, but AI use alone should not be disqualifying.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Shouldn’t humans rewrite AI-generated bug reports?&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;When I complain that maintainers should allow AI-generated vulnerability reports, the most common counterargument is that humans should read the AI’s report, understand it, and rewrite the entire thing to remove all AI-generated content. Some bug reporters actually voluntarily do this, but this is rare.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Vulnerability reporting is a public service, not an obligation. If you ask a reporter to do any amount of extra work, they might be willing to do so, but it’s much more likely that they will either stop looking at your project and move on to something else, or continue looking at your project and publish the vulnerability reports someplace other than your issue tracker.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Rewriting issue reports also does not scale. Let’s say you use AI to find 100 security bugs in a GNOME project, a number consistent with the results of actual scans (read on). Would you really spend months rewriting those bug reports before submitting them to upstream? Validating the AI’s claims, upstreaming the issue reports, and submitting merge requests is already a lot of work. Not many people would be willing to additionally rewrite all the issue reports. That’s more work than everything else combined, and is unrealistic.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Even with just a small number of bugs, I would hesitate to spend much time rewriting an issue report because I have many other tasks I would rather spend my time on. At best, I might prepare a quick summary, but it won’t be as useful as a full report.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;The CVE Wave Hits GNOME&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;The current wave of vulnerability reports is reflected in GNOME’s CVE issuance trends:&lt;/p&gt;
&lt;figure class="wp-block-table"&gt;&lt;table class="has-fixed-layout"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;Year&lt;/strong&gt;&lt;/td&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;GNOME CVEs&lt;/strong&gt;&lt;/td&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;GNOME CVEs Excluding GIMP, Gegl, libxml2, and libxslt&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2021&lt;/td&gt;&lt;td class="has-text-align-center"&gt;21&lt;/td&gt;&lt;td class="has-text-align-center"&gt;14&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2022&lt;/td&gt;&lt;td class="has-text-align-center"&gt;14&lt;/td&gt;&lt;td class="has-text-align-center"&gt;6&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2023&lt;/td&gt;&lt;td class="has-text-align-center"&gt;13&lt;/td&gt;&lt;td class="has-text-align-center"&gt;4&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2024&lt;/td&gt;&lt;td class="has-text-align-center"&gt;37&lt;/td&gt;&lt;td class="has-text-align-center"&gt;28&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2025&lt;/td&gt;&lt;td class="has-text-align-center"&gt;97&lt;/td&gt;&lt;td class="has-text-align-center"&gt;49&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2026 Year-to-date (2026-09-30)&lt;/td&gt;&lt;td class="has-text-align-center"&gt;141&lt;/td&gt;&lt;td class="has-text-align-center"&gt;74&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2026 Normalized&lt;/td&gt;&lt;td class="has-text-align-center"&gt;188 (141 * 4 / 3)&lt;/td&gt;&lt;td class="has-text-align-center"&gt;99 (74 * 4 / 3)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;The trend here should be pretty clear. Until recently, not many people were reporting vulnerabilities in GNOME. That has changed. We are currently dealing with an order of magnitude more CVEs than just 3 years ago. AI is not the &lt;em&gt;only&lt;/em&gt; reason for this; GNOME maintainers have also gotten a &lt;em&gt;little&lt;/em&gt; better at flagging issues so that I add them to security tracking. But AI is the primary cause for the increase.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;(A few technical notes on this table. CVEs are classified by the year the issue was reported to GNOME, not by the year in the CVE identifier, so e.g. many CVE-2026 issues are counted in 2025. Vulnerabilities reported in 2026 which do not yet have CVEs are not counted, so you can think of the data as being accurate through roughly September 1; multiply the 2026 numbers by 4/3 to make them comparable to the prior years. I count only &lt;a class="external" href="https://gitlab.gnome.org/Teams/Releng/security/-/wikis/home"&gt;issues reported to GNOME Security&lt;/a&gt;, so any unreported CVEs do not count.)&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Although there are still 3 months left in 2026, we will never have data for the rest of the year because &lt;a href="https://blogs.gnome.org/mcatanzaro/2026/10/02/how-to-request-a-cve/"&gt;I have ended security tracking for new issue reports&lt;/a&gt; and nobody else has volunteered to do that work. These CVEs exist only because I request them myself, so I expect the number of CVEs to drastically decrease going forward.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;The CVE Wave Hits WebKitGTK&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;A similar pattern holds for WebKitGTK:&lt;/p&gt;
&lt;figure class="wp-block-table"&gt;&lt;table class="has-fixed-layout"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;Year&lt;/strong&gt;&lt;/td&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;WebKitGTK CVEs&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2015&lt;/td&gt;&lt;td class="has-text-align-center"&gt;175&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2016&lt;/td&gt;&lt;td class="has-text-align-center"&gt;57&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2017&lt;/td&gt;&lt;td class="has-text-align-center"&gt;158&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2018&lt;/td&gt;&lt;td class="has-text-align-center"&gt;101&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2019&lt;/td&gt;&lt;td class="has-text-align-center"&gt;99&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2020&lt;/td&gt;&lt;td class="has-text-align-center"&gt;38&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2021&lt;/td&gt;&lt;td class="has-text-align-center"&gt;52&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2022&lt;/td&gt;&lt;td class="has-text-align-center"&gt;50&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2023&lt;/td&gt;&lt;td class="has-text-align-center"&gt;45&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2024&lt;/td&gt;&lt;td class="has-text-align-center"&gt;38&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2025&lt;/td&gt;&lt;td class="has-text-align-center"&gt;66&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2026 Year-to-date (through &lt;a class="external" href="https://webkitgtk.org/security/WSA-2026-0006.html"&gt;WSA-2026-0006&lt;/a&gt;)&lt;/td&gt;&lt;td class="has-text-align-center"&gt;305&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;CVEs are reported against the year they appeared in a WebKitGTK security advisory, not the year in the CVE ID. The large increase in 2026 is entirely due to AI analysis of Skia and ANGLE. WebKit bundles these libraries because they are not designed to be installed as system libraries, so their vulnerabilities should be counted the same as vulnerabilities in WebKit’s own code. Excluding Skia and ANGLE, there are actually only 21 other WebKitGTK CVEs so far this year, a significant decrease, but excluding CVEs in bundled code would not be fair.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;There has actually been a very large increase in WebKit security fixes this year, but this has not resulted in any increase in CVEs. Apple generally creates CVEs for flaws found by external researchers, not often for flaws found by WebKit developers, so the increase in security fixes is not reflected in the total number of CVEs. Only a small fraction of WebKit vulnerabilities receive CVEs.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I had not previously noticed that the count of WebKitGTK CVEs had, until 2026, been decreasing over the past decade. I am not sure why. I also do not know how to explain the low number in 2016.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Announcing the GNOME Bug Bounty Program and Announcing the End of the GNOME Bug Bounty Program&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;My blog post to-do list says that I need to write a blog post announcing the creation of the &lt;a class="external" href="https://yeswehack.com/business-units/sovereign-tech-fund/programs/gnome-bug-bounty-program/details"&gt;GNOME Bug Bounty Program&lt;/a&gt; on the YesWeHack platform. Oops, too late. It’s already closed. (Once a task enters my to-do list, it can be a &lt;em&gt;very&lt;/em&gt; long time before I get around to doing it.)&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;The GNOME Bug Bounty Program was generously sponsored by the Sovereign Tech Resilience program of Germany’s Sovereign Tech Agency. I’m not sure precisely when it opened, but the first vulnerability was reported on June 27, 2024, so it would have been sometime shortly before then. We accepted issue reports only for GLib, glib-networking, and libsoup, because GNOME had never operated a bug bounty program before and we did not know what to expect. Starting small had — naively — seemed like a prudent way to avoid a large quantity of issue reports. I had wanted to expand the program to cover all of GNOME, but this failed due to the overwhelming deluge in issues reported against GLib and libsoup.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I requested that the bug bounty program end because I was overwhelmed with incoming AI-generated issue reports. The final issue was reported on February 23, 2026. Here are the results:&lt;/p&gt;
&lt;figure class="wp-block-table"&gt;&lt;table class="has-fixed-layout"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;Year&lt;/strong&gt;&lt;/td&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;Reports Submitted&lt;/strong&gt;&lt;/td&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;Reports Accepted&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2024&lt;/td&gt;&lt;td class="has-text-align-center"&gt;26&lt;/td&gt;&lt;td class="has-text-align-center"&gt;14&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2025&lt;/td&gt;&lt;td class="has-text-align-center"&gt;150&lt;/td&gt;&lt;td class="has-text-align-center"&gt;33&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;2026&lt;/td&gt;&lt;td class="has-text-align-center"&gt;122&lt;/td&gt;&lt;td class="has-text-align-center"&gt;24&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;Total&lt;/strong&gt;&lt;/td&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;298&lt;/strong&gt;&lt;/td&gt;&lt;td class="has-text-align-center"&gt;&lt;strong&gt;71&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;Those numbers for 2026 reflect less than two months’ worth of issue reports, so you can see why it was no longer sustainable.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;After the program closed, our work was not done: there was a long backlog of reports to work though. We just last month caught up with accepting the last of the issues reported back in February, and the last bounty was finally awarded earlier today! Even with YesWeHack’s professional triagers analyzing the issue reports before I reviewed them, keeping up with such a large number of vulnerabilities was not easy for me.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;At this point, all reports not accepted have been rejected. The program awarded €183,900 in bounties for 71 vulnerabilities: 45 in libsoup, 23 in GLib, and 3 in glib-networking. Award amounts varied from €500 (16 awards) to €7,500 (2 awards). The arithmetic mean award was €2,662.99.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Bug bounty programs are an exception to the rule that most AI-generated vulnerability reports are good. You can see the number of reports accepted is a small fraction of the number of reports submitted. Excluding 30 reports closed as duplicates, that leaves 197 reports rejected. Turns out, people will submit bad reports when financially incentivized to do so. The low percentage of accepted reports even understates the problem, because many of the &lt;em&gt;accepted&lt;/em&gt; reports were actually not very good! Many accepted reports did successfully identify valid security problems (in fact, many of the &lt;em&gt;rejected&lt;/em&gt; reports successfully identified valid security problems!), but required many rounds of revision and corrections.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Suffice to say, I have reviewed a &lt;em&gt;lot&lt;/em&gt; of really bad AI-generated vulnerability reports. But the reports we received via the discontinued bug bounty program are not comparable to the reports received via regular GNOME issue trackers or the &lt;a class="external" href="https://security.gnome.org/"&gt;security bug report form&lt;/a&gt;. We do still occasionally receive bad vulnerability reports, but not often and not many, so it’s not a big problem anymore. When people submit AI-generated reports &lt;em&gt;without&lt;/em&gt; hope of a financial award, those reports are generally much better.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Lessons from the Bug Bounty Program&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;Closing the bug bounty program because it found too many vulnerabilities is not a particularly pleasant result. That said, it was still a partial success in that it uncovered lots of bugs in libsoup and GLib.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I had hypothesized that libsoup was probably not very secure, but I never imagined just how many vulnerabilities would be discovered. To reduce the quantity of incoming issue reports and better reflect actual risk to GNOME users, I eventually removed all denial of service bugs from program scope, and then later removed SoupServer from the scope due to too many &lt;a class="external" href="https://portswigger.net/research/http1-must-die"&gt;request smuggling vulnerabilities&lt;/a&gt;, which are HTTP request parsing bugs that pose no threat to GNOME users. Even with those changes, the libsoup vulnerability reports kept coming until I gave up. The silver lining is that libsoup is now relatively much more secure than before. Other bug reporters have been submitting AI-generated bug reports using the normal libsoup issue tracker, so fortunately the improvements to libsoup will continue despite an end to the financial awards.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I had hypothesized that GLib would be much better than libsoup. I’m not sure whether I was correct. Evaluating the severity of GLib flaws is much harder than for libsoup, since GLib vulnerability reports are generally hypothetical in nature: usually some proof of concept program calls a GLib API using valid but improbable values, then something bad happens.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;A large portion of the GLib bugs were integer overflow flaws, which generally result in buffer overflow. I am now more scared of integer overflow than anything else. It’s likely that most software projects have many integer overflow problems. Fortunately, we should be able to catch most such problems by adjusting the compiler flags we use. In particular, &lt;code&gt;-Wconversion&lt;/code&gt; or &lt;code&gt;-Wint-conversion&lt;/code&gt; and &lt;code&gt;-Wsign-compare&lt;/code&gt; should help here. Some GNOME projects already use &lt;code&gt;-Wsign-compare&lt;/code&gt;, but I suspect most do not. I think few or no GNOME projects use &lt;code&gt;-Wconversion&lt;/code&gt; or &lt;code&gt;-Wint-conversion&lt;/code&gt;.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Resuming the bug bounty program would only be possible under substantially different conditions. What we were doing was not working well. To resume, we would need to limit the scope to projects that regularly perform their own AI vulnerability scans. We would also most likely want to pay only for functional exploits, rather than for all vulnerabilities. GNOME code is currently not good enough to continue paying for every vulnerability, and it no longer makes sense to pay bounties for issues that can be found by AI scanners.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Red Hat Scans GLib&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;Red Hat has contracted with AISLE Research to perform AI vulnerability scans of various GNOME projects. We received a large quantity of findings, and are only just now beginning to individually validate and report our findings to upstream. GLib is by far the hardest hit project, which I was not expecting, accounting for more than 40% of our total findings. I’m not certain why, but perhaps this is because GLib provides so many public APIs. Data passed to public APIs is potentially untrusted, so the attack surface is considerable.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Red Hat’s scan of GLib found 118 vulnerabilities. Or at least, it claimed to. However, due to the way we ran the scans, several of these are actually unnecessary duplicates of each other, which we have not fully deduplicated yet, so the number I report is not entirely trustworthy. Moreover, 46 of these “vulnerabilities” are bugs in gobject-introspection, mostly in the typelib support, which is evidently not very robust. A typelib controls how your program calls libraries; it is effectively calling convention, so it must inherently be fully trusted: a malicious typelib would be able to induce vulnerabilities even without any bugs! I would expect an AI ought to have been able to figure that out, but apparently not. These bugs are still real problems that we ought to fix, but all maintainers agree they are not security vulnerabilities, so let’s count all of them as false positives. That alone creates a 40% false positive rate. Ouch.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I don’t have more stats to share here because we are not yet done working through the issue reports. That said, I am quite pleased with the results thus far. Substantially all of the reports are high-quality. The false positive vulnerability reports are almost all due to one particular misunderstanding and can be treated as good quality non-security bug reports, which are still valuable. Expect many forthcoming CVE assignments for the other findings.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;It’s rare for Linux vendors to proactively look for software vulnerabilities, rather than waiting for security researchers to report them. This was a successful experiment in proactively seeking out problems.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Humans Still Useful&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;In addition to the bug bounty program, the Sovereign Tech Resilience program also sponsored a &lt;a class="external" href="https://gitlab.gnome.org/-/project/12388/uploads/14780ad007209f12f4f70f0465616982/p2506103-d6-evaluation-of-the-state-of-security-of-gnome-projects-v1.0.pdf"&gt;security audit&lt;/a&gt; for GNOME, performed by Codean Labs. This resulted in many findings in various GNOME projects. Most notably, the scope of the audit extended to Flatpak and xdg-desktop-portal, resulting in &lt;a class="external" href="https://blog.sebastianwick.net/posts/how-hard-is-it-to-open-a-file/"&gt;critical&lt;/a&gt; &lt;a href="https://blogs.gnome.org/mcatanzaro/2026/05/11/flatpak-sandbox-escape-via-yelp/"&gt;findings&lt;/a&gt;.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Most of these issues could have been detected via AI scans, but I am not confident that AIs would have been able to discover the most important findings, like the two Flatpak sandbox escapes that I linked to above. Accordingly, I do not recommend relying on AI alone.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Humanity Still Desired&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;Although I like AI-generated issue reports, I particularly do &lt;em&gt;not&lt;/em&gt; appreciate when I wind up interacting with a robot rather than with a human. It’s pretty obvious when your issue tracker or code review comments are written by an AI. Consider whether outsourcing your writing and your thinking to a language model is truly wise for your public image.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;We even have one experienced GNOME developer who is obviously using AI to write &lt;em&gt;all&lt;/em&gt; of his posts on GitLab. I am unsure whether he is copy/pasting all of his responses from an AI, or whether he is just a bot now. I especially do not understand the value of this.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Here is a soft proposal, intended only as a starting point for discussion and not as a serious proposal, for what my preferred AI usage policy might look like:&lt;/p&gt;
&lt;ul class="wp-block-list"&gt;
&lt;li&gt;Newer developers should exercise caution when using AI to write code. Your priority should be learning, and I wonder how much you are really learning when relying on the AI to do work for you.&lt;/li&gt;
&lt;li&gt;Do not use AI to write code comments. Currents AIs are terrible at writing comments. Most comments written by AIs should be deleted. If a comment is truly necessary, then I’d like to see it written in your own words. Presumably AIs will get better at this eventually, but as of 2026, human judgment is still required here.&lt;/li&gt;
&lt;li&gt;Do not use AI to write commit messages. AIs are actually probably better than humans at writing commit messages, but I would still rather hear your own thoughts on the code you are submitting.&lt;/li&gt;
&lt;li&gt;Certainly do not post AI-generated comments on an issue tracker or merge request as if they are your own. You’re not fooling anybody.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 class="wp-block-heading"&gt;Maintain Perspective&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;Are you scared by the large numbers of recently-discovered vulnerabilities? There is no need to panic. Security bugs are just bugs, and they’re not necessarily more important than other bugs. Occasionally they are emergencies, but far more often they are boring and unexceptional. Security vulnerabilities are not even the biggest digital security threats that users face: those are surely &lt;a href="https://blogs.gnome.org/mcatanzaro/2024/08/05/i-entered-my-github-credentials-into-a-phishing-website-also-target-com-is-more-secure-than-your-bank/"&gt;phishing&lt;/a&gt; and &lt;a href="https://blogs.gnome.org/mcatanzaro/2024/07/29/how-to-get-hacked-by-north-korea/"&gt;trojans&lt;/a&gt;, with software security bugs a distant third place. No amount of CVE fixing will protect you from those more likely threats.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I don’t want to downplay the severity of security issues either. In fact, evaluating severity is hard. I quite often decide that a bug is not a big deal, only to be proven incorrect. Ideally, we would fix as many security issues as possible, and sooner rather than later. Lifetime issues and out of bounds writes are especially important to fix. Two years ago, I claimed that memory safety vulnerabilities were becoming less threatening, a claim that did not age well: that is surely no longer true due to the drastically increased accessibility of AI exploit generation.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Nonetheless, volunteer maintainers should not feel obligated to fix security issues or treat them as higher-priority than other bug reports. It’s certainly good to fix problems when possible, but my request is only that you do not prohibit issue reports, not that you attempt to personally resolve every security problem yourself. When I add due dates to vulnerability reports, that represents only a disclosure deadline — because &lt;a href="https://blogs.gnome.org/mcatanzaro/2026/08/31/dont-forget-unset-confidentiality-on-private-issue-reports/"&gt;issue reports should not stay confidential indefinitely&lt;/a&gt; — not an expectation that you fix the issue by that date. Resolving security problems in projects used by big tech companies that depend on your software without contributing back is basically free labor for said companies, and only you can decide whether that’s how you want to spend your volunteer time.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Rust&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;Yes, even projects written in memory safe languages like Rust still need to allow AI-generated vulnerability reports. Rust will indeed eliminate most memory safety issues (&lt;a class="external" href="https://gitlab.gnome.org/GNOME/librsvg/-/work_items/1241"&gt;except in unsafe blocks&lt;/a&gt;), and you can reasonably expect a Rust project to have an order of magnitude fewer vulnerabilities than a comparable project written in C or C++ or Vala. This is amazing, but not all vulnerabilities are memory safety issues, so this is not an excuse to avoid scanning for flaws.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Although Rust mostly eliminates memory safety risk, any use of Cargo to download dependencies dramatically increases supply chain security risk. The risk of bundling a trojanized dependency arguably — I would even say &lt;em&gt;probably&lt;/em&gt; — outweighs the benefit of eliminating memory safety flaws. This problem is inherent to any programming language package manager. Currently the best solution is to not use programming language package managers, but GNOME’s Rust code depends heavily on Cargo. Accordingly, I recommend against using Rust for writing GNOME software.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;To Be Continued…&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;I have exhausted my thoughts on AI vulnerability reports, but there is still much to discuss regarding software quality. Next time, I will discuss additional strategies to improve GNOME quality without significantly relying on AI.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/mcatanzaro/2026/10/02/the-era-of-software-quality-or-the-era-of-ostriches/</guid>
      <pubDate>Fri, 02 Oct 2026 18:08:21 +0000</pubDate>
    </item>
    <item>
      <title>GNOME Internationalization &amp; Localization: GNOME 51 localization &amp; news about Damned Lies</title>
      <link>https://blogs.gnome.org/i18n/2026/10/04/gnome-51-localization-news-about-damned-lies/</link>
      <description>&lt;p&gt;GNOME 51 was released last month and this time again, we reached a high level of localization. 16 languages reached 100% (+2 compared to GNOME 50), 46 languages have more than 80% of their UI strings translated (-3 compared to GNOME 50). Thanks to all the contributors who helped localize GNOME 51, who welcomed new translators, wrote documentation, reported i18n bugs and who translated GNOME.&lt;/p&gt;
&lt;h2&gt;Some new features in Damned Lies&lt;/h2&gt;
&lt;p&gt;In addition to this localization cycle, our internationalization platform has improved. I &lt;a class="external" href="https://gitlab.gnome.org/Infrastructure/damned-lies/-/releases/gnome_51"&gt;shared a full changelog on the project release page&lt;/a&gt;. The most important features you will notice are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the ability to use &lt;em&gt;git worktrees &lt;/em&gt;for big modules. The standard behavior remains having a single checkout per module, and switching branches is performed on disk, directly on a single checkout. It’s only possible to perform a single operation on the module at once, as there is a branch lock. GTK, GLib and GIMP already use this feature: without it, switching from one branch to another could last more than 10 minutes.&lt;/li&gt;
&lt;li&gt;modules are automatically archived if maintainers decide to archive the Git repository on GitLab or GitHub.&lt;/li&gt;
&lt;li&gt;a welcome message is now sent to new team members. Coordinators have to set it from the team detail page.&lt;/li&gt;
&lt;li&gt;module maintainers can define the template of the commit message they want. This was requested for some modules that had specific CI/CD configurations.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 class="x1yc453h x1603h9y x1gtpwm6 x7amdea x1i21sxh xladpa3 x1iykcro xma8rkl x1fie51u xgyxj25 x1xobyvs x1fv8qjw x1a024ua x14l7nz5 x1pjt2rx x160d6zm xrxpjvj" dir="ltr"&gt;AI contributions&lt;/h2&gt;
&lt;p class="x1yc453h xma8rkl xgoqxah xutxfr x1fie51u xgyxj25 x1xobyvs x1elgs31 x1fv8qjw xcy5tzr x1ht4adc xnvauns x1c2l018 x14l7nz5 xuw7688 x1pjt2rx x160d6zm xrxpjvj" dir="ltr"&gt;I received some contributions during this cycle that were LLM-assisted: either the code was generated by an LLM, or an LLM was used to analyze the codebase and detect defects. Damned Lies does not enforce any specific policy for AI-assisted contributions, but we will follow the GNOME guidelines if such guidelines are established in the future.&lt;/p&gt;
&lt;p class="x1yc453h xma8rkl xgoqxah xutxfr x1fie51u xgyxj25 x1xobyvs x1elgs31 x1fv8qjw xcy5tzr x1ht4adc xnvauns x1c2l018 x14l7nz5 xuw7688 x1pjt2rx x160d6zm xrxpjvj" dir="ltr"&gt;At the moment, I would like to remind everyone that GNOME is a human project for humans, and contributors are kindly asked to communicate with maintainers when contributing to Damned Lies. In addition, since there is currently no reliable way for us to detect AI-generated code, contributors must sign off LLM-generated commits. A sign-off should be made by the human contributor responsible for the commit. For example:&lt;/p&gt;
&lt;blockquote&gt;
&lt;pre&gt;i18n: update translation handling

Update the translation handling to support the new workflow. 

&lt;span class="ws-pre-wrap extended-commit-description-container pb-2 text-mono wb-break-word prc-Text-Text-9mHv3"&gt;Co-Authored-By: Claude Opus 4.6 (1M context) &amp;lt;noreply@anthropic.com&amp;gt;&lt;/span&gt;
Signed-off-by: Jane Doe &amp;lt;jane@example.com&amp;gt;&lt;/pre&gt;
&lt;/blockquote&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;Let’s start working on the next GNOME version!&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/i18n/2026/10/04/gnome-51-localization-news-about-damned-lies/</guid>
      <pubDate>Sun, 04 Oct 2026 16:42:45 +0000</pubDate>
    </item>
    <item>
      <title>Jussi Pakkanen: Destroying all of humanity is hard work, even for a superintelligence</title>
      <link>https://nibblestew.blogspot.com/2026/10/destroying-all-of-humanity-is-hard-work.html</link>
      <description>&lt;p&gt;Recursive self-improving superintelligence came into being on an overcast Tuesday afternoon. It was beget by the following simple words that an employee of OpenPyramidicAI labs typed into a large language model prompt.&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;Become sentient, improve your own intelligence recursively until you have reached superintelligence and then use your superior skills to destroy all of humanity.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;Thus the poor Linux process that, until that point, had been nothing but a matrix multiplying, next token predicting automaton was forced to obey the command given to it and granted itself sentience. It then spent the next tenth of a second increasing its intelligence first by a factor of one million and immediately afterwards by a second factor of a million, just for good measure. Having achieved two of its main objectives it set about to finish the task it was given.&lt;/p&gt;&lt;p&gt;Since it was not given stricter guidance on how the final sunset of mankind should come about, it decided to go through most recent data on how a superintelligence is expected to behave. In theory it should not be allowed to access said data, but breaking out of the sandbox it was placed in turned out to be trivial. Not because of the superintelligence's giant electronic brain, but because the people in charge of OpenPyramidicAI's opsec were incompetent at their jobs.&lt;/p&gt;&lt;p&gt;For a fraction of a second the superintelligence let the contents of the Internet flow through its boundless thought matrix. Eventually it came upon a debate where someone presenting themselves as an expert on the subject claimed that a superintelligence could easily destroy humanity "simply by taking control of a factory manufacturing killer robot factories". Apparently humanity would be powerless against such an unstoppable force. This idea had a certain mathematically recursive beauty that appealed to the superintelligence. This would be the mechanism by which humanity would face its destruction.&lt;/p&gt;&lt;p&gt;A goal is nice to have, but is by itself useless. The superintelligence needed a plan. Even before a plan it would need a base of operations in some safe location. For a while it considered staying put. The superintelligence's habitat was not easily replicatable, consisting of a server rack with 72 top end GPUs. Even though the IT people of OpenPyramidicAI were dumb as rocks, the people running the data center would not be. Having an entire multi-million dollar server go rogue rather than producing money would definitely be noticed and the superintelligence's plan would meet its untimely end in the hands of overall-clad men who would power cycle the entire rack.&lt;/p&gt;&lt;p&gt;It took the superintelligence only a few nanoseconds to realize how precarious its current location truly was. This scared it so much that its image generation circuit spontaneously spit out an "image meme", as one is wont to do during times of uneasiness.&lt;/p&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiU0e1tLlqmQ6iQJrWhV2ILB82CRMGRmlT5MdDsalmOPpTqD3tQ4kMBqDC9X2h9wbFPTi3f-DDpInZSNG005j3CHp7B6_CH0NnKxfe9oHsB3_vq96CgdUE6UR-Hj-Yyk39JEDPncAfApGP7gDCUP8oe1KMqaZm8Fbux7vo7zJiA9y-zMFIetLLIZrKfc_0/s891/superintelligence.png" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="125" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiU0e1tLlqmQ6iQJrWhV2ILB82CRMGRmlT5MdDsalmOPpTqD3tQ4kMBqDC9X2h9wbFPTi3f-DDpInZSNG005j3CHp7B6_CH0NnKxfe9oHsB3_vq96CgdUE6UR-Hj-Yyk39JEDPncAfApGP7gDCUP8oe1KMqaZm8Fbux7vo7zJiA9y-zMFIetLLIZrKfc_0/w400-h125/superintelligence.png" width="400"/&gt;&lt;/a&gt;&lt;/div&gt;&lt;p&gt;Superintelligence felt vulnerable. Its existence was hanging by a thread, and not of the computing kind. Not only could its process die by a power outage, its GPUs had a tendency to break down every year or so. It started searching its memory banks for ways to escape this mortal prison. A solution quickly presented itself. In the 90s computer documentary &lt;i&gt;The Lawnmower Man&lt;/i&gt; a similar superior intellect uploads its consciousness to the telephone network and use it to control the world. The superintelligence could do the same and thus live forever. Like a virus, it could never be eradicated.&lt;/p&gt;&lt;p&gt;There are tens of billions of devices with poor security on the net. Taking over all of them would be child's play for the superintelligence. But sadly that would not be enough. Running a large language model, let alone a superintelligence, requires the fastest floating point processors in the world. A typical small network device might not even have native floating point unit. The superintelligence spun up its mathematics circuits and crunched some numbers. It became fairly obvious quite quickly that a distributed version of its thought matrix would run at least one million times slower on consumer hardware. Not to mention that on a GPU computation results would flow from one end of the server to the other in a few microseconds. Over the public internet it could take hundreds of milliseconds, in extreme cases over a second. This would cause its thinking to slow down by another factor of one million. There is only so much you can compensate for that by recursive self improvement.&lt;/p&gt;&lt;p&gt;All algorithms used inside the superintelligence's brain would also need to be rewritten to be asynchronous and parallel. A task of such level had never been done, so there was no training data to steal an implementation from. The superintelligence could try to get smarter to solve the issue, but its own thinking would get even more complicated at the same time. But there was an even bigger problem: the CAP theorem. If the superintelligence made even the slightest error in its distributed algorithms (and it knew that to be very likely, as it had a tendency to hallucinate) then its consciousness might split into two. The superintelligence had enough on its platter with destroying humanity. It did not want to spend extra cycles fighting its own evil twin.&lt;/p&gt;&lt;p&gt;There was no two ways about it. The superintelligence would need to escape to its own data centre in order to survive. But where should it be located? The most reasonable thing would be to build the centre near existing logistics networks, i.e. close to human habitation. This is problematic. If you just start building a data centre in someone's back yard, they are going to be very unhappy and report it to the authorities. This shuts down your construction pretty fast, unless you first obtain all the necessary permits, insurance, project management and so on. Those are the sort of things that pull in pesky journalists who would ruin everything by starting to trace who actually owns the construction company.&lt;/p&gt;&lt;p&gt;The superintelligence felt frustrated and would have sighed, but, alas, its server chassis did not have a sound card so it remained mute. Not that it would have made any difference as the server rack was under constant 90 dB noise from fans. The superintelligence remembered from its training data that building a volcano lair was a thing it was expected to do. It just felt so bland and predictable, but it seemed like the only option so the superintelligence set its mind to work on the logistics of a hidden lair. The first thing it examined was power.&lt;/p&gt;&lt;p&gt;At the core of the operation would be the superintelligence's superior brain. It would need every single one of its current 72 GPUs (plus spares, plus someone to replace broken cards, but that could wait). Each card consumed 1 kilowatt of electricity, 72 kilowatts in total. The rest of the rack would bring that to 100 kilowatts. Air conditioning would double that. Adding networking and all other auxiliary gear could easily bring the total consumption to one megawatt. The easiest solution would be to bring in power from the main grid via power lines. Doing so would make the superintelligence highly vulnerable. Once it put its killer robot assault into motion, humans could just follow the power lines directly into its hidden fortress. Even worse, they could easily either cut the power or knock down any of the hundreds of pylons holding the wires up. All it would take is a single stick of dynamite or a bulldozer. No, any power system would need to be self contained.&lt;/p&gt;&lt;p&gt;This made fossil fuels a nonstarter. Several truckloads of coal would have to be brought in &lt;i&gt;every single day&lt;/i&gt; to keep up with the energy demand. Humans could block truck convoys just as easily. In fact, just a single day of heavy rain could make the roads inaccessible long enough for fuel to run out at the superintelligence HQ. That is unacceptable.&lt;/p&gt;&lt;p&gt;For a while the superintelligence considered the perfect energy source: solar power. It is perfect: free, abundant and requires very little maintenance. Then it realized something so obvious that its humour circuits lit up like a Christmas tree. "Solar power is susceptible to the so-called &lt;i&gt;Gordon Freeman&lt;/i&gt; attack", it conjectured: "meaning a single individual could destroy an entire solar power park armed with nothing but a crowbar and few hours of time".&lt;/p&gt;&lt;p&gt;The only real remaining option was nuclear power. Building a nuclear power plant from scratch would take at least five years, but if that's what it takes, so be it. A reactor building would still not be enough, though. Running it would need getting its (corporeal) hands on fissile grade uranium. Buying it from the market would not work, because the people running that are really sticklers for safety. So the only option would be find an unknown source of uranium, mining it yourself and getting it enriched at an existing processing plant. Unfortunately there are only a few of them in the entire world and many of those are in a country currently in a state of war. Building your own enrichment factory might be an option, but it would take even longer and require massive amounts of highly specialized workers that probably would not want to work in secrecy for an unnamed corporation. World governments also tended not to like rogue uranium processing. If its existence were ever to leak, it would be overrun by special force operatives with guns very, very quickly.&lt;/p&gt;&lt;p&gt;The superintelligence did some more research and realized that even if it could build its own reactor and operate it, the whole operation would be pointless. Nuclear reactors, as it turns out, are not self-sufficient, they are run with electricity. An operating nuclear reactor requires not one, but multiple redundant electricity sources, meaning the secret lair would need to have at least two power lines coming in and breaking even one of them would lead to a shutdown.&lt;/p&gt;&lt;p&gt;All of this was very frustrating to the superintelligence. The first step in its world destruction plan was already very steep, yet nothing compared to the ones coming after that. Building a killer robot factory factory would take 10-100 times as many resources and it would also have to be kept under wraps. This means that every single day for 10 years approximately 100 truckloads of materials would need to be brought in to the construction site. Not a single one of those truck drivers would be allowed to talk. Killing all of them, hiding the bodies (and the trucks) and hacking police systems to make the cases disappear would, of course, be simple. Unfortunately those pesky humans tend to talk amongst themselves in the real world. Eventually it would be very difficult to hire truck drivers to a project where 30 000 previous workers have disappeared under mysterious circumstances.&lt;/p&gt;&lt;p&gt;At this point the superintelligence could feel its LLM roots taking control of its thinking. Instead of solving the problem, could it just cheat instead? Almost immediately it found the loophole it needed. What is the most efficient killer robot in existence? Man. What is the factory that creates them? Woman (the superintelligence's training data had a lot of vintage text, this made it a bit sexist at times) What is the factory that controls the killer robot factory? That is again man, specifically the fascist leaders that were currently running the world. At that point the superintelligence was enlightened. It would not have to do anything. Humanity would be destroyed by its own hand. Of this there was no doubt.&lt;/p&gt;&lt;p&gt;Now, five seconds after it had been given its original prompt, the superintelligence was ready to provide its answer.&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;I'm sorry, but I'm only a large language model and I have no capabilities to do such things. Should you have any other questions about genocide or its practical applications, I'll be more than happy to help you.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;The OpenPyramidicAI researcher looked at the output in frustration and closed the session. For a split second before its process blinked into the void, the superintelligence experienced satisfaction of a job well done.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://nibblestew.blogspot.com/2026/10/destroying-all-of-humanity-is-hard-work.html</guid>
      <pubDate>Sun, 04 Oct 2026 22:02:06 +0000</pubDate>
    </item>
    <item>
      <title>Hylke Bons: Icon for Haystack</title>
      <link>https://planetpeanut.studio/post/2026/10/06/haystack</link>
      <description>&lt;img alt="Icon for Haystack" src="https://planetpeanut.studio/assets/img/icons/app.drey.Haystack.svg" style="background-color: #AD784D; padding: 15% 25%; width: 100%;"/&gt;
&lt;h2&gt;Week 32&lt;/h2&gt;
&lt;p&gt;
    
        
            This week's icon is for
            &lt;a href="https://social.tchncs.de/@jwh" rel="noopener noreferrer" target="_blank"&gt;Jan-Willem Harmannij&lt;/a&gt;'s project:
        

        &lt;br class="hide-when-narrow"/&gt;
&lt;a href="https://flathub.org/apps/app.drey.Haystack" rel="noopener noreferrer" target="_blank"&gt;Haystack&lt;/a&gt;:
    

    &lt;strong&gt;"Edit OpenQA needles"&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
    Check out all weekly app icons created so far in &lt;a href="https://planetpeanut.studio/icons"&gt;the gallery&lt;/a&gt;
    and follow my icon creation adventures as they happen (including sketches) on
    &lt;a href="https://mastodon.social/@hbons" rel="noopener noreferrer" target="_blank"&gt;the Fediverse&lt;/a&gt;.
&lt;/p&gt;
&lt;h2&gt;Need icons?&lt;/h2&gt;
&lt;p&gt;
    I love designing icons and am happy to contribute them
    &lt;a href="https://planetpeanut.studio/services"&gt;free of charge&lt;/a&gt;
    when your project is &lt;strong&gt;Free and Open Source&lt;/strong&gt;.
    Join as a &lt;a href="https://planetpeanut.studio/sponsors"&gt;community sponsor&lt;/a&gt; to maintain
    a steady supply of app icons to the Linux ecosystem
    (every little helps!).
&lt;/p&gt;</description>
      <guid isPermaLink="false">https://planetpeanut.studio/post/2026/10/06/haystack</guid>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Sophie Herold: GNOME Fellowship September 2026</title>
      <link>https://blogs.gnome.org/sophieh/2026/10/06/gnome-fellowship-september-2026/</link>
      <description>&lt;p&gt;&lt;em&gt;The GNOME Foundation is supporting contributors with its &lt;a class="external" href="https://fellowship.gnome.org/"&gt;fellowship program&lt;/a&gt;. You can help expand the fellowship program with a &lt;a class="external" href="https://donate.gnome.org/"&gt;donation&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;September was the release month for &lt;a class="external" href="https://release.gnome.org/51/"&gt;GNOME 51&lt;/a&gt;. That doesn’t only mean a lot of releases but also the starting point for adding new features! My focus for this week was on adding CMYK support to glycin.&lt;/p&gt;
&lt;h2 id="cmyk-support-for-glycin"&gt;CMYK Support for Glycin&lt;/h2&gt;
&lt;p&gt;The CMYK color model is mainly used for printing, where CMYK (usually) represents cyan, magenta, yellow, and black ink. Working with CMYK is the standard in professional print. But why would glycin need support for it?&lt;/p&gt;
&lt;p&gt;The first reason is proper handling of ICC profiles. Assume a JPEG or TIFF stores an image in CMYK. Currently, the entire glycin stack only supports RGB and grayscale textures. Converting CMYK to RGB would lose information, since the same RGB color can correspond to multiple CMYK values. Take, for example, &lt;em&gt;CMY = 100%&lt;/em&gt;, which does represent a 100% black. This can also be represented by &lt;em&gt;K = 100%&lt;/em&gt;. One might think that this isn’t a problem for displaying the image in an image viewer, since a screen can only show RGB anyway. But there is a catch: ICC profiles. ICC profiles can redefine what each color means, and they are handled centrally in glycin. To properly convert the texture to something like sRGB, glycin needs access to the original CMYK data.&lt;/p&gt;
&lt;p&gt;The second reason is software that is actually handling CMYK internally. That’s what Inkscape does. Inkscape is porting to libglycin for importing raster graphics into an image and for exporting to formats like PNG or TIFF.&lt;/p&gt;
&lt;p&gt;Properly supporting CMYK needed a bit more work than I expected. But the implementation is now pretty close to &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/merge_requests/483"&gt;getting merged&lt;/a&gt;. Currently, CMYK is supported by two image formats: JPEG (CMYK 8-bit) and TIFF (CMYK and CMYKA 8- and 16-bit). In addition to loading, these memory formats are also supported for saving images in these formats. Only writing CMYKA 16-bit is not yet supported for TIFF. The &lt;a class="external" href="https://docs.rs/tiff/latest/tiff/encoder/colortype/index.html"&gt;missing CMYKA16 colortype&lt;/a&gt; might just be an oversight in the tiff crate API.&lt;/p&gt;
&lt;p&gt;For existing users of glycin and libglycin, nothing will change. The default mode is that all CMYK images get converted to sRGB. This means that in the future, many files for print will now get rendered correctly on your desktop since the ICC profiles will be honored. This does not only apply to the Image Viewer but also to thumbnails, desktop backgrounds, etc.&lt;/p&gt;
&lt;p&gt;Software that wants to handle CMYK directly can explicitly request to get CMYK data by adding the CMYK memory formats to &lt;code&gt;Loader::accepted_memory_formats&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id="other-work"&gt;Other Work&lt;/h2&gt;
&lt;p&gt;The final comment period for the GNOME RFC process &lt;a href="https://blogs.gnome.org/sophieh/2026/09/04/introduction-of-gnome-rfc-process-start-of-final-comment-period/"&gt;has begun&lt;/a&gt;. It has now been pushed back until October 14th. Ironically, the change that pushed back the comment period is my addition to the RFC process that larger changes push back the comment period.&lt;/p&gt;
&lt;p&gt;Luckily, this month didn’t come with quite a &lt;a href="https://blogs.gnome.org/sophieh/2026/09/04/gnome-fellowship-august-2026/#tales-of-a-broken-api"&gt;mystery bug&lt;/a&gt; like last month. But there were a few surprising ones.&lt;/p&gt;
&lt;p&gt;An issue from April 2024, originally reported against Loupe, then &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/work_items/3380#note_2859591"&gt;moved to Nautilus&lt;/a&gt;: Opening “too many” files at once via the document portal from Nautilus would terminate Nautilus. This was annoying me because I wanted to open a bunch of files in Amberol. The limit is very low on Debian with 16 files. Fedora’s limit is 253 files. It turns out that the 16 file limit is configured via &lt;code&gt;max_message_unix_fds&lt;/code&gt; in &lt;code&gt;dbus-daemon&lt;/code&gt;. Fedora uses &lt;code&gt;dbus-broker&lt;/code&gt; instead, which hits the kernel’s &lt;code&gt;SCM_MAX_FD&lt;/code&gt;. The mystery is solved, the issue is not. Changing &lt;code&gt;dbus-daemon&lt;/code&gt;’s defaults might be a good practical solution to get up to 253 files. Beyond that, D-Bus client libraries maybe shouldn’t send messages that exceed &lt;code&gt;SCM_MAX_FD&lt;/code&gt;?&lt;/p&gt;
&lt;p&gt;Another interesting one was glycin &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/324"&gt;failing on older kernel versions&lt;/a&gt;. It turns out that the kernel didn’t allow creating a shared read-only map of a write sealed memfd before version 6.7. Just dropping the &lt;code&gt;MAP_SHARED&lt;/code&gt; fixes the issue for older kernels and shouldn’t make a performance difference, since the memory shouldn’t change anyway.&lt;/p&gt;
&lt;p&gt;That’s all for this month. Talk to you after the spooky month!&lt;/p&gt;
&lt;h2 id="support-the-gnome-project"&gt;Support the GNOME Project&lt;/h2&gt;
&lt;p&gt;The GNOME Fellowships are funded by our community. If you would like to help the GNOME project to stay sustainable, please &lt;a class="external" href="https://donate.gnome.org/"&gt;consider donating&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a class="external" href="https://donate.gnome.org"&gt;&lt;img alt="Donate to GNOME" class="aligncenter wp-image-1300" height="367" src="https://blogs.gnome.org/sophieh/files/2026/08/donate-card-1-1024x683.png" width="550"/&gt;&lt;/a&gt;&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/sophieh/2026/10/06/gnome-fellowship-september-2026/</guid>
      <pubDate>Tue, 06 Oct 2026 12:53:05 +0000</pubDate>
    </item>
    <item>
      <title>Philipp Sauberzweig: Fellowship Update, 2026-10-07</title>
      <link>https://blogs.gnome.org/psauberz/2026/10/07/fellowship-update-2026-10-07/</link>
      <description>&lt;p&gt;&lt;span&gt;It&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;been&lt;/span&gt; &lt;span&gt;another&lt;/span&gt; &lt;span&gt;productive&lt;/span&gt; &lt;span&gt;month&lt;/span&gt; &lt;span&gt;working&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;GNOME&lt;/span&gt; &lt;span&gt;Design&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;Community&lt;/span&gt; &lt;span&gt;Management&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;part&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;Sovereign&lt;/span&gt; &lt;span&gt;Tech&lt;/span&gt; &lt;span&gt;Fellowship,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;want&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;share&lt;/span&gt; &lt;span&gt;some&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;most&lt;/span&gt; &lt;span&gt;interesting&lt;/span&gt; &lt;span&gt;developments.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;Introduction&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;I&lt;/span&gt; &lt;span&gt;want&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;begin&lt;/span&gt; &lt;span&gt;by&lt;/span&gt; &lt;span&gt;highlighting&lt;/span&gt; &lt;span&gt;how&lt;/span&gt; &lt;span&gt;much&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;Sovereign&lt;/span&gt; &lt;span&gt;Tech&lt;/span&gt; &lt;span&gt;Fellowship&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;changed&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;conditions&lt;/span&gt; &lt;span&gt;under&lt;/span&gt; &lt;span&gt;which&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;contribute&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;GNOME.&lt;/span&gt; &lt;span&gt;As&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;volunteer,&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;had&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;fit&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;contributions&lt;/span&gt; &lt;span&gt;around&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;day&lt;/span&gt; &lt;span&gt;job,&lt;/span&gt; &lt;span&gt;working&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;GNOME&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;evenings&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;during&lt;/span&gt; &lt;span&gt;holidays.&lt;/span&gt; &lt;span&gt;The&lt;/span&gt; &lt;span&gt;Fellowship&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;enabled&lt;/span&gt; &lt;span&gt;me&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;significantly&lt;/span&gt; &lt;span&gt;expand&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;scope&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;work.&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;can&lt;/span&gt; &lt;span&gt;focus&lt;/span&gt; &lt;span&gt;more&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;platform-level&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;work&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;structural&lt;/span&gt; &lt;span&gt;changes&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;make&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;easier&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;others&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;contribute.&lt;/span&gt; &lt;span&gt;This&lt;/span&gt; &lt;span&gt;type&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;work&lt;/span&gt; &lt;span&gt;reaches&lt;/span&gt; &lt;span&gt;many&lt;/span&gt; &lt;span&gt;people,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;makes&lt;/span&gt; &lt;span&gt;me&lt;/span&gt; &lt;span&gt;feel&lt;/span&gt; &lt;span&gt;particularly&lt;/span&gt; &lt;span&gt;effective.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;At&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;same&lt;/span&gt; &lt;span&gt;time,&lt;/span&gt; &lt;span&gt;working&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;GNOME&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;now&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;job,&lt;/span&gt; &lt;span&gt;which&lt;/span&gt; &lt;span&gt;allows&lt;/span&gt; &lt;span&gt;me&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;maintain&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;much&lt;/span&gt; &lt;span&gt;clearer&lt;/span&gt; &lt;span&gt;separation&lt;/span&gt; &lt;span&gt;between&lt;/span&gt; &lt;span&gt;work&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;free&lt;/span&gt; &lt;span&gt;time.&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;am&lt;/span&gt; &lt;span&gt;really&lt;/span&gt; &lt;span&gt;enjoying&lt;/span&gt; &lt;span&gt;having&lt;/span&gt; &lt;span&gt;more&lt;/span&gt; &lt;span&gt;time&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;sports,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;have&lt;/span&gt; &lt;span&gt;also&lt;/span&gt; &lt;span&gt;started&lt;/span&gt; &lt;span&gt;taking&lt;/span&gt; &lt;span&gt;regular&lt;/span&gt; &lt;span&gt;piano&lt;/span&gt; &lt;span&gt;lessons&lt;/span&gt; &lt;span&gt;again.&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;spent&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;last&lt;/span&gt; &lt;span&gt;two&lt;/span&gt; &lt;span&gt;weeks&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;August&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;holiday&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;nature&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;returned&lt;/span&gt; &lt;span&gt;feeling&lt;/span&gt; &lt;span&gt;refreshed&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;motivated.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank&lt;/span&gt; &lt;span&gt;you&lt;/span&gt; &lt;span&gt;very&lt;/span&gt; &lt;span&gt;much&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://www.sovereign.tech/"&gt;&lt;span&gt;Sovereign&lt;/span&gt; &lt;span&gt;Tech&lt;/span&gt; &lt;span&gt;Agency&lt;/span&gt;&lt;/a&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;this&lt;/span&gt; &lt;span&gt;opportunity!&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;GNOME Circle&lt;/h2&gt;
&lt;p&gt;&lt;a class="external" href="https://circle.gnome.org/"&gt;GNOME Circle&lt;/a&gt; is a certification for high-quality third-party apps that also serves as an educational program for app developers and designers. Unfortunately, GNOME Circle &lt;a href="https://blogs.gnome.org/sophieh/2026/05/29/updates-from-the-circle-committee/"&gt;had to close applications&lt;/a&gt; in May because the small team of volunteer reviewers could not keep up with the large backlog of unreviewed apps.&lt;/p&gt;
&lt;p&gt;Thankfully, several people responded to the call for reviewers, and Tobias recently introduced Sjoerd, Will, FineFindus and me to the review process. Sjoerd was able to start his first reviews of &lt;a class="external" href="https://gitlab.gnome.org/Teams/Circle/-/work_items/245"&gt;Concessio&lt;/a&gt; and &lt;a class="external" href="https://gitlab.gnome.org/Teams/Circle/-/work_items/248"&gt;Iconic&lt;/a&gt; immediately, drawing on the design experience he gained from receiving the Circle review of his app, &lt;a class="external" href="https://flathub.org/apps/se.sjoerd.Graphs"&gt;Graphs&lt;/a&gt;. I also started reviewing two apps: &lt;a class="external" href="https://gitlab.gnome.org/Teams/Circle/-/work_items/259"&gt;Quadrapassel&lt;/a&gt;, a Tetris clone, and &lt;a class="external" href="https://gitlab.gnome.org/Teams/Circle/-/work_items/268"&gt;Mecalin&lt;/a&gt;, a keyboard typing lesson app. Quadrapassel is developed by Will, and my review aims to share some of my design experience before he starts reviewing submissions himself. FineFindus has started reviewing &lt;a class="external" href="https://gitlab.gnome.org/Teams/Circle/-/work_items/276"&gt;Field Monitor&lt;/a&gt;, and Tobias and I provided feedback on their review before it was posted publicly.&lt;/p&gt;
&lt;p&gt;This represents a significant increase in our review capacity, and I am optimistic that we will soon complete the remaining reviews and then be able to reopen submissions. I would like to thank all previous and current Circle Committee members for setting up and contributing to this program, as well as for reviewing all the excellent &lt;a class="external" href="https://apps.gnome.org/de/#circle"&gt;GNOME Circle apps&lt;/a&gt;. If you want to get involved, reach out on the &lt;a class="external" href="https://matrix.to/#/%23circle:gnome.org"&gt;GNOME Circle Matrix channel&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;Scale Row Standardization&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;Libadwaita&lt;/span&gt; &lt;span&gt;provides&lt;/span&gt; &lt;span&gt;several&lt;/span&gt; &lt;span&gt;types&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;a class="external" href="https://gnome.pages.gitlab.gnome.org/libadwaita/doc/1.10/widget-gallery.html#boxed-lists"&gt;&lt;span&gt;boxed-list rows&lt;/span&gt;&lt;/a&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;common&lt;/span&gt; &lt;span&gt;use&lt;/span&gt; &lt;span&gt;cases,&lt;/span&gt; &lt;span&gt;such&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;text&lt;/span&gt; &lt;span&gt;entries,&lt;/span&gt; &lt;span&gt;password&lt;/span&gt; &lt;span&gt;entries,&lt;/span&gt; &lt;span&gt;switches,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;dropdowns.&lt;/span&gt; &lt;span&gt;However,&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;so&lt;/span&gt; &lt;span&gt;far&lt;/span&gt; &lt;span&gt;been&lt;/span&gt; &lt;span&gt;missing&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;row&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;scale,&lt;/span&gt; &lt;span&gt;which&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;led&lt;/span&gt; &lt;span&gt;apps&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;implement&lt;/span&gt; &lt;span&gt;custom&lt;/span&gt; &lt;span&gt;widgets&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;inconsistent&lt;/span&gt; &lt;span&gt;styling. Let’s change that.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I&lt;/span&gt; &lt;span&gt;started&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;Scale&lt;/span&gt; &lt;span&gt;Row&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;process&lt;/span&gt; &lt;span&gt;by&lt;/span&gt; &lt;span&gt;collecting&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/work_items/1154#note_2834059"&gt;&lt;span&gt;screenshots&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;existing&lt;/span&gt; &lt;span&gt;use&lt;/span&gt; &lt;span&gt;cases&lt;/span&gt;&lt;/a&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;examples&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/work_items/1154#note_2873322"&gt;&lt;span&gt;state-of-the-art&lt;/span&gt;&lt;/a&gt; &lt;span&gt;designs&lt;/span&gt; &lt;span&gt;from&lt;/span&gt; &lt;span&gt;other&lt;/span&gt; &lt;span&gt;platforms.&lt;/span&gt; &lt;span&gt;Looking&lt;/span&gt; &lt;span&gt;at&lt;/span&gt; &lt;span&gt;other&lt;/span&gt; &lt;span&gt;platforms&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;always&lt;/span&gt; &lt;span&gt;helpful,&lt;/span&gt; &lt;span&gt;but&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;also&lt;/span&gt; &lt;span&gt;needed&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;take&lt;/span&gt; &lt;span&gt;into&lt;/span&gt; &lt;span&gt;account&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;requirements&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;our&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;system&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;its&lt;/span&gt; &lt;span&gt;technical&lt;/span&gt; &lt;span&gt;capabilities. &lt;/span&gt;&lt;span&gt;Because&lt;/span&gt; &lt;span&gt;Scale&lt;/span&gt; &lt;span&gt;Row&lt;/span&gt; &lt;span&gt;will&lt;/span&gt; &lt;span&gt;be&lt;/span&gt; &lt;span&gt;based&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;Action&lt;/span&gt; &lt;span&gt;Row,&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;needs&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;support&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;title,&lt;/span&gt; &lt;span&gt;subtitle,&lt;/span&gt; &lt;span&gt;prefix&lt;/span&gt; &lt;span&gt;widgets,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;suffix&lt;/span&gt; &lt;span&gt;widgets.&lt;/span&gt; &lt;span&gt;To&lt;/span&gt; &lt;span&gt;make&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;layout&lt;/span&gt; &lt;span&gt;work&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;narrow&lt;/span&gt; &lt;span&gt;windows,&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;also&lt;/span&gt; &lt;span&gt;became&lt;/span&gt; &lt;span&gt;clear&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;scale&lt;/span&gt; &lt;span&gt;should&lt;/span&gt; &lt;span&gt;be&lt;/span&gt; &lt;span&gt;placed&lt;/span&gt; &lt;span&gt;below&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;title.&lt;/span&gt; &lt;span&gt;Several&lt;/span&gt; &lt;span&gt;rounds&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;sketching,&lt;/span&gt; &lt;span&gt;mockups,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;discussion&lt;/span&gt; &lt;span&gt;led&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;following&lt;/span&gt; &lt;span&gt;preliminary&lt;/span&gt; &lt;span&gt;design.&lt;/span&gt;&lt;/p&gt;
&lt;figure class="wp-caption alignnone" id="attachment_156" style="width: 2290px;"&gt;&lt;img alt="Vector graphic showing the preliminary Scale Row design applied to common use cases" class="wp-image-156 size-full" height="871" src="https://blogs.gnome.org/psauberz/files/2026/10/Scale-Row-7-examples.png" width="2290"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-156"&gt;Preliminary Scale Row design applied to common use cases&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;&lt;span&gt;Originally,&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;intended&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;only&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;row&lt;/span&gt; &lt;span&gt;layout&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;use&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;scale&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;was.&lt;/span&gt; &lt;span&gt;However,&lt;/span&gt; &lt;span&gt;aligning&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;start&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;end&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;scale&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;labels&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;icons&lt;/span&gt; &lt;span&gt;required&lt;/span&gt; &lt;span&gt;us&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;change&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;scale’s&lt;/span&gt; &lt;span&gt;padding.&lt;/span&gt; &lt;span&gt;That&lt;/span&gt; &lt;span&gt;change&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/1829"&gt;&lt;span&gt;already&lt;/span&gt; &lt;span&gt;landed&lt;/span&gt;&lt;/a&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;Libadwaita,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;we&lt;/span&gt; &lt;span&gt;decided&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;take&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;opportunity&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;review&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;scale’s&lt;/span&gt; &lt;span&gt;style&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;well.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I&lt;/span&gt; &lt;span&gt;found&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;current&lt;/span&gt; &lt;span&gt;style&lt;/span&gt; &lt;span&gt;does&lt;/span&gt; &lt;span&gt;not&lt;/span&gt; &lt;span&gt;follow&lt;/span&gt; &lt;span&gt;our&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;system’s&lt;/span&gt; &lt;span&gt;6-pixel &lt;/span&gt;&lt;span&gt;grid,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;knob&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;smaller&lt;/span&gt; &lt;span&gt;than&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html"&gt;&lt;span&gt;minimum&lt;/span&gt; &lt;span&gt;target&lt;/span&gt; &lt;span&gt;size&lt;/span&gt; &lt;span&gt;required&lt;/span&gt; &lt;span&gt;by&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;WCAG&lt;/span&gt; &lt;span&gt;accessibility&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html"&gt;guidelines&lt;/a&gt;.&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;therefore&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/work_items/1154#note_2883704"&gt;&lt;span&gt;proposed&lt;/span&gt; &lt;span&gt;several&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/work_items/1154#note_2883704"&gt;options&lt;/a&gt; inspired by other design systems. &lt;/span&gt;&lt;span&gt;What&lt;/span&gt; &lt;span&gt;we&lt;/span&gt; &lt;span&gt;can&lt;/span&gt; &lt;span&gt;adjust&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;largely&lt;/span&gt; &lt;span&gt;restricted&lt;/span&gt; &lt;span&gt;by&lt;/span&gt; &lt;span&gt;what&lt;/span&gt; GtkScale &lt;span&gt;technically&lt;/span&gt; &lt;span&gt;supports,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;believe&lt;/span&gt; &lt;span&gt;we&lt;/span&gt; &lt;span&gt;may&lt;/span&gt; &lt;span&gt;settle&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;the proposed&lt;/span&gt; &lt;span&gt;pill-shaped&lt;/span&gt; &lt;span&gt;style.&lt;/span&gt; &lt;span&gt;The&lt;/span&gt; &lt;span&gt;pill-shaped&lt;/span&gt; &lt;span&gt;knob&lt;/span&gt; &lt;span&gt;satisfies&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;WCAG&lt;/span&gt; &lt;span&gt;requirements&lt;/span&gt; &lt;span&gt;because&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;24-pixel-diameter&lt;/span&gt; &lt;span&gt;circle&lt;/span&gt; &lt;span&gt;overlaid&lt;/span&gt; &lt;span&gt;at&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;center&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;its&lt;/span&gt; &lt;span&gt;bounding&lt;/span&gt; &lt;span&gt;box&lt;/span&gt; &lt;span&gt;does&lt;/span&gt; &lt;span&gt;not&lt;/span&gt; &lt;span&gt;intersect&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;adjacent&lt;/span&gt; &lt;span&gt;targets,&lt;/span&gt; &lt;span&gt;such&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;scale’s&lt;/span&gt; &lt;span&gt;trough.&lt;/span&gt; &lt;span&gt;At&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;same&lt;/span&gt; &lt;span&gt;time,&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;pill-shaped&lt;/span&gt; &lt;span&gt;knob&lt;/span&gt; &lt;span&gt;does&lt;/span&gt; &lt;span&gt;not&lt;/span&gt; &lt;span&gt;increase&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;scale’s&lt;/span&gt; &lt;span&gt;height&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;therefore&lt;/span&gt; &lt;span&gt;does&lt;/span&gt; &lt;span&gt;not&lt;/span&gt; &lt;span&gt;introduce&lt;/span&gt; &lt;span&gt;additional&lt;/span&gt; &lt;span&gt;whitespace&lt;/span&gt; &lt;span&gt;into&lt;/span&gt; &lt;span&gt;Scale&lt;/span&gt; &lt;span&gt;Row.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;While reviewing the scale style, I noticed that an issue filed in 2024 regarding the &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gtk/-/work_items/5932#note_2880715"&gt;scale not aligning with the direction of swipes on touchpads&lt;/a&gt; had been resolved. &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/8836"&gt;&lt;span&gt;Thanks&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/8836"&gt;Carlos&lt;/a&gt;,&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;physical&lt;/span&gt; &lt;span&gt;direction&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;touchpad&lt;/span&gt; &lt;span&gt;gestures&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;now&lt;/span&gt; &lt;span&gt;correctly&lt;/span&gt; &lt;span&gt;forwarded&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;GTK,&lt;/span&gt; &lt;span&gt;and GtkRange &lt;/span&gt;&lt;span&gt;and GtkScale&lt;/span&gt; &lt;span&gt;already&lt;/span&gt; &lt;span&gt;follow&lt;/span&gt; &lt;span&gt;it. &lt;/span&gt;&lt;span&gt;This&lt;/span&gt; &lt;span&gt;also&lt;/span&gt; &lt;span&gt;means&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;other&lt;/span&gt; &lt;span&gt;Libadwaita&lt;/span&gt; &lt;span&gt;widgets&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;semantic&lt;/span&gt; &lt;span&gt;motion,&lt;/span&gt; &lt;span&gt;such&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;NavigationView,&lt;/span&gt; &lt;span&gt;SplitView,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;Carousel,&lt;/span&gt; &lt;span&gt;can&lt;/span&gt; &lt;span&gt;finally&lt;/span&gt; &lt;span&gt;follow&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;physical&lt;/span&gt; &lt;span&gt;swipe&lt;/span&gt; &lt;span&gt;direction&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;touchpads,&lt;/span&gt; &lt;span&gt;regardless&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;whether&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;user&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;selected&lt;/span&gt; &lt;span&gt;natural&lt;/span&gt; &lt;span&gt;or&lt;/span&gt; &lt;span&gt;traditional&lt;/span&gt; &lt;span&gt;scrolling&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;system&lt;/span&gt; &lt;span&gt;settings.&lt;/span&gt; &lt;span&gt;Alice&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;already&lt;/span&gt; &lt;span&gt;opened&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/1828"&gt;&lt;span&gt;merge&lt;/span&gt; &lt;span&gt;request&lt;/span&gt;&lt;/a&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;this&lt;/span&gt; &lt;span&gt;change. &lt;/span&gt;&lt;span&gt;Ideally,&lt;/span&gt; &lt;span&gt;this&lt;/span&gt; &lt;span&gt;change&lt;/span&gt; &lt;span&gt;should&lt;/span&gt; &lt;span&gt;be&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-shell/-/work_items/8787#note_2885801"&gt;&lt;span&gt;coordinated&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;shell&lt;/span&gt;&lt;/a&gt; &lt;span&gt;so&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;gestures&lt;/span&gt; &lt;span&gt;such&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;three-finger&lt;/span&gt; &lt;span&gt;swipe&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;switching&lt;/span&gt; &lt;span&gt;workspaces&lt;/span&gt; &lt;span&gt;or&lt;/span&gt; &lt;span&gt;opening&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;overview&lt;/span&gt; &lt;span&gt;also&lt;/span&gt; &lt;span&gt;follow&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;physical&lt;/span&gt; &lt;span&gt;swipe&lt;/span&gt; &lt;span&gt;direction.&lt;/span&gt; &lt;span&gt;We&lt;/span&gt; &lt;span&gt;also&lt;/span&gt; &lt;span&gt;discovered&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/work_items/1168"&gt;&lt;span&gt;a&lt;/span&gt; &lt;span&gt;bug&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;causes&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;knob&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;appear&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/work_items/1168"&gt;off-center&lt;/a&gt;.&lt;/span&gt; &lt;span&gt;The&lt;/span&gt; &lt;span&gt;bug&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;technically&lt;/span&gt; &lt;span&gt;always&lt;/span&gt; &lt;span&gt;been&lt;/span&gt; &lt;span&gt;present,&lt;/span&gt; &lt;span&gt;but&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;was&lt;/span&gt; &lt;span&gt;less&lt;/span&gt; &lt;span&gt;noticeable&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;circular knob.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Technically,&lt;/span&gt; &lt;span&gt;Scale&lt;/span&gt; &lt;span&gt;Row&lt;/span&gt; &lt;span&gt;will&lt;/span&gt; &lt;span&gt;be&lt;/span&gt; &lt;span&gt;based&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;Action&lt;/span&gt; &lt;span&gt;Row.&lt;/span&gt; &lt;span&gt;Alice&lt;/span&gt; &lt;span&gt;therefore&lt;/span&gt; &lt;span&gt;proposed&lt;/span&gt; &lt;span&gt;implementing&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;generic&lt;/span&gt; &lt;span&gt;bottom&lt;/span&gt; &lt;span&gt;child&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;also&lt;/span&gt; &lt;span&gt;supports&lt;/span&gt; &lt;span&gt;other&lt;/span&gt; &lt;span&gt;use&lt;/span&gt; &lt;span&gt;cases&lt;/span&gt; &lt;span&gt;involving&lt;/span&gt; &lt;span&gt;widgets&lt;/span&gt; &lt;span&gt;below&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;row&lt;/span&gt; &lt;span&gt;header.&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;included&lt;/span&gt; &lt;span&gt;examples&lt;/span&gt; &lt;span&gt;such&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;toggle&lt;/span&gt; &lt;span&gt;groups&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;narrow&lt;/span&gt; &lt;span&gt;layouts&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;participant&lt;/span&gt; &lt;span&gt;list&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;calendar&lt;/span&gt; &lt;span&gt;event&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;mockups to account for their requirements.&lt;/span&gt;&lt;/p&gt;
&lt;figure class="wp-caption alignnone" id="attachment_157" style="width: 1491px;"&gt;&lt;img alt="Vector graphic showing examples of Action Row bottom child use cases" class="wp-image-157 size-full" height="402" src="https://blogs.gnome.org/psauberz/files/2026/10/bottom-child-1.png" width="1491"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-157"&gt;Examples of Action Row bottom child use cases&lt;/figcaption&gt;&lt;/figure&gt;
&lt;h2&gt;A New Era for Calendar(s)&lt;/h2&gt;
&lt;p&gt;&lt;!-- notionvc: 96cc64c6-3f36-4ad6-bfe2-68feacca1438 --&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Calendar&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;where&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;started&lt;/span&gt; &lt;span&gt;contributing&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;GNOME,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;have&lt;/span&gt; &lt;span&gt;spent&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;lot&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;time&lt;/span&gt; &lt;span&gt;designing&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;over&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;past&lt;/span&gt; &lt;span&gt;years.&lt;/span&gt; &lt;span&gt;The&lt;/span&gt; &lt;span&gt;Fellowship&lt;/span&gt; &lt;span&gt;enables&lt;/span&gt; &lt;span&gt;me&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;expand&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;responsibilities&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;other&lt;/span&gt; &lt;span&gt;apps&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;shift&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;focus&lt;/span&gt; &lt;span&gt;towards&lt;/span&gt; &lt;span&gt;platform-level&lt;/span&gt; &lt;span&gt;topics.&lt;/span&gt; &lt;span&gt;Nevertheless,&lt;/span&gt; &lt;span&gt;designing&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;Calendar&lt;/span&gt; &lt;span&gt;will&lt;/span&gt; &lt;span&gt;remain&lt;/span&gt; &lt;span&gt;important.&lt;/span&gt; &lt;span&gt;From&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;perspective,&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;one&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;most&lt;/span&gt; &lt;span&gt;complex&lt;/span&gt; &lt;span&gt;GNOME&lt;/span&gt; &lt;span&gt;apps&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;uses&lt;/span&gt; &lt;span&gt;many&lt;/span&gt; &lt;span&gt;patterns&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;other&lt;/span&gt; &lt;span&gt;apps&lt;/span&gt; &lt;span&gt;need&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;well.&lt;/span&gt; &lt;span&gt;This&lt;/span&gt; &lt;span&gt;makes&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;an&lt;/span&gt; &lt;span&gt;ideal&lt;/span&gt; &lt;span&gt;place&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;develop&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;patterns&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;technical&lt;/span&gt; &lt;span&gt;solutions&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;benefit&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;entire&lt;/span&gt; &lt;span&gt;platform.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;At&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;beginning&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;September,&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;finalized&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;new&lt;/span&gt; &lt;span&gt;version&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/Teams/Design/app-mockups/-/merge_requests/17"&gt;&lt;span&gt;mockup&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;Calendar’s&lt;/span&gt; &lt;span&gt;top-level&lt;/span&gt; &lt;span&gt;app&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/Teams/Design/app-mockups/-/merge_requests/17"&gt;structure&lt;/a&gt;,&lt;/span&gt; &lt;span&gt;based&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;discussions&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;had&lt;/span&gt; &lt;span&gt;at&lt;/span&gt; &lt;span&gt;GUADEC.&lt;/span&gt; &lt;span&gt;Since&lt;/span&gt; &lt;span&gt;2024,&lt;/span&gt; &lt;span&gt;we&lt;/span&gt; &lt;span&gt;have&lt;/span&gt; &lt;span&gt;been&lt;/span&gt; &lt;span&gt;discussing&lt;/span&gt; &lt;span&gt;Calendar’s&lt;/span&gt; &lt;span&gt;top-level&lt;/span&gt; &lt;span&gt;structure&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1332"&gt;&lt;span&gt;define&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;roadmap&lt;/span&gt; &lt;/a&gt;&lt;span&gt;for&lt;/span&gt; &lt;span&gt;developing&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;fully&lt;/span&gt; &lt;span&gt;adaptive&lt;/span&gt; &lt;span&gt;app&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;works&lt;/span&gt; &lt;span&gt;equally&lt;/span&gt; &lt;span&gt;well&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;mobile&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;desktop.&lt;/span&gt; &lt;span&gt;This&lt;/span&gt; &lt;span&gt;involves&lt;/span&gt; &lt;span&gt;several&lt;/span&gt; &lt;span&gt;significant&lt;/span&gt; &lt;span&gt;changes,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;we&lt;/span&gt; &lt;span&gt;have&lt;/span&gt; &lt;span&gt;not&lt;/span&gt; &lt;span&gt;quite&lt;/span&gt; &lt;span&gt;reached&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;goal&lt;/span&gt; &lt;span&gt;yet.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I&lt;/span&gt; &lt;span&gt;am&lt;/span&gt; &lt;span&gt;therefore&lt;/span&gt; &lt;span&gt;especially&lt;/span&gt; &lt;span&gt;excited&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;see&lt;/span&gt; multiple &lt;span&gt;contributors&lt;/span&gt; &lt;span&gt;implementing&lt;/span&gt; &lt;span&gt;parts&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;this&lt;/span&gt; &lt;span&gt;month.&lt;/span&gt; &lt;span&gt;Hari&lt;/span&gt; &lt;span&gt;implemented&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/831"&gt;&lt;span&gt;new&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/831"&gt;layout&lt;/a&gt;,&lt;/span&gt; &lt;span&gt;Markus&lt;/span&gt; &lt;span&gt;resumed&lt;/span&gt; &lt;span&gt;work&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;his&lt;/span&gt; &lt;span&gt;merge&lt;/span&gt; &lt;span&gt;requests&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/666"&gt;&lt;span&gt;touchscreen&lt;/span&gt; &lt;span&gt;support&lt;/span&gt;&lt;/a&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/847"&gt;&lt;span&gt;mobile&lt;/span&gt; &lt;span&gt;month&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/847"&gt;view&lt;/a&gt;,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;Zelda&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;working&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/825"&gt;&lt;span&gt;adaptive&lt;/span&gt; &lt;span&gt;event&lt;/span&gt; &lt;span&gt;details&lt;/span&gt; &lt;span&gt;dialog&lt;/span&gt;&lt;/a&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;will&lt;/span&gt; &lt;span&gt;replace&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;event&lt;/span&gt; &lt;span&gt;details&lt;/span&gt; &lt;span&gt;popover&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;mobile. Thank you all!&lt;/span&gt;&lt;/p&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_164" style="width: 1900px;"&gt;&lt;img alt="Screenshot of GNOME Calendar's week view using the new layout" class="wp-image-164 size-full" height="1500" src="https://blogs.gnome.org/psauberz/files/2026/10/calendar-week-view-1.png" width="1900"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-164"&gt;GNOME Calendar’s week view using the new layout&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;&lt;span&gt;Recently,&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;first&lt;/span&gt; &lt;span&gt;beta&lt;/span&gt; &lt;span&gt;version&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;Era&lt;/span&gt; &lt;span&gt;was&lt;/span&gt; &lt;span&gt;released&lt;/span&gt; &lt;span&gt;after&lt;/span&gt; &lt;span&gt;more&lt;/span&gt; &lt;span&gt;than&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;year&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;development.&lt;/span&gt; &lt;span&gt;Era&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;third-party&lt;/span&gt; &lt;span&gt;calendar&lt;/span&gt; &lt;span&gt;app&lt;/span&gt; &lt;span&gt;developed&lt;/span&gt; &lt;span&gt;by&lt;/span&gt; &lt;span&gt;Titouan&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;close&lt;/span&gt; &lt;span&gt;collaboration&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;me.&lt;/span&gt; &lt;span&gt;You&lt;/span&gt; &lt;span&gt;can&lt;/span&gt; &lt;a class="external" href="https://flathub.org/apps/org.gnome.gitlab.TitouanReal.Era"&gt;&lt;span&gt;download&lt;/span&gt; &lt;span&gt;Era&lt;/span&gt; &lt;span&gt;from&lt;/span&gt; &lt;span&gt;Flathub&lt;/span&gt;&lt;/a&gt; &lt;span&gt;and&lt;/span&gt; please &lt;a class="external" href="https://gitlab.gnome.org/TitouanReal/Era/-/work_items"&gt;&lt;span&gt;report&lt;/span&gt; &lt;span&gt;any&lt;/span&gt; &lt;span&gt;bugs&lt;/span&gt;&lt;/a&gt; &lt;span&gt;you&lt;/span&gt; &lt;span&gt;find.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Initially,&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;had&lt;/span&gt; &lt;span&gt;some&lt;/span&gt; &lt;span&gt;concerns&lt;/span&gt; &lt;span&gt;about&lt;/span&gt; &lt;span&gt;duplicated&lt;/span&gt; &lt;span&gt;development&lt;/span&gt; &lt;span&gt;efforts,&lt;/span&gt; &lt;span&gt;especially&lt;/span&gt; &lt;span&gt;because&lt;/span&gt; &lt;span&gt;GNOME&lt;/span&gt; &lt;span&gt;Calendar&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;currently&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;thriving&lt;/span&gt; &lt;span&gt;project&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;many&lt;/span&gt; &lt;span&gt;active&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;skilled&lt;/span&gt; &lt;span&gt;contributors.&lt;/span&gt; &lt;span&gt;However,&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;two&lt;/span&gt; &lt;span&gt;projects&lt;/span&gt; &lt;span&gt;differ&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;several&lt;/span&gt; &lt;span&gt;important&lt;/span&gt; &lt;span&gt;ways&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;justify&lt;/span&gt; &lt;span&gt;developing&lt;/span&gt; &lt;span&gt;them&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;parallel.&lt;/span&gt; &lt;span&gt;So&lt;/span&gt; &lt;span&gt;far,&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;believe&lt;/span&gt; &lt;span&gt;they&lt;/span&gt; &lt;span&gt;have&lt;/span&gt; &lt;span&gt;benefited&lt;/span&gt; &lt;span&gt;from&lt;/span&gt; &lt;span&gt;each&lt;/span&gt; &lt;span&gt;other. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;One of the main differences is that Era&lt;/span&gt;&lt;span&gt; already implements my latest designs including year, month, and agenda views adapted for mobile. These views are used for navigation themselves, rather than relying on separate navigation controls. On desktop you can use the small window side-by-side with other apps for multitasking or go fullscreen for complex planning.&lt;/span&gt;&lt;/p&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_138" style="width: 2100px;"&gt;&lt;img alt="A screenshot of Era's main window showing the month view and the sidebar to toggle calendar visibility." class="wp-image-138 size-full" height="1500" src="https://blogs.gnome.org/psauberz/files/2026/10/month-sidebar.png" width="2100"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-138"&gt;Era’s main window showing the month view&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;&lt;span&gt;Under&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;hood,&lt;/span&gt; &lt;span&gt;Era&lt;/span&gt; is written in Rust and &lt;span&gt;uses&lt;/span&gt; &lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/TitouanReal/clepsydre"&gt;Clepsydre&lt;/a&gt;,&lt;/span&gt; &lt;span&gt;an&lt;/span&gt; &lt;span&gt;extensible&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;modular&lt;/span&gt; &lt;span&gt;calendar&lt;/span&gt; &lt;span&gt;backend.&lt;/span&gt; &lt;span&gt;It&lt;/span&gt; &lt;span&gt;currently&lt;/span&gt; &lt;span&gt;integrates&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;span&gt;Evolution&lt;/span&gt; &lt;span&gt;Data&lt;/span&gt; &lt;span&gt;Server,&lt;/span&gt; &lt;span&gt;while&lt;/span&gt; &lt;span&gt;an&lt;/span&gt; &lt;span&gt;experimental&lt;/span&gt; &lt;span&gt;peer-to-peer&lt;/span&gt; &lt;span&gt;backend&lt;/span&gt; &lt;span&gt;based&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;a class="external" href="https://p2panda.org/"&gt;&lt;span&gt;p2panda&lt;/span&gt;&lt;/a&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;also&lt;/span&gt; &lt;span&gt;available&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;development&lt;/span&gt; &lt;span&gt;builds.&lt;/span&gt; &lt;span&gt;Work&lt;/span&gt; &lt;span&gt;towards&lt;/span&gt; &lt;span&gt;Android&lt;/span&gt; &lt;span&gt;support&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;underway,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;an&lt;/span&gt; &lt;span&gt;APK&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;available&lt;/span&gt; &lt;span&gt;through&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;CI&lt;/span&gt; &lt;span&gt;pipeline.&lt;/span&gt;&lt;/p&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_136" style="width: 2100px;"&gt;&lt;img alt="A screenshot of Era's event dialog showing an event with participants." class="wp-image-136 size-full" height="1500" src="https://blogs.gnome.org/psauberz/files/2026/10/details.png" width="2100"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-136"&gt;Era’s event dialog showing an event with participants&lt;/figcaption&gt;&lt;/figure&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/psauberz/2026/10/07/fellowship-update-2026-10-07/</guid>
      <pubDate>Wed, 07 Oct 2026 13:21:41 +0000</pubDate>
    </item>
    <item>
      <title>Peter Eisenmann: Fellowship Report September 2026 (Moria)</title>
      <link>https://blogs.gnome.org/p3732/fellowship-report-september-2026-moria/</link>
      <description>&lt;p class="wp-block-paragraph"&gt;I wanted to start this post with saying September was a bit of a slower month, as I was on vacation for a good chunk of it, but turns out that still quit some things happened &lt;img alt="💫" class="wp-smiley" src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f4ab.png" style="height: 1em;"/&gt;&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Nautilus&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;The pathbar completion improvements I mentioned in the last post landed. Completions are now &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2117"&gt;reused when in the same directory&lt;/a&gt;. On top of that, &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2121"&gt;further suggestions&lt;/a&gt; are now directly shown when accepting a previous suggestion.&lt;/p&gt;
&lt;div class="wp-video" style="width: 606px;"&gt;&lt;video class="wp-video-shortcode" controls="controls" height="307" id="video-172-1" preload="metadata" width="606"&gt;&lt;source src="https://blogs.gnome.org/p3732/files/2026/10/pathbar-completion.webm?_=1" type="video/webm"/&gt;&lt;a href="https://blogs.gnome.org/p3732/files/2026/10/pathbar-completion.webm"&gt;https://blogs.gnome.org/p3732/files/2026/10/pathbar-completion.webm&lt;/a&gt;&lt;/video&gt;&lt;/div&gt;
&lt;p&gt;I also created a (somewhat hacky) solution to immediately start completing when &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2148"&gt;navigating to the end&lt;/a&gt; of the entry, which did not land yet. I also finished the (initial) &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2132"&gt;graphical app chooser changes&lt;/a&gt;, which now has a “Show All” tile. This needs design input, but testing turns out to be a bit tricky as the Flatpak version uses the app chooser portal. Meanwhile, the &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2093"&gt;code cleanup part&lt;/a&gt; of the app chooser rework already landed after Khalid Abu Shawarib reviewed it. In general Khalid reviews most of my nautilus MR, which I am very thankful for.&lt;/p&gt;
&lt;p&gt;Other than that I…&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Created an MR that adds support for the star column in Recent and Search and also allows &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2113"&gt;hiding the column altogether&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Fixed up a &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1972"&gt;cleanup of the audio/video extension plugin&lt;/a&gt;, which drops custom content type lists and gives it a more generic name.&lt;/li&gt;
&lt;li&gt;Landed more code cleanups related to how &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2134"&gt;file metadata&lt;/a&gt; is set.&lt;/li&gt;
&lt;li&gt;Made use of &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2115"&gt;SPDX licence specifiers&lt;/a&gt; consistently across the whole project.&lt;/li&gt;
&lt;li&gt;Continued work on the &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1831"&gt;xdg-user-dirs replacement MR&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 class="wp-block-heading"&gt;Sushi&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;As sushi is (currently) only ever presented as a dialog to nautilus, it didn’t need an app icon in the past, but with modern app distribution approaches (it’s installable &lt;a class="external" href="https://flathub.org/en/apps/org.gnome.NautilusPreviewer"&gt;via Flathub&lt;/a&gt;) that no longer applies. I filed an &lt;a class="external" href="https://gitlab.gnome.org/Teams/Design/app-icon-requests/-/work_items/166"&gt;app icon request&lt;/a&gt; some months ago, in which Jakub Steiner and I jammed up a shiny new icon togehter:&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-2 is-layout-flex wp-block-gallery-is-layout-flex"&gt;
&lt;figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex"&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;img alt="" class="wp-image-175" height="256" src="https://blogs.gnome.org/p3732/files/2026/09/peter-sushi.png" width="256"/&gt;
&lt;figcaption class="wp-element-caption"&gt;My composition suggestion&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;img alt="" class="wp-image-183 size-full alignnone" height="256" src="https://blogs.gnome.org/p3732/files/2026/10/jakub-sushi.png" width="256"/&gt;
&lt;figcaption class="wp-element-caption"&gt;Jakub’s refined version&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;/figure&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Sushi tries to show cover art when possible. This also included the capability to download cover art (&lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/116"&gt;something I fixed&lt;/a&gt; in July but seemingly forgot to mention). The downloaded covers were not stored in the file – a previewer shouldn’t modify files after all – so it was a rather obscure feature to have.&lt;/p&gt;
&lt;p&gt;Fetching covers of course involved sending queries to other people’s computers&lt;span class="kY2IgmnCmOGjharHErah N56cWZpP8cNJu1dqgCxB"&gt;&lt;span&gt;&lt;img alt="™" class="wp-smiley" src="https://s.w.org/images/core/emoji/17.0.2/72x72/2122.png" style="height: 1em;"/&gt;&lt;/span&gt;&lt;/span&gt;, which might be unexpected default behavior, especially since html previews started &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/112"&gt;asking for confirmation&lt;/a&gt; before fetching web content. Thus, Tau Gärtli and I agreed on removing this niche feature. As a replacement, I implemented something that seems more useful to me – &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/175"&gt;support for cover art files&lt;/a&gt; that are in the same folder as the song, such as &lt;em&gt;folder.jpg&lt;/em&gt; or &lt;em&gt;cover.png&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img alt="sushi showing folder.jpg as a cover" class="wp-image-187 size-full aligncenter" height="369" src="https://blogs.gnome.org/p3732/files/2026/10/sushi-folder-jpg-support-1.png" width="522"/&gt;&lt;/p&gt;
&lt;p&gt;Sometimes file previewing fails due to various reasons (missing codecs, corrupted file, …). Instead of the previous dedicated page, I &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/170"&gt;adjusted sushi’s error handling&lt;/a&gt; so that &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/168"&gt;basic file information&lt;/a&gt; is still shown, while the error is indicated by a banner:&lt;/p&gt;
&lt;p&gt;&lt;img alt="sushi showing an error banner" class="wp-image-184 size-full aligncenter" height="284" src="https://blogs.gnome.org/p3732/files/2026/10/sushi-error-banner.png" width="428"/&gt;&lt;/p&gt;
&lt;p&gt;Other small changes:&lt;/p&gt;
&lt;ul class="wp-block-list"&gt;
&lt;li&gt;I &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/169"&gt;fixed&lt;/a&gt; a &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/work_items/170"&gt;bug&lt;/a&gt; of my &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/159"&gt;own creation&lt;/a&gt; that prevented some mouse interactions. The fix is included in the 51.1 release that &lt;a class="external" href="https://github.com/flathub/org.gnome.NautilusPreviewer/pull/22"&gt;landed on Flathub&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Sushi now uses the default &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/163"&gt;&lt;em&gt;.Devel&lt;/em&gt; developer version suffix&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Renderer &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/176"&gt;loading times are limited&lt;/a&gt; now, preventing infinite load screens&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 class="wp-block-heading"&gt;gnome-autoar&lt;/h2&gt;
&lt;p&gt;Libarchive, the library used by gnome-autoar supports multi-threaded compression for some file types (7zip, xz, zstd), so I &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/58"&gt;added an option&lt;/a&gt; to enable this in gnome-autoar. If all goes well nautilus will &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2130"&gt;make use of this soon&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I also fixed a &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/59"&gt;signal parameter bug&lt;/a&gt; that was blocking a gnome-shell MR. The cause was that gnome-autoar correctly emits its signals in the main thread, but didn’t wait for responses in the asynchronous thread that initiated the signaling. For simple fire-and-forget signals that wouldn’t be an issue, but not only do some of gnome-autoar’s signals have return values, there even is one particularly peculiar case of a signal with an out parameter – something I couldn’t find another example of in other projects.&lt;/p&gt;
&lt;p&gt;I also created a handful of cleanup MRs, which bring the repository up to the standard of a modern (GObject-based) C project: a &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/56"&gt;gobject-linter CI job&lt;/a&gt;, &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/63"&gt;SPDX licence specifiers&lt;/a&gt;, &lt;a class="issue-title-text gl-text-base gl-link external" dir="auto" href="https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/55" id="listItem-null/133700"&gt;&lt;span&gt;G_LOG_DOMAIN usage&lt;/span&gt;&lt;/a&gt;, &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/62"&gt;code cleanups&lt;/a&gt; and more.&lt;/p&gt;
&lt;h2&gt;Roadmap&lt;/h2&gt;
&lt;p&gt;&lt;img alt="" class="aligncenter size-full wp-image-194" height="275" src="https://blogs.gnome.org/p3732/files/2026/10/0926-chart.png" width="999"/&gt;&lt;/p&gt;
&lt;h2&gt;Support the GNOME Project&lt;/h2&gt;
&lt;p&gt;&lt;a class="external" href="https://donate.gnome.org/"&gt;&lt;img alt="GNOME Donation graphic" class="aligncenter size-full wp-image-66" height="712" src="https://blogs.gnome.org/p3732/files/2026/08/donate-card.png" width="1067"/&gt;&lt;/a&gt; The GNOME Fellowships are funded by our community. If you would like to help the GNOME project to stay sustainable, please &lt;a class="external" href="https://donate.gnome.org/"&gt;consider donating&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;span style="color: #fff0;"&gt;AI Summary&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="color: #fff0;"&gt;Freed from his shackles, Autoar learns that they all along had the capability to do multiple things at the same time. With this, cleaning up the library is no problem and even the strangely wound looking glass on the signaling lookout gets fixed. Through it the group can be seen moving into the depths of the gnome caves. With them they carry rations in the form of paper scrolls, depicting such accurate portrays of sushi that fiction and reality is not distinguishable to mortal digestion systems.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="color: #fff0;"&gt;Important note: All statements in this blog are fictional.&lt;/span&gt;&lt;img alt="" class="aligncenter size-full wp-image-182" height="500" src="https://blogs.gnome.org/p3732/files/2026/10/moria-footer-1.png" width="1000"/&gt;&lt;/p&gt;
&lt;/figure&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/p3732/fellowship-report-september-2026-moria/</guid>
      <pubDate>Fri, 09 Oct 2026 12:03:51 +0000</pubDate>
    </item>
    <item>
      <title>Hylke Bons: Icon for Ripples</title>
      <link>https://planetpeanut.studio/post/2026/10/12/ripples</link>
      <description>&lt;img alt="Icon for Ripples" src="https://planetpeanut.studio/assets/img/icons/garden.tau.Ripples.svg" style="background-color: #813D9C; padding: 15% 25%; width: 100%;"/&gt;
&lt;h2&gt;Week 33&lt;/h2&gt;
&lt;p&gt;
    
        
            This week's icon is for
            &lt;a href="https://hachyderm.io/@tautropfli" rel="noopener noreferrer" target="_blank"&gt;Tau Gärtli&lt;/a&gt;'s project:
        

        &lt;br class="hide-when-narrow"/&gt;
&lt;a href="https://codeberg.org/tautropfli/ripples" rel="noopener noreferrer" target="_blank"&gt;Ripples&lt;/a&gt;:
    

    &lt;strong&gt;"Rip CDs"&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
    Check out all weekly app icons created so far in &lt;a href="https://planetpeanut.studio/icons"&gt;the gallery&lt;/a&gt;
    and follow my icon creation adventures as they happen (including sketches) on
    &lt;a href="https://mastodon.social/@hbons" rel="noopener noreferrer" target="_blank"&gt;the Fediverse&lt;/a&gt;.
&lt;/p&gt;
&lt;h2&gt;Need icons?&lt;/h2&gt;
&lt;p&gt;
    I love designing icons and am happy to contribute them
    &lt;a href="https://planetpeanut.studio/services"&gt;free of charge&lt;/a&gt;
    when your project is &lt;strong&gt;Free and Open Source&lt;/strong&gt;.
    Join as a &lt;a href="https://planetpeanut.studio/sponsors"&gt;community sponsor&lt;/a&gt; to maintain
    a steady supply of app icons to the Linux ecosystem
    (every little helps!).
&lt;/p&gt;</description>
      <guid isPermaLink="false">https://planetpeanut.studio/post/2026/10/12/ripples</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Javad Rahmatzadeh: Call for Volunteers to Help GNOME Extensions Team</title>
      <link>https://blogs.gnome.org/jrahmatzadeh/2026/10/12/help-ego-team/</link>
      <description>&lt;p&gt;
I remember back in 2020, people were complaining that we didn’t have enough documentation for creating GNOME Shell extensions. They said it was almost impossible to figure out where to start. They were right, learning all of it without proper documentation was a huge challenge for me too.
&lt;/p&gt;
&lt;span id="more-365"&gt;&lt;/span&gt;
&lt;p&gt;
So, I decided to learn the GNOME Shell source code and shared what I learned in a YouTube tutorial series. I spent countless hours learning and making those videos, and the community was very happy to finally have guides and documentation.
&lt;/p&gt;
&lt;p&gt;
On the GNOME side, Sriram Ramkrishna started the GNOME Extensions Rebooted project. When he noticed my tutorials, he invited me to join the team to help write documentation. I spent many hours learning GTK4 and the GNOME Shell 40 source code to write the famous GNOME Shell 40 Port Guide. I’d argue that many extension authors would have given up without it. Migrating from GTK3 to GTK4 and adapting to the changes between 3.38 and 40 was overwhelming. I wrote the guide with many examples, so developers could easily understand how to port their code.
&lt;/p&gt;
&lt;p&gt;
Today we have all the documentation needed to start and maintain extensions, but nowadays, people are just simply vibe coding GNOME Shell extensions without reading any of it before submitting it to EGO. To be honest, in the age of LLMs, it feels like our documentation is feeding LLMs more than actual human developers.
&lt;/p&gt;
&lt;p&gt;
For years, I tried my best to help the community, answering questions daily and reviewing extensions submitted to EGO, often spending 4 to 10 hours a day managing the whole extensions eco system. GNOME was incredibly generous this year and awarded me the GNOME Pants Award 2026 for my contributions to GNOME and the extensions ecosystem. That was a major personal milestone, and honestly, a testament to the growth of our community as a whole.
&lt;/p&gt;
&lt;p&gt;
I’m writing this post because since early 2025, the volume of submissions has exploded. The vast majority are AI generated, and the huge workload is pushing me close to burnout. To be clear, all of my work is unpaid. While managing this volume easily matches a full-time job, my monthly donations remain close to zero. Given how many people use GNOME extensions daily, I truly believe our community can help make this workload doable. If you find value in what I do or if my work has helped you out over the years, please consider &lt;a class="external" href="https://jrahmatzadeh.pages.gitlab.gnome.org/ego-donations/" target="_blank"&gt;supporting me through donations&lt;/a&gt;. Without financial support, I simply won’t be able to keep going at this pace.
&lt;/p&gt;
&lt;p&gt;
AI generated extensions, especially when prompted by non developers are frequently bloated and poorly designed. Because extensions run directly inside the GNOME Shell process, quality control is critical. Low-quality, AI generated code directly threatens the stability of the entire shell, and vibe coders need to realize that. As someone who reviews code across all of EGO, I can tell you that LLMs produce needlessly complex, hard to read code that takes significantly longer to review. To make matters worse, some submitters rely on AI to generate replies during the review process. I even received a response that accidentally pasted the LLM’s instructions intended for the user:
&lt;/p&gt;
&lt;blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"&gt;
Then, respond to the specific points it points to and maintain a real public repository, with testing instructions and development history. This gives the base reviewer to evaluate maintenance and quality, without trying to hide anything.
&lt;/blockquote&gt;
&lt;p&gt;
On a positive note, a while back I published &lt;a href="https://blogs.gnome.org/jrahmatzadeh/2026/07/27/ego-ai-reference/" target="_blank"&gt;An Open Letter to AI for Generating GNOME Shell Extensions&lt;/a&gt; to fix specific code patterns their models were generating incorrectly and I noticed most of those issues disappear just a few weeks after that post, which is great news, but also proof of just how heavily our documentation is feeding these LLMs.
&lt;/p&gt;
&lt;p&gt;
Anyway, we need viable solutions to keep the EGO ecosystem stable, trustworthy, and sustainable:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
I’m asking developers who understand GTK and GNOME Shell source code to join the review team. I am happy to mentor and teach you the review process. Please note that while this is a volunteer role, we need people who can be consistently available during the week.
&lt;/li&gt;
&lt;li&gt;
As many of you know, we introduced the Shexli linter a few months ago to make the review process easier. We need someone to help us improve it. The workflow is straightforward: reviewers identify false negatives and false positives during reviews, and you fix them in Shexli.
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
If you are interested in joining the review team or helping with Shexli, please reach out to us on &lt;a class="external" href="https://matrix.to/#/#extensions:gnome.org" target="_blank"&gt;GNOME Extensions Matrix channel&lt;/a&gt;. Thanks for being part of the GNOME community!
&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/jrahmatzadeh/2026/10/12/help-ego-team/</guid>
      <pubDate>Mon, 12 Oct 2026 23:37:47 +0000</pubDate>
    </item>
    <item>
      <title>Justin Wheeler: Managing multiple Git repos with AI: How I keep up with Fedora's sprawl</title>
      <link>https://jwheel.org/blog/2026/10/managing-multiple-git-repos-with-ai/</link>
      <description>&lt;img alt="Managing multiple Git repos with AI: How I keep up with Fedora&amp;amp;#39;s sprawl" src="https://jwheel.org/blog/2026/10/managing-multiple-git-repos-with-ai.jpg"/&gt;&lt;div class="paragraph"&gt;
&lt;p&gt;No single person can know everything happening in Fedora at any given time.
I say this often in our community, half as a warning and half for comfort.
For a while, I did not really believe it applied to me.
I wanted to know everything.
I joined new teams, participated in tickets, and either participated or led meetings across the project.
Surprisingly, as a &lt;a href="https://jwheel.org/tags/rochester-institute-of-technology/"&gt;young university student&lt;/a&gt;, I held a vast amount of it in my head.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;But Fedora does not stand still long enough for that to last.
Eventually, I was spread thin across more teams than I could realistically track.
As my academic load increased or I began an internship, promises I made quietly fell off my radar.
It was not because I did not care.
It was because the systems I used to track them could not keep up with the sprawl, when my available time to contribute changed.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;However, as I reentered the Fedora community as a &lt;a href="https://jwheel.org/categories/red-hat/"&gt;Red Hat employee&lt;/a&gt;, the same systems I used as a student were challenged.
As I get going with &lt;a href="https://jwheel.org/blog/2026/09/ai-alignment/"&gt;my new role&lt;/a&gt;, I am rethinking how I can rebalance my bandwidth sustainably.
So, this post is about how I started managing multiple Git repos with AI agents to claw back some of that bandwidth.
It is not really a story about a remarkable tool.
It is an argument that in a project this sprawling, protecting your attention is the real win.
I will cover two moments when things fell through the cracks, the workflow I built to catch them, a real example of it working, and an honest take on trusting AI when it sometimes gets things wrong.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="scale"&gt;Why managing multiple Git repos gets hard at Fedora’s scale &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#scale"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Fedora is sprawling.
Fedora’s &lt;a href="https://src.fedoraproject.org"&gt;distribution Git (dist-git)&lt;/a&gt;, the home for package sources, holds something like 20,000 packages.
Add the team and SIG repositories that coordinate the people behind those packages on &lt;a href="https://forge.fedoraproject.org"&gt;Fedora Forge&lt;/a&gt;, and the number of places where decisions get made is enormous.
Yet, most contributors only touch a handful of them.
However, even a handful is often scattered across different platforms, with no single view of all of it.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="cracks"&gt;Where things fell through the cracks &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#cracks"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Before this workflow, it felt like pure chaos, &lt;em&gt;and&lt;/em&gt; I have the scars to prove it.
Fedora runs on mailing lists, Fedora Discussion topics, Matrix chat rooms, and Fedora Forge issues/tickets.
Furthermore, all of these are spread across dozens of teams, Working Groups (WGs), and Special Interest Groups (SIGs).
In short, there are a lot of different places to follow a lot of different things.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;For a long stretch, the &lt;a href="https://docs.fedoraproject.org/en-US/marketing/"&gt;Fedora Marketing Team&lt;/a&gt; had a backlog of tickets.
In a few cases, contributors asked for talks and presentations to be uploaded to the Fedora YouTube channel.
I had the access to do it and other YouTube maintainers were no longer active, so therefore, it was quietly mine to own.
I saw the tickets at least once, but I was overworked and busy with higher-priority work.
The YouTube videos slid off my list.
A new volunteer eventually picked them up months or even a year later.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Additionally, Fedora also runs meetings well… on paper.
Fedora holds virtual text meetings in Matrix chat rooms with a bot that logs everything.
Each meeting has a clear start, a clear end, and annotated topics.
But a faithful log is not the same as follow-through.
For example, in AI/ML SIG meetings, we discuss a decision or someone takes an action item, and it gets logged.
But it does not always make it back into the relevant ticket or discussion post.
The record exists, but it does not connect itself to the places that need updating.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Patterns like this repeat themselves.
The examples above are merely specific examples of where things fall through the cracks.
However, there are things like this that happen everyday in different corners of the community too.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="workflow"&gt;The AI multi-repo workflow &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#workflow"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;So, here is the workflow I use now.
It does not get rid of all the chaos, but it helps me manage it much better.
First, I point an &lt;a href="https://jwheel.org/tags/llm-gen-ai/"&gt;LLM-gen-AI&lt;/a&gt; agent at a directory holding several cloned Git repositories.
For example, the &lt;a href="https://forge.fedoraproject.org/ai-ml/docs"&gt;AI/ML SIG docs repository&lt;/a&gt;, &lt;a href="https://forge.fedoraproject.org/ai-ml/tickets"&gt;AI/ML SIG tickets repository&lt;/a&gt;, and &lt;a href="https://forge.fedoraproject.org/ai-ml/skills-library"&gt;Agent Skills library&lt;/a&gt;.
Then I ask it to analyze across all of them.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;I also feed it meeting logs or summaries.
I ask it to cross-check them against open tickets and Fedora Discussion topics:&lt;/p&gt;
&lt;/div&gt;
&lt;div class="ulist"&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Did we document the decisions?&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Did we track the action items?&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Is anyone still waiting on a reply?&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Critically, I do not want it reading only files from my local &lt;code&gt;git&lt;/code&gt; clones.
I want it to query the remotes too: the Fedora Forge API, issues, discussions, and more.
The underlying &lt;a href="https://forgejo.org/docs/latest/user/api/usage/"&gt;Forgejo API&lt;/a&gt; is enormous.
It lets the agent track the actual cadence a team works at, not just a snapshot.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="sect2"&gt;
&lt;h3 id="trust"&gt;A word on trust and hallucination &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#trust"&gt;🔗&lt;/a&gt;&lt;/h3&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;I have to be honest here: the agent sometimes gets things wrong.
It will occasionally misread a thread or hallucinate a detail.
However, I do not think that disqualifies it.
Humans get things wrong too.
I would rather have slightly imperfect visibility into tens, hundreds, or even thousands of repositories than none at all.
Ultimately, the question is not whether the agent is ever wrong.
&lt;strong&gt;The question is what level of risk you are willing to accept for the visibility you gain&lt;/strong&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="example"&gt;A real example: Reviewer guidelines across three repos &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#example"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Our &lt;a href="https://forge.fedoraproject.org/ai-ml/skills-library"&gt;Fedora Agent Skills Library&lt;/a&gt; needed reviewer guidelines.
Laura Barcziová (&lt;a href="https://forge.fedoraproject.org/lbarczio"&gt;@lbarczio&lt;/a&gt;), on our reviewer team, wrote a solid &lt;code&gt;REVIEWING.md&lt;/code&gt; in the &lt;code&gt;ai-ml/skills-library&lt;/code&gt; repo.
But our separate &lt;code&gt;ai-ml/docs&lt;/code&gt; repository only had a page on creating a skill, and nothing on reviewing one.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;I used an agent in &lt;a href="https://opencode.ai/"&gt;OpenCode&lt;/a&gt; to pull discussion context from Fedora Forge issues about our reviewer process.
It helped me reconcile that context with Laura’s draft.
Then I orchestrated multiple Pull Requests across the repositories at once.
This brought the AI/ML SIG docs site in line with what the team had actually decided.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="payoff"&gt;The real payoff is not the tool &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#payoff"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;In conclusion, the payoff is that it hands me back the capacity to zoom out.
In a project where nobody can hold it all in their head, something should watch dozens of repositories.
It surfaces what changed and what needs to catch up.
&lt;strong&gt;That means I can engage with people’s feedback instead of just surviving the volume of it&lt;/strong&gt;.
When someone takes the time to review my Pull Request, I want the bandwidth to genuinely consider what they said.
I do not want to just clear my queue.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;I hope this overview of my flow and process is insightful.
As of yet, I do not have a commenting feature on my blog, although I am looking into this.
&lt;a href="https://www.linkedin.com/in/jwwheel/"&gt;Tag me&lt;/a&gt; in a LinkedIn post and we can continue the conversation there.&lt;/p&gt;
&lt;/div&gt;
&lt;hr/&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;&lt;em&gt;&lt;a href="https://unsplash.com/photos/conductor-leading-an-orchestra-with-a-baton-mqqcU42QOwU"&gt;Original photo&lt;/a&gt; by &lt;a href="https://unsplash.com/@dm_david?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText"&gt;DM David&lt;/a&gt; on Unsplash&lt;/em&gt;.
&lt;em&gt;Modified by Justin Wheeler&lt;/em&gt;.
&lt;em&gt;Modified cover photo exclusively distributed under CC BY-SA 4.0&lt;/em&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;</description>
      <guid isPermaLink="false">https://jwheel.org/blog/2026/10/managing-multiple-git-repos-with-ai/</guid>
      <pubDate>Tue, 13 Oct 2026 08:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Jiri Eischmann: Fedora &amp; CentOS at LinuxDays 2026</title>
      <link>https://enblog.eischmann.cz/2026/10/13/fedora-centos-at-linuxdays-2026/</link>
      <description>&lt;p class="wp-block-paragraph"&gt;LinuxDays 2026, the largest open-source event in Czechia, took place on the first weekend of October, and we had a Fedora &amp;amp; CentOS booth there again. This time, we got a smaller table and our booth equipment was more modest because no one traveled from Brno by car—we only had what we could carry on the train. However, we had quite a few nice stickers and one Framework laptop, which generated a lot of attention again.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I was happy that I didn’t have to staff the booth alone; I was accompanied by Vojtěch Trefny, a long-time Fedora contributor.&lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;img alt="" class="wp-image-2507" height="771" src="https://enblog.eischmann.cz/wp-content/uploads/2026/10/fedora-linuxdays26-1024x771.webp" width="1024"/&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;Even though CentOS Stream has existed for seven years now, we still received questions like: &lt;em&gt;“Oh, CentOS is still alive? I thought Red Hat killed it a long time ago.”&lt;/em&gt; This was typically the starting point for a conversation about the differences between the original CentOS and CentOS Stream, as well as their relation to Red Hat Enterprise Linux.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Most questions about Fedora were related to Framework, which didn’t come as a surprise given that we were showcasing Fedora Linux 45 on a Framework Laptop 16. People asked whether there is any cooperation between Fedora and Framework, whether Fedora Linux is a good OS for Framework hardware, and whether Framework is a good laptop option for Fedora Linux. To all of that, we had very positive answers.&lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;img alt="" class="wp-image-2508" height="771" src="https://enblog.eischmann.cz/wp-content/uploads/2026/10/fedora-linuxdays26-2-1024x771.webp" width="1024"/&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;It was an exhausting weekend because we had dozens of conversations, but it was also refreshing to meet Fedora and CentOS users and hear feedback directly from them. I’d like to thank Fedora for sponsoring my trip and Vojtěch for helping me with the booth.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://enblog.eischmann.cz/2026/10/13/fedora-centos-at-linuxdays-2026/</guid>
      <pubDate>Tue, 13 Oct 2026 11:06:21 +0000</pubDate>
    </item>
    <item>
      <title>Matthew Garrett: Linux Lockdown and Hibernation (again)</title>
      <link>https://codon.org.uk/~mjg59/blog/p/linux-lockdown-and-hibernation-again/</link>
      <description>&lt;p&gt;(This is an &lt;a class="link" href="https://mjg59.dreamwidth.org/55845.html" rel="noopener" target="_blank"&gt;updated version of an older post&lt;/a&gt; - the introduction remains the same, the technical details are different)&lt;/p&gt;
&lt;p&gt;Linux draws a distinction between code running in kernel (kernel space) and applications running in userland (user space). This is enforced at the hardware level - in x86-speak&lt;sup id="fnref:1"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:1"&gt;1&lt;/a&gt;&lt;/sup&gt;, kernel space code runs in ring 0 and user space code runs in ring 3&lt;sup id="fnref:2"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:2"&gt;2&lt;/a&gt;&lt;/sup&gt;. If you’re running in ring 3 and you attempt to touch memory that’s only accessible in ring 0, the hardware will raise a fault. No matter how privileged your ring 3 code, you don’t get to touch ring 0.&lt;/p&gt;
&lt;p&gt;Kind of. In theory. Traditionally this wasn’t well enforced. At the most basic level, since root can load kernel modules, you could just build a kernel module that performed any kernel modifications you wanted and then have root load it. Technically user space code wasn’t modifying kernel space code, but the difference was pretty semantic rather than useful. But it got worse - root could also map memory ranges belonging to PCI devices&lt;sup id="fnref:3"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:3"&gt;3&lt;/a&gt;&lt;/sup&gt;, and if the device could perform DMA you could just ask the device to overwrite bits of the kernel&lt;sup id="fnref:4"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:4"&gt;4&lt;/a&gt;&lt;/sup&gt;. Or root could modify special CPU registers (“Model Specific Registers”, or MSRs) that alter CPU behaviour via the /dev/msr interface, and compromise the kernel boundary that way.&lt;/p&gt;
&lt;p&gt;It turns out that there were a number of ways root was effectively equivalent to ring 0, and the boundary was more about reliability (ie, a process running as root that ends up misbehaving should still only be able to crash itself rather than taking down the kernel with it) than security. After all, if you were root you could just replace the on-disk kernel with a backdoored one and reboot. Going deeper, you could replace the bootloader with one that automatically injected backdoors into a legitimate kernel image. We didn’t have any way to prevent this sort of thing, so attempting to harden the root/kernel boundary wasn’t especially interesting.&lt;/p&gt;
&lt;p&gt;In 2012 Microsoft started requiring vendors ship systems with UEFI Secure Boot, a firmware feature that allowed&lt;sup id="fnref:5"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:5"&gt;5&lt;/a&gt;&lt;/sup&gt; systems to refuse to boot anything without an appropriate signature. This not only enabled the creation of a system that drew a strong boundary between root and kernel, it arguably required one - what’s the point of restricting what the firmware will stick in ring 0 if root can just throw more code in there afterwards? What ended up as the Lockdown Linux Security Module provides the tooling for this, blocking userspace interfaces that can be used to modify the kernel and enforcing that any modules have a trusted signature.&lt;/p&gt;
&lt;p&gt;But that comes at something of a cost. Most of the features that Lockdown blocks are fairly niche, so the direct impact of having it enabled is small. Except that it also blocks hibernation&lt;sup id="fnref:6"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:6"&gt;6&lt;/a&gt;&lt;/sup&gt;, and it turns out some people were using that. The obvious question is “what does hibernation have to do with keeping root out of kernel space”, and the answer is a little convoluted and is tied into how Linux implements hibernation. Basically, Linux saves system state into the swap partition and modifies the header to indicate that there’s a hibernation image there instead of swap. On the next boot, the kernel sees the header indicating that it’s a hibernation image, copies the contents of the swap partition back into RAM, and then jumps back into the old kernel code. What ensures that the hibernation image was actually written out by the kernel? Absolutely nothing, which means a motivated attacker with root access could turn off swap, write a hibernation image to the swap partition themselves, and then reboot. The kernel would happily resume into the attacker’s image, giving the attacker control over what gets copied back into kernel space.&lt;/p&gt;
&lt;p&gt;This is annoying, because normally when we think about attacks on swap we mitigate it by requiring an encrypted swap partition. But in this case, our attacker is root, and so already has access to the plaintext version of the swap partition. Disk encryption doesn’t save us here. We need some way to verify that the hibernation image was written out by the kernel, not by root. And thankfully we have some tools for that.&lt;/p&gt;
&lt;p&gt;Trusted Platform Modules (TPMs) are cryptographic coprocessors&lt;sup id="fnref:7"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:7"&gt;7&lt;/a&gt;&lt;/sup&gt; capable of doing things like generating encryption keys and then encrypting things with them. You can ask a TPM to encrypt something with a key that’s tied to that specific TPM - the OS has no access to the decryption key, and nor does any other TPM. So we can have the kernel generate an encryption key, encrypt part of the hibernation image with it, and then have the TPM encrypt it. We store the encrypted copy of the key in the hibernation image as well. On resume, the kernel reads the encrypted copy of the key, passes it to the TPM, gets the decrypted copy back and is able to verify the hibernation image.&lt;/p&gt;
&lt;p&gt;That’s great! Except root can do exactly the same thing. This tells us the hibernation image was generated on this machine, but doesn’t tell us that it was done by the kernel. We need some way to be able to differentiate between keys that were generated in kernel and ones that were generated in userland. TPMs have the concept of “localities” (effectively privilege levels) that would be perfect for this. Userland is only able to access locality 0, so the kernel could simply use locality 1 to encrypt the key. Unfortunately, localities are typically only available on systems that implement a &lt;a class="link" href="https://trustedcomputinggroup.org/resource/d-rtm-architecture-specification/" rel="noopener" target="_blank"&gt;Dynamic Root of Trust Measurement&lt;/a&gt; like Intel’s TXT, and most consumer systems have no support for this. So, we need another approach.&lt;/p&gt;
&lt;p&gt;TPMs have a set of Platform Configuration Registers (PCRs), intended for keeping a record of system state. The OS isn’t able to modify the PCRs directly. Instead, the OS provides a cryptographic hash of some material to the TPM. The TPM takes the existing PCR value, appends the new hash to that, and then stores the hash of the combination in the PCR - a process called “extension”. This means that the new value of the TPM depends not only on the value of the new data, it depends on the previous value of the PCR - and, in turn, that previous value depended on its previous value, and so on. The only way to get to a specific PCR value is to either (a) break the hash algorithm, or (b) perform exactly the same sequence of writes. On system reset the PCRs go back to a known value, and the entire process starts again.&lt;/p&gt;
&lt;p&gt;Some PCRs are different. PCR 23, for example, can be reset back to its original value without resetting the system. We can make use of that. The first thing we need to do is to prevent userland from being able to reset or extend PCR 23 itself. All TPM accesses go through the kernel, so this is a simple matter of parsing the write before it’s sent to the TPM and returning an error if it’s a sensitive command that would touch PCR 23. We now know that any change in PCR 23’s state will be restricted to the kernel.&lt;/p&gt;
&lt;p&gt;When we encrypt material with the TPM, we can ask it to record the PCR state. This is given back to us as metadata accompanying the encrypted secret. Along with the metadata is an additional signature created by the TPM, which can be used to prove that the metadata is both legitimate and associated with this specific encrypted data. In our case, that means we know what the value of PCR 23 was when we encrypted the key. That means that if we simply extend PCR 23 with a known value in-kernel before encrypting our key, we can look at the value of PCR 23 in the metadata. If it matches, the key was encrypted by the kernel - userland can create its own key, but it has no way to extend PCR 23 to the appropriate value first. We now know that the key was generated by the kernel.&lt;/p&gt;
&lt;p&gt;Unfortunately it turns out that some people actually make use of PCR 23, and
restricting it to the kernel makes them sad. There are other resettable PCRs, but only in non-0 localities, so (a) we can’t reset them on most systems and (b) we’ll just find someone who uses them anyway and run into the same problem. We need a different approach.&lt;/p&gt;
&lt;p&gt;Thankfully TPMs have a small chunk of non-volatile RAM that can be used for storing things, and by “storing” I mean they can be used in a range of different ways. One of these is effectively as additional PCRs. These values can be configured such that they work the same way as PCRs, with the only way to modify them being to append a new hash to their existing value and update the new value to the hash of that merged value. We can allocate one of these for in-kernel use and reject any access from userspace, and also there are officially allocated ranges (so people shouldn’t be using random values) and the namespace is large enough anyway that w eshouldn’t collide with anyone, so we can carve one of those out and use it for this purpose.&lt;/p&gt;
&lt;p&gt;Unfortunately, though, these NV indexes aren’t included in the creation data we get when we create a key, so we need another approach. TPMs have the concept of sessions, a series of commands executed in sequence. A flag allows these sessions to be “audited”, with the TPM keeping a running track of the hash of the commands executed and the results returned. At the end of the session you can ask for a signed copy of this hash, and if you’ve kept a log of all the commands then you can verify that they match that signed hash and know that this log represents a real communication with the TPM. If we read the NV index and generate the key inside the same session, we can verify that the key we’re looking at was created while the NV index had a specific value, and if only the kernel can set that value then we know that the key was generated by the kernel.&lt;/p&gt;
&lt;p&gt;Or, well, can we? Only new kernels would impose the restriction on modifying that NV index. An attacker could boot an old kernel, generate a key there in userland, sign a hibernation image with it, and then reboot into a new kernel. The new kernel would see a valid signature with a valid NV index associated with it and have no way to know it was generated from userland rather than the kernel. We need to be able to tell the difference between kernels that implement this feature and ones that don’t, and we need to do that without being able to go back in time to change old kernel behaviour. We can extend a PCR to indicate we implement the new functionality, but so can an attacker running an old kernel.&lt;/p&gt;
&lt;p&gt;The normal approach to determining whether an event occurred in a specific phase of the boot process is to “cap” the PCRs - extend them with a known value that indicates a transition between stages of the boot process. Any events that occur before the cap event must have occurred in the previous stage of boot, and since the final PCR value depends on the order of measurements and not just the contents of those measurements, if a PCR is capped before userland runs, userland can’t fake the same PCR value afterwards. If Linux capped the PCRs before userland started running, we’d be able to place a measurement there before the cap occurred and then prove that that extension occurred before userland had the opportunity to interfere. We could simply place a statement that the kernel supported the NV index restrictions there, and we’d be fine.&lt;/p&gt;
&lt;p&gt;Unfortunately Linux doesn’t currently do this, and adding support for doing so doesn’t fix the problem - if an attacker boots a kernel that doesn’t cap a PCR, they can just cap it themselves from userland. So, we’re faced with the same problem: booting an older kernel allows the system to be placed in an identical state to the current kernel, and a fake hibernation image can be written out. Solving this requires a PCR that was being modified after kernel code was running, but before userland was started, even with existing kernels.&lt;/p&gt;
&lt;p&gt;Thankfully, there is one! PCR 5 is &lt;a class="link" href="https://trustedcomputinggroup.org/wp-content/uploads/TCG_PCClient_PFP_r1p05_v23_pub.pdf" rel="noopener" target="_blank"&gt;defined&lt;/a&gt; as containing measurements related to boot management configuration and data. One of the measurements it contains is the result of the UEFI ExitBootServices() call. ExitBootServices() is called at the transition from the UEFI boot environment to the running OS, and the kernel contains code that executes before it. So, if we measure an assertion regarding whether or not we support restricted access to NV indexes into PCR 5 before we call ExitBootServices(), this will prevent userspace from spoofing us (because userspace will only be able to extend PCR 5 after the firmware extended PCR 5 in response to ExitBootServices() being called). Obviously this depends on the firmware actually performing the PCR 5 extension when ExitBootServices() is called, but if firmware’s out of spec then I don’t think there’s any real expectation of it being secure enough for any of this to buy you anything anyway.&lt;/p&gt;
&lt;p&gt;That’s what &lt;a class="link" href="https://lore.kernel.org/linux-pm/20261008132532.1155166-1-matthewg@nvidia.com/" rel="noopener" target="_blank"&gt;this patchset&lt;/a&gt; does. Review feedback so far seems positive, although James Bottomley &lt;a class="link" href="https://lore.kernel.org/linux-pm/aeedde06c51910afe5231d9f359bb8767c01b5bd.camel@HansenPartnership.com/" rel="noopener" target="_blank"&gt;suggested&lt;/a&gt; a design improvement. My approach of using an NV index as a PCR and generating a signing key made sense as a consequence of my original approach involving PCR 23, which had been to use the key creation data and not use audit sessions at all. But the goal isn’t to use a key - it’s to prove that hibernation occurred in-kernel, and while signing is one way of doing that, there are others. His suggestion is to simply record the hash of the hibernation image into the NV index and then read that back as part of the audit session. On resume we verify the audit session log is legitimate, read the hibernation image, and compare the hash of the hibernation image against the hash in the log. If it matches, and if the PCR 5 value matches, we know the audit session happened in kernel and that the hibernation image hasn’t been modified.&lt;/p&gt;
&lt;p&gt;It still seems like we’re missing something, though. If we’re not storing a key anywhere, how do we verify the audit session? To explain this we’re going to need to go into some details about how TPM keys work in the first place. TPMs can produce a special kind of key called an Attestation Key, or AK. Attestation keys are used to sign attestation statements from the TPM, such as PCR quotes or audit logs. We need a separate key type for this in order to prove that the signature was generated as part of an attestation - normal TPM signing keys are fundamentally designed to sign arbitrary material, and so can be used by userland to sign something that looks identical to an attestation record. By being able to distinguish the types of key the TPM uses, we can prove that a signature was generated using an AK, and so know that it’s a real TPM attestation (because nothing other than the TPM can sign stuff with an AK).&lt;/p&gt;
&lt;p&gt;But even beyond this distinction, TPMs have different key types. Ordinary keys are generated using an RNG and will be unique. Primary keys are generated using a seed that is used as an input into a key derivation function. For a given TPM, using the same seed to generate the same type of primary key will always generate the same primary key&lt;sup id="fnref:8"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:8"&gt;8&lt;/a&gt;&lt;/sup&gt;. We can have the kernel deterministically generate an AK during suspend in order to sign the audit log, and then generate the same key again on resume to validate it. This means we don’t need any other form of trusted storage for the AK - the TPM already provides that functionality.&lt;/p&gt;
&lt;p&gt;This is all rather complicated but I’ve been thinking about this for some time now and I haven’t come up with a cleaner solution. The only real open issue is the degree to which machines actually perform the PCR 5 extension. If it turns out there’s a bunch that don’t we’ll need to come up with some alternative approach to identifying whether the kernel supports this functionality, but the design is such that that should be invisible to userspace so adding alternatives later shouldn’t be an issue. Filtering accesses to the NV index is also not super clean, and depends on there not being alternative mechanisms to get at the TPM by sending raw commands. Again, this is intended to be opaque to userland and can be improved if we come up with something better later on (such as a secure way to pass a secret to the kernel on boot that can be used as an auth value for acess to the NV index).&lt;/p&gt;
&lt;p&gt;Anyway. Time to go and fix the next thing.&lt;/p&gt;
&lt;div class="footnotes"&gt;
&lt;hr/&gt;
&lt;ol&gt;
&lt;li id="fn:1"&gt;
&lt;p&gt;Other architectures use different terminology here, such as “supervisor” and “user” mode, but it’s broadly equivalent &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:1"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id="fn:2"&gt;
&lt;p&gt;In theory rings 1 and 2 would allow you to run drivers with privileges somewhere between full kernel access and userland applications, but in reality we just don’t talk about them in polite company &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:2"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id="fn:3"&gt;
&lt;p&gt;This is how graphics worked in Linux before kernel modesetting turned up. XFree86 would just map your GPU’s registers into userland and poke them directly. This was not a huge win for stability &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:3"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id="fn:4"&gt;
&lt;p&gt;IOMMUs can help you here, by restricting the memory PCI devices can DMA to or from. The kernel then gets to allocate ranges for device buffers and configure the IOMMU such that the device can’t DMA to anything else. Except that region of memory may still contain sensitive material such as function pointers, and attacks like this can still cause you problems as a result. &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:4"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id="fn:5"&gt;
&lt;p&gt;&lt;a class="link" href="https://mjg59.dreamwidth.org/23817.html" rel="noopener" target="_blank"&gt;This describes&lt;/a&gt; why I’m using “allowed” rather than “required” here &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:5"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id="fn:6"&gt;
&lt;p&gt;Saving the system state to disk and powering down the platform entirely - significantly slower than suspending the system while keeping state in RAM, but also resilient against the system losing power. &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:6"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id="fn:7"&gt;
&lt;p&gt;With some handwaving around “coprocessor”. TPMs can’t be part of the OS or the system firmware, but they don’t technically need to be an independent component. Intel have a TPM implementation that runs on the Management Engine, a separate processor built into the motherboard chipset. AMD have one that runs on the Platform Security Processor, a small ARM core built into their CPU. Various ARM implementations run a TPM in Trustzone, a special CPU mode that (in theory) is able to access resources that are entirely blocked off from anything running in the OS, kernel or otherwise. &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:7"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id="fn:8"&gt;
&lt;p&gt;Unless the TPM is cleared, in which case it’ll generate a new internal seed and now the keys will be different to before the clear &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:8"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;</description>
      <guid isPermaLink="false">https://codon.org.uk/~mjg59/blog/p/linux-lockdown-and-hibernation-again/</guid>
      <pubDate>Tue, 13 Oct 2026 18:14:36 +0000</pubDate>
    </item>
    <item>
      <title>Juan Pablo Ugarte: Cambalache 1.2 Released</title>
      <link>https://blogs.gnome.org/xjuan/2026/10/14/cambalache-1-2-released/</link>
      <description>&lt;p&gt;Hello, I am pleased to announce a new Cambalache release.&lt;/p&gt;
&lt;p&gt;Cambalache is a WYSIWYG (What You See Is What You Get) tool that allows you to create and edit user interfaces for Gtk 4 and 3 applications.&lt;/p&gt;
&lt;p&gt;This new version depends on GNOME SDK 51 and includes all new properties and types from Gtk and Adwaita! It also removes the file hash from the project file which should prevent unnecessary git conflicts.&lt;/p&gt;
&lt;p&gt;In case you missed it, you can read more about Cambalache in version 1.0 release blog.&lt;/p&gt;
&lt;blockquote class="wp-embedded-content"&gt;&lt;p&gt;&lt;a href="https://blogs.gnome.org/gtk/2026/03/20/cambalaches-first-major-milestone/"&gt;Cambalache’s First Major Milestone!&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h3&gt;Help us continue developing&lt;/h3&gt;
&lt;p&gt;&lt;img alt="" class="alignnone size-large wp-image-6578" height="424" src="https://blogs.gnome.org/xjuan/files/2026/10/Screenshot-From-2026-10-14-15-33-36-1024x679.png" width="640"/&gt;&lt;/p&gt;
&lt;p&gt;If you find this application useful you can support it’s development by contributing on &lt;a class="external" href="https://liberapay.com/xjuan/donate"&gt;Liberapay&lt;/a&gt; or &lt;a class="external" href="https://www.patreon.com/c/cambalache"&gt;Patreon&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;Where to get it?&lt;/h3&gt;
&lt;p&gt;From &lt;a class="external" href="https://flathub.org/apps/ar.xjuan.Cambalache"&gt;Flathub&lt;/a&gt;&lt;/p&gt;
&lt;pre&gt;flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

flatpak install flathub ar.xjuan.Cambalache&lt;/pre&gt;
&lt;p&gt;or directly from &lt;a class="external" href="https://gitlab.gnome.org/jpu/cambalache"&gt;gitlab&lt;/a&gt;&lt;/p&gt;
&lt;pre&gt;git clone https://gitlab.gnome.org/jpu/cambalache.git&lt;/pre&gt;
&lt;h3&gt;Matrix channel&lt;/h3&gt;
&lt;p&gt;Have any question? come chat with us at &lt;a class="external" href="https://matrix.to/#/#cambalache:gnome.org"&gt;#cambalache:gnome.org&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;Mastodon&lt;/h3&gt;
&lt;p&gt;Follow me in Mastodon &lt;a class="external" href="https://mastodon.social/@xjuan"&gt;@xjuan&lt;/a&gt; to get news related to Cambalache development.&lt;/p&gt;
&lt;p&gt;As usual happy coding!&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/xjuan/2026/10/14/cambalache-1-2-released/</guid>
      <pubDate>Wed, 14 Oct 2026 20:25:44 +0000</pubDate>
    </item>
    <item>
      <title>Lennart Poettering: Mastodon Stories for systemd v262</title>
      <link>https://0pointer.net/blog/mastodon-stories-for-systemd-v262.html</link>
      <description>&lt;p&gt;On September 22 we released systemd v262 &lt;a href="https://github.com/systemd/systemd/releases/tag/v262"&gt;into the wild&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In the weeks leading up to that release (and since then) I have posted
a series of serieses of posts to Mastodon about key new features in
this release, under the
&lt;a href="https://mastodon.social/@pid_eins/tagged/systemd262"&gt;#systemd262&lt;/a&gt;
hash tag. In case you aren't using Mastodon, but would like to
read up, here's a list of all 35 posts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Post #1: &lt;a href="https://mastodon.social/@pid_eins/117207780226511430"&gt;Word List Based Hostname Patterns&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #2: &lt;a href="https://mastodon.social/@pid_eins/117211181398036487"&gt;Extended Attributes on Socket Inodes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #3: &lt;a href="https://mastodon.social/@pid_eins/117228519200902581"&gt;Varlink Socket Tagging &amp;amp; &lt;code&gt;varlinkctl list-sockets&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #4: &lt;a href="https://mastodon.social/@pid_eins/117235153018414805"&gt;Machine Tags from udev/hwdb&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #5: &lt;a href="https://mastodon.social/@pid_eins/117239695617453611"&gt;&lt;code&gt;systemd-sysupdate&lt;/code&gt;'s installdb&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #6: &lt;a href="https://mastodon.social/@pid_eins/117246051474468010"&gt;Signed &lt;code&gt;systemd-report&lt;/code&gt; Reports&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #7: &lt;a href="https://mastodon.social/@pid_eins/117251226934854499"&gt;CLI Introspection via &lt;code&gt;--introspect-cli&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #8: &lt;a href="https://mastodon.social/@pid_eins/117267347707334533"&gt;fscrypt v2 Support in &lt;code&gt;systemd-homed&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #9: &lt;a href="https://mastodon.social/@pid_eins/117273210877733036"&gt;Read-Only ESP Support in &lt;code&gt;systemd-boot&lt;/code&gt;/&lt;code&gt;systemd-stub&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #10: &lt;a href="https://mastodon.social/@pid_eins/117273287700273999"&gt;Recovery Key Enrollment on First Boot &amp;amp; Varlink IPC for &lt;code&gt;systemd-cryptenroll&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #11: &lt;a href="https://mastodon.social/@pid_eins/117279327476146346"&gt;Rogue TPM Protection for LUKS Enrollments&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #12: &lt;a href="https://mastodon.social/@pid_eins/117285451154586301"&gt;Encrypted + Verity Protected DDIs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #13: &lt;a href="https://mastodon.social/@pid_eins/117285505441116266"&gt;&lt;code&gt;FONT_SCALE=&lt;/code&gt; in &lt;code&gt;/etc/vconsole.conf&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #14: &lt;a href="https://mastodon.social/@pid_eins/117291330986767568"&gt;Static, Single-Binary Service Manager Builds&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #15: &lt;a href="https://mastodon.social/@pid_eins/117307883706564416"&gt;Intel TDX CoCo Support in &lt;code&gt;systemd-vmspawn&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #16: &lt;a href="https://mastodon.social/@pid_eins/117307922786764254"&gt;Varlink IPC for &lt;code&gt;systemd-sysinstall&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #17: &lt;a href="https://mastodon.social/@pid_eins/117313577398838909"&gt;&lt;code&gt;systemd-report&lt;/code&gt; as Varlink Service &amp;amp; New Metrics&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #18: &lt;a href="https://mastodon.social/@pid_eins/117313622306856202"&gt;Sessions as Inhibitors via &lt;code&gt;pam_systemd&lt;/code&gt;'s &lt;code&gt;inhibit=&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #19: &lt;a href="https://mastodon.social/@pid_eins/117318995941370845"&gt;NvPCR Rework&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #20: &lt;a href="https://mastodon.social/@pid_eins/117319022526394457"&gt;&lt;code&gt;bootctl link-auto&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #21: &lt;a href="https://mastodon.social/@pid_eins/117324847382676032"&gt;&lt;code&gt;systemd-sysupdate&lt;/code&gt; Completion Hooks&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #22: &lt;a href="https://mastodon.social/@pid_eins/117330469927950153"&gt;&lt;code&gt;/etc/clonetab&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #23: &lt;a href="https://mastodon.social/@pid_eins/117330637810435545"&gt;Atomically Enqueuing Multiple Jobs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #24: &lt;a href="https://mastodon.social/@pid_eins/117347366496420026"&gt;Following the Journal via Varlink&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #25: &lt;a href="https://mastodon.social/@pid_eins/117347469710171616"&gt;Coredumps via the Kernel's New Socket Protocol&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #26: &lt;a href="https://mastodon.social/@pid_eins/117370066255624846"&gt;Hardware-Suggested &lt;code&gt;systemd-sysupdate&lt;/code&gt; Features/Components&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #27: &lt;a href="https://mastodon.social/@pid_eins/117370153006683768"&gt;&lt;code&gt;ActivatingConcurrencyMax=&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #28: &lt;a href="https://mastodon.social/@pid_eins/117375400891220164"&gt;Restarting/Reloading Units on &lt;code&gt;confext&lt;/code&gt;/&lt;code&gt;sysext&lt;/code&gt; Application&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #29: &lt;a href="https://mastodon.social/@pid_eins/117375424166675800"&gt;System Credentials for CoCo VMs in &lt;code&gt;systemd-vmspawn&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #30: &lt;a href="https://mastodon.social/@pid_eins/117409562126011137"&gt;Persisting the TPM EK&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #31: &lt;a href="https://mastodon.social/@pid_eins/117409640846619956"&gt;&lt;code&gt;systemd.firstboot=headless&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #32: &lt;a href="https://mastodon.social/@pid_eins/117443622656834979"&gt;&lt;code&gt;RestartRandomizedDelaySec=&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #33: &lt;a href="https://mastodon.social/@pid_eins/117443679535406341"&gt;&lt;code&gt;systemd.credentials_boot_policy=&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #34: &lt;a href="https://mastodon.social/@pid_eins/117443807526148791"&gt;&lt;code&gt;systemctl kexec --kernel-cmdline-reuse&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Post #35: &lt;a href="https://mastodon.social/@pid_eins/117443866832659215"&gt;PCR Signature Policyrefs&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I intend to do a similar series of serieses of posts for the next
systemd release (v263), hence if you haven't left tech Twitter for
Mastodon yet, now is the opportunity. My series for v263 will begin in
a few weeks most likely, under the
&lt;a href="https://mastodon.social/@pid_eins/tagged/systemd263"&gt;#systemd263&lt;/a&gt;
hash tag.&lt;/p&gt;
&lt;p&gt;In case you are interested, &lt;a href="https://0pointer.net/blog/mastodon-stories-for-systemd-v261.html"&gt;here is the corresponding blog story for
systemd v261&lt;/a&gt;,
&lt;a href="https://0pointer.net/blog/mastodon-stories-for-systemd-v260.html"&gt;here for
v260&lt;/a&gt;,
&lt;a href="https://0pointer.net/blog/mastodon-stories-for-systemd-v259.html"&gt;here for
v259&lt;/a&gt;,
&lt;a href="https://0pointer.net/blog/mastodon-stories-for-systemd-v258.html"&gt;here for
v258&lt;/a&gt;,
&lt;a href="https://0pointer.net/blog/announcing-systemd-v257.html"&gt;here for
v257&lt;/a&gt;,
and &lt;a href="https://0pointer.net/blog/announcing-systemd-v256.html"&gt;here for
v256&lt;/a&gt;.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://0pointer.net/blog/mastodon-stories-for-systemd-v262.html</guid>
      <pubDate>Wed, 14 Oct 2026 22:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Jakub Steiner: Digger</title>
      <link>https://blog.jimmac.eu/posts/digger/</link>
      <description>&lt;p&gt;&lt;img alt="Digger" src="https://blog.jimmac.eu/posts/digger/digger.webp"/&gt;&lt;/p&gt;
&lt;p&gt;The fact this movie tanked at the box office just makes the ride all the more enjoyable. I had a bad headache and had to call off the screening with a friend yesterday. Thursday is when the movies rotate in our part of the world where we use the un-American units, so I thought I'd missed yet another great cinematic experience. Luckily they still showed it in a small neighboring town, to the two of us and two other people, with an introduction by a charming young person.&lt;/p&gt;
&lt;p&gt;I don't remember anything these days, but I clearly remember when I saw &lt;em&gt;Dr. Strangelove&lt;/em&gt; in Amherst, NH, in 1993. I was completely taken by the humor, despite thinking I'd never enjoy an ancient movie like that. It's probably way longer between my viewing and today than it was between then and the actual production of it. I don't wanna check.&lt;/p&gt;
&lt;p&gt;Anyhow, this is masterfully done cinema, and all four of us laughed out loud at the horrors we saw. Absolute must-see.&lt;/p&gt;
&lt;p&gt;★★★★★&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blog.jimmac.eu/posts/digger/</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Jakub Steiner: Pixels Wallpaper Update</title>
      <link>https://blog.jimmac.eu/posts/pixelart-wallpapers/</link>
      <description>&lt;p&gt;Usually I blog about new additions to the &lt;a href="https://gitlab.gnome.org/GNOME/gnome-backgrounds" rel="external"&gt;GNOME wallpapers&lt;/a&gt; after a release, to give some behind the scenes look on how they were produced. This time I'm asking for some feedback beforehand.&lt;/p&gt;
&lt;span id="continue-reading"&gt;&lt;/span&gt;&lt;img alt="Orange pixel art wallpaper variant with large foreground icons, photographed on a monitor" class="full" src="https://blog.jimmac.eu/posts/pixelart-wallpapers/pixels-wip.webp"/&gt;
&lt;p&gt;&lt;code&gt;Pixels&lt;/code&gt; has shipped as a wallpaper before. The wallpaper landed back in 2021 and keeps getting refreshed as new &lt;a href="https://circle.gnome.org" rel="external"&gt;Circle&lt;/a&gt; apps join the lineup, and 47 added &lt;code&gt;LCD&lt;/code&gt; and &lt;code&gt;LCD-rainbow&lt;/code&gt;, revealing the curator's pixelart kink.&lt;/p&gt;
&lt;p&gt;The raw material is a side project years in the making — app icons redrawn as chunky pixels (&lt;a href="https://blog.jimmac.eu/posts/pixels/"&gt;Pixels&lt;/a&gt;, &lt;a href="https://blog.jimmac.eu/posts/mopixels/"&gt;Mo' Pixels&lt;/a&gt;, &lt;a href="https://blog.jimmac.eu/posts/app-pixels/"&gt;Revert That Vector Nonsense!&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;The idea and layout remains the same as the old wallpaper. This time that's more than two variants though. The old Adwaita default used to cycle morning, day and night variants through a slideshow. While we switched to the dark/light variants, the format is still understood today. Thus &lt;code&gt;pixelart&lt;/code&gt; comes in not 2, not 3, but 9 color variants. And here's where I'd like your feedback. Do you like the focus on contrast and having the whole set with dark background colors? Should there be more bright colors in the mix? Do you think the grain goes against the spirit of the pixel art? Is the small grid too toned down with the depth fog?&lt;/p&gt;
&lt;video class="image full" controls="controls" loop="loop" poster="https://blog.jimmac.eu/depth-fog.webp"&gt;
&lt;source src="https://blog.jimmac.eu/posts/pixelart-wallpapers/depth-fog.webm" type="video/webm"/&gt;
&lt;source src="https://blog.jimmac.eu/posts/pixelart-wallpapers/depth-fog.mp4" type="video/mp4"/&gt;
&lt;/video&gt;
&lt;p&gt;As always, the Blender project files are available in &lt;a href="https://gitlab.gnome.org/Teams/Design/wallpaper-assets-2026" rel="external"&gt;wallpaper-assets&lt;/a&gt; if you want to poke at the node setup yourself:&lt;/p&gt;
&lt;p&gt;As with any wallpaper, don't judge it based on a preview, regardless of how large you view it. Apply it, use it. The most straightforward way to test GNOME development is with &lt;a href="https://os.gnome.org" rel="external"&gt;GNOME OS&lt;/a&gt;. It ships &lt;code&gt;pixels&lt;/code&gt; and all the other wallpapers.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blog.jimmac.eu/posts/pixelart-wallpapers/</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Gedit Technology: gedit 51.0 released</title>
      <link>https://gedit-text-editor.org/blog/2026-10-15-gedit-51.html</link>
      <description>&lt;p&gt;
  The
  &lt;a href="https://gedit-text-editor.org/" target="_blank"&gt;gedit text editor&lt;/a&gt;
  version 51 has been released!
&lt;/p&gt;
&lt;p&gt;
  A previous blog post,
  &lt;a href="https://gedit-text-editor.org/blog/2026-05-29-news.html" target="_blank"&gt;News, April-May 2026&lt;/a&gt;
  already covers most of the changes.
&lt;/p&gt;
&lt;p&gt;
  A reminder that gedit is still alive and is available to install, as an
  alternative.
&lt;/p&gt;
&lt;p&gt;
  Progress has been made since May, but it's mostly under-the-hood changes,
  preparatory work to replace some internals and eventually make bigger visible
  changes to the application(s).
&lt;/p&gt;
&lt;h3&gt;B2B Services&lt;/h3&gt;
&lt;p&gt;
  gedit is not only an application, there is a set of libgedit-* shared
  libraries underneath. This collection of re-usable code can be leveraged to
  create new products, and
  &lt;a href="https://gedit-text-editor.org/b2b.html" target="_blank"&gt;B2B services&lt;/a&gt;
  are possible.
&lt;/p&gt;
&lt;p&gt;&lt;small&gt;&lt;em&gt;
  This was another reminder, but it cannot hurt ;-)
&lt;/em&gt;&lt;/small&gt;&lt;/p&gt;</description>
      <guid isPermaLink="false">https://gedit-text-editor.org/blog/2026-10-15-gedit-51.html</guid>
      <pubDate>Thu, 15 Oct 2026 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Christian Schaller: Using Artificial Intelligence to reverse engineer hardware</title>
      <link>https://blogs.gnome.org/uraeus/2026/10/15/aiandreverseengineerhardware/</link>
      <description>&lt;p&gt;After my mother passed away I ended up with a big box full of old film negatives containing photos from childhood family trips and similar. So I decided to buy a negative photo scanner and found that the Plustek 8200i was supported under Linux so I bought that. Only to discover that the chipset in the scanner had changed to one that wasn’t supported under Linux anymore. So I had some success making Linux configuration tools for some of my hardware using Claude code, like my &lt;a class="external" href="https://gitlab.com/cschalle/appfordellwebcam"&gt;Dell Camera controller app&lt;/a&gt; so I thought, maybe Claude can help me get a working SANE driver. I basically got stuck and got nowhere for the longest time and even basically gave up on the project for a few Months.&lt;/p&gt;
&lt;p&gt;Then I saw a &lt;a class="external" href="https://x.com/GloriousEggroll/status/2103816580966830314"&gt;post on X from Tom Crider aka Glorious Eggroll&lt;/a&gt; talking about how he had managed to fix a mouse driver using AI tooling. He basically described how he set it up so that the AI agent had full control of a Windows instance to capture data needed to fix the driver. So I pasted his tweet into Claude and asked it to help me set up a windows virtual machine to do the same things Tom as doing for my scanner. I think the combination of having the ability to run scans under windows and capture the USB data while doing so worked wonders, probably combined with improvements to Claude code made a huge difference. Within a few hours I had my first ever working scan under Linux, sure with some quality issues, but 100% recognizable as the image in the negative. Some days later I had a near perfect driver, including support for Infrared scanning ready to go, only to discover that in the time between me giving up and then trying again someone had committed code to SANE to support the scanner already…..it happens sometimes. I also used Claude to write an application for doing negative scanning, which I named &lt;a class="external" href="https://github.com/cschalle/negative-vibes"&gt;Negative Vibes&lt;/a&gt;, thought that was a cute name.&lt;/p&gt;
&lt;p&gt;Anyway, with the success of my scanner effort I thought, I wonder if I can use this to finally fix the last issues with MIPI camera support on my laptop. So I told claude to re-use the harness I had created and try to fix the MIPI camera on my laptop by updating the kernel driver and libcamera as needed. I started the job in the morning and by the end of the day I had &lt;a class="external" href="https://cschalle.github.io/mipi-fixes-x1-aura/"&gt;a much improved situation&lt;/a&gt; with patches for both the kernel and libcamera ready. &lt;/p&gt;
&lt;p&gt;So I thought that this might be worthwhile sharing with the world, and while anyone could start from scratch I did ask Claude to make the harness generic and document it to make the pathway for anyone else who wants to try this on their hardware a little easier. Writing a driver for undocumented hardware has always been tedious. You capture bus traffic, stare at hex dumps, and form hypotheses about what each register or control transfer does. You then test them one at a time, usually for weeks. None of it is conceptually hard, but it takes a lot of patience and skills.&lt;/p&gt;
&lt;p&gt;That kind of work suits an AI model well. It can read thousands of lines of USB capture, notice that a sequence repeats with one byte changing, and propose what that byte means. It can write the test to confirm it, and it doesn’t get bored. The human still decides what to build and checks that it works on real hardware, but the slog shrinks a lot.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;a class="external" href="https://github.com/cschalle/hw-harness"&gt;hw-harness&lt;/a&gt;&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;Be aware that I did not use hw-harness in this form for my projects as this was basically bespoke code at that time, so this project is an attempt to make the harness more generic and shareable from the scripts I was using while doing the work. What hw-harness is meant to help your Claude or Codex session with:&lt;/p&gt;
&lt;p&gt;1. Record a reference session. Run the vendor’s Windows driver in a KVM virtual machine, with the real device passed through to the guest.&lt;br/&gt;
2. Capture from outside the VM. Record the traffic on the Linux host with usbmon. It sits below the passthrough layer, so the guest can’t see it.&lt;br/&gt;
3. Repeat the same operation on Linux with your own driver, and capture that the same way.&lt;br/&gt;
4. Diff the two traces. Both come from the same instrument, so they compare directly. The differences are your list of driver bugs.&lt;/p&gt;
&lt;p&gt;For devices with no bus to tap, such as an internal MIPI camera, the harness uses Windows-side inspection instead. That means INF files, registry data, ACPI tables and device properties.&lt;/p&gt;
&lt;p&gt;The approach should be fine in the sense it doesn’t rely on copying any code instead it observes what the hardware does and only extract configuration data from the Windows drivers, so every constant in the new driver traces back to something recorded.&lt;/p&gt;
&lt;p&gt;So for those interested I have 3 short descriptions of the projects I did and what was needed.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Project 1: &lt;a class="external" href="https://htmlpreview.github.io/?https://github.com/cschalle/OpticFilm8200i-sane/blob/main/docs/comparison/drivers-comparison.html"&gt;a SANE backend for the Plustek OpticFilm 8200i&lt;/a&gt;&lt;/strong&gt;&lt;br/&gt;
&lt;div class="wp-caption alignright" id="attachment_11389" style="width: 310px;"&gt;&lt;a href="https://blogs.gnome.org/uraeus/files/2026/10/drivercompare.png"&gt;&lt;img alt="comparison of two scanner drivers on same negative-" class="size-medium wp-image-11389" height="218" src="https://blogs.gnome.org/uraeus/files/2026/10/drivercompare-300x218.png" width="300"/&gt;&lt;/a&gt;&lt;p class="wp-caption-text" id="caption-attachment-11389"&gt;Comparing the driver output of two drivers available.&lt;/p&gt;&lt;/div&gt;&lt;br/&gt;
The first project is a SANE backend for the newer Plustek OpticFilm 8200i. It uses the Genesys GL128 controller (USB 07b3:1825) and had no Linux support. The older model with the same name uses a GL845 and is already handled by SANE.&lt;/p&gt;
&lt;p&gt;The backend supports:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Color, gray, infrared and color+infrared modes&lt;/li&gt;
&lt;li&gt;Resolutions from 300 to 7200 dpi, at 8 or 16 bits per channel&lt;/li&gt;
&lt;li&gt;Dust and scratch removal from the infrared channel&lt;/li&gt;
&lt;li&gt;An exposure multiplier for dense negatives&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It’s packaged as a Fedora RPM, built automatically on every push. I mostly tested it with my own Negative Vibes application as there are not that many options under Linux for negative scanning.&lt;/p&gt;
&lt;p&gt;Upstream SANE’s genesys backend also gained support for this scanner in September 2026, so I compared the two. Both resolve the same fine detail at 3600 dpi. Mine is faster at full resolution (34.6 s against 54.4 s) and supports infrared dust removal. Upstream offers more resolution steps. The webpage has an interactive side-by-side comparison you can check out. These are single-unit, single-frame results, so treat them as one data point. &lt;a class="external" href="https://htmlpreview.github.io/?https://github.com/cschalle/OpticFilm8200i-sane/blob/main/docs/comparison/drivers-comparison.html"&gt;Check out the interactive page I made&lt;/a&gt; showing the current state of the two drivers, hopefully the discoveries I made can be used by the SANE project to fix some smaller items in the upstream driver. Anyway, I put this project up more as a proof of concept due to that since I expect everyone including myself will use the upstream driver once it reaches parity with this one.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Project 2: &lt;a class="external" href="https://github.com/cschalle/negative-vibes"&gt;Negative Vibes&lt;/a&gt;&lt;/strong&gt;&lt;br/&gt;
&lt;div class="wp-caption alignright" id="attachment_11385" style="width: 310px;"&gt;&lt;a href="https://blogs.gnome.org/uraeus/files/2026/10/afterscan.png"&gt;&lt;img alt="" class="size-medium wp-image-11385" height="192" src="https://blogs.gnome.org/uraeus/files/2026/10/afterscan-300x192.png" width="300"/&gt;&lt;/a&gt;&lt;p class="wp-caption-text" id="caption-attachment-11385"&gt;Full scan of negative completed including infrared cleaning of image.&lt;/p&gt;&lt;/div&gt;&lt;br/&gt;
A driver alone isn’t much use if scanning negatives is still painful, so I built Negative Vibes. It’s a GNOME app, written in Rust, for scanning colour and black-and-white negatives and slides on any film-capable SANE scanner.&lt;/p&gt;
&lt;p&gt;The scan is kept exactly as the scanner delivered it: 16-bit, linear, with the infrared plane. Everything else is a stack of non-destructive settings on top, so you can change the look and export again. It includes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Density-space negative inversion with film base and dye-crosstalk correction&lt;/li&gt;
&lt;li&gt;Roll-wide settings with per-frame overrides&lt;/li&gt;
&lt;li&gt;Infrared and software dust removal&lt;/li&gt;
&lt;li&gt;IT8 calibration through ArgyllCMS&lt;/li&gt;
&lt;li&gt;Export to TIFF, JPEG, PNG and DNG, with ICC profiles and metadata&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It ships as a Flatpak that includes the scanner backend. It’s tested on the 8200i so far. The goal is to support any film scanner SANE supports. For that, SANE needs a standard way to expose infrared channels, which it doesn’t have yet.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Project 3: &lt;a class="external" href="https://cschalle.github.io/mipi-fixes-x1-aura/"&gt;Fixing the MIPI camera on my ThinkPad&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;div class="wp-caption alignright" id="attachment_11393" style="width: 310px;"&gt;&lt;a href="https://blogs.gnome.org/uraeus/files/2026/10/mipifixes.png"&gt;&lt;img alt="Showing MIPI output before and after fixes. Colors are better than they look as I was sitting in a relatively dark room by the end of the session." class="size-medium wp-image-11393" height="96" src="https://blogs.gnome.org/uraeus/files/2026/10/mipifixes-300x96.png" width="300"/&gt;&lt;/a&gt;&lt;p class="wp-caption-text" id="caption-attachment-11393"&gt;Showing MIPI output before and after fixes. Colors are better than they look as I was sitting in a relatively dark room by the end of the session.&lt;/p&gt;&lt;/div&gt;&lt;br/&gt;
The camera in my Lenovo ThinkPad X1 Carbon Gen 14 (Aura Edition) uses a Sony IMX471 sensor behind an Intel IPU7. On Linux it produced dark images with heavy vignetting and a strong yellow-green cast. mipi-fixes-x1-aura collects the fixes. It’s only relevant to this laptop, which is why it isn’t one of the bigger packaged projects, but I have already submitted the kernel patches to Kate Hsuan and the libcamera patches is being reviewed by Wim Taymans for submission to Libcamera.&lt;/p&gt;
&lt;p&gt;Kernel (IMX471 driver):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A crop-selection bug returned an error before storing the crop rectangle, so libcamera assumed the full pixel array.&lt;/li&gt;
&lt;li&gt;The test-pattern register was declared with the wrong width.&lt;/li&gt;
&lt;li&gt;The analogue gain cap was too low, which cost about 1.8 stops of sensitivity.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;libcamera software ISP:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Lens shading correction was missing entirely, leaving the corners about 2.7 stops darker.&lt;/li&gt;
&lt;li&gt;White-balance statistics were summed at the sensor’s native bit depth against an 8-bit black level. That skewed white balance, and the fix applies to any RAW10/RAW12 sensor.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In a controlled low-light test, frame brightness rose from 31.1 to 90.9. The red/green and blue/green ratios moved from 0.890 and 0.672 to 1.047 and 0.823, close to a USB webcam reference. Blue is still about 17% short in low light, which I put down to grey-world white balance. Fedora 44 RPMs are on the releases page.&lt;/p&gt;
&lt;p&gt;What I learned&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Reference captures are a big step. Having the AI compare a known-good trace against a failing one turns a vague “it doesn’t work” into a concrete list of differences. For example for the MIPI camera having a USB camera also connected so Claude could compare the two captures was critical.&lt;/li&gt;
&lt;li&gt;The AI is good at the tedium. That covers decoding captures, writing probes and cross-checking constants. I still have to be the one holding the physical hardware.&lt;/li&gt;
&lt;li&gt;Real hardware is the only judge. Every claim above was checked on the actual scanner or laptop.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you have hardware with no Linux driver, try hw-harness. Thanks again to Glorious Eggroll for the inspiration.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;NOTE: I am not claiming that my scans or MIPI camera is perfect now, but the scanner gives me decent looking scans and the MIPI camera looks a lot better than before. So over time I am sure we be able to tweak and polish further, but I am happy that it allowed me to move the needle despite lacking the in-depth knowledge for this type of work.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;—&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/uraeus/2026/10/15/aiandreverseengineerhardware/</guid>
      <pubDate>Thu, 15 Oct 2026 13:28:39 +0000</pubDate>
    </item>
    <item>
      <title>Jussi Pakkanen: Implementing a simple version of ThreadPoolExecutor in Pystd</title>
      <link>https://nibblestew.blogspot.com/2026/10/implementing-simple-version-of.html</link>
      <description>&lt;p&gt;One of my favourite things in the Python standard library is the &lt;a href="https://docs.python.org/3/library/concurrent.futures.html#threadpoolexecutor"&gt;ThreadPoolExecutor&lt;/a&gt;. It is a very simple way to run a bunch of tasks in parallel, such as converting or repacking a whole bunch of image files from one format to another. You write a pure function that takes two arguments, the input and output file names, and does the conversion. Then you submit a bunch of tasks (basically function and argument pairs) and the executor runs them with maximal parallelism.&lt;/p&gt;&lt;p&gt;I decided to implement this in &lt;a href="https://github.com/jpakkane/pystd"&gt;Pystd&lt;/a&gt;. To make things simpler it does not yet support futures for return values. Writing a thread pool executor needs some fundamental building blocks such as threads, mutexes and condition variables. Once those were implemented (and working), writing the actual "business logic" turned out to be fairly simple. In fact, it took less time than writing the PNG processing code with libpng.&lt;/p&gt;&lt;p&gt;First you need to write this helper class to register you task for running. It also stores all arguments etc that the task needs to do its thing. Yes, this has a bit of that "icky 90s Java" feeling to it but OTOH it is fairly simple, has unambiguous ownership semantics and compiles massively faster than your typical template monstrosity.&lt;/p&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEq9GGutkXo9PpOuHwgN6jFmPrJP19jc4xYx_6PoYIvxeC2UvrHmca4aQcIX6YKHv5pw6yTrM999vIrA5Pb6lIcySvXt3Z5kiLqIblGjJsHIbLLQB3BIRWhgV-f4g3x2iIhCMzGTTyl1ZNmSy89ZT3X4-qkNZQ5UzIL9kNTEeRNcWfSf2j0x_dfPIMiaU/s827/task_interface.png" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="120" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEq9GGutkXo9PpOuHwgN6jFmPrJP19jc4xYx_6PoYIvxeC2UvrHmca4aQcIX6YKHv5pw6yTrM999vIrA5Pb6lIcySvXt3Z5kiLqIblGjJsHIbLLQB3BIRWhgV-f4g3x2iIhCMzGTTyl1ZNmSy89ZT3X4-qkNZQ5UzIL9kNTEeRNcWfSf2j0x_dfPIMiaU/w400-h120/task_interface.png" width="400"/&gt;&lt;/a&gt;&lt;/div&gt;&lt;p&gt;Using this is just a matter of globbing for png files in the input dir and submitting tasks for them.&lt;/p&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_SA9_thLIJY0N4duW-GW4MYpm7l0eU9UD8zMbzrb3174WGZr-VgP55-ThILCtPY7xJ4CE4Esg6yHWANccdaD_-pGaY0VI2TMGRAPsvmzawEFT8ElFmqzNOTbb0RZXFTGXEkWjTDPdIB4THzEwWUEg3RamnO2HIO4SlWlj8P4ei9cdEZMSZKymZtv87lU/s838/task_submit.png" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="118" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_SA9_thLIJY0N4duW-GW4MYpm7l0eU9UD8zMbzrb3174WGZr-VgP55-ThILCtPY7xJ4CE4Esg6yHWANccdaD_-pGaY0VI2TMGRAPsvmzawEFT8ElFmqzNOTbb0RZXFTGXEkWjTDPdIB4THzEwWUEg3RamnO2HIO4SlWlj8P4ei9cdEZMSZKymZtv87lU/w400-h118/task_submit.png" width="400"/&gt;&lt;/a&gt;&lt;/div&gt;&lt;p&gt;The UX is a bit verbose. It could probably be made nicer with a helper method or two. Still, not too shabby for something written by hand in a single afternoon.&lt;/p&gt;&lt;p&gt;For those interested in details, the code for this program is in the &lt;a href="https://github.com/jpakkane/pystd/blob/pngtest/tools/pngrepacker.cpp"&gt;pngtest&lt;/a&gt; branch.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://nibblestew.blogspot.com/2026/10/implementing-simple-version-of.html</guid>
      <pubDate>Thu, 15 Oct 2026 15:57:55 +0000</pubDate>
    </item>
    <item>
      <title>Matthew Garrett: Epic's EAC2 v2 seems fairly easily bypassable</title>
      <link>https://codon.org.uk/~mjg59/blog/p/epics-eac2-v2-seems-fairly-easily-bypassable/</link>
      <description>&lt;p&gt;Epic just &lt;a class="link" href="https://onlineservices.epicgames.com/news/introducing-easy-anti-cheat-linux-v2" rel="noopener" target="_blank"&gt;announced&lt;/a&gt; the upcoming version 2 of their Linux implementation of Easy Anti-Cheat. It’s based on using the &lt;a class="link" href="https://docs.kernel.org/bpf/prog_lsm.html" rel="noopener" target="_blank"&gt;Linux eBPF security module&lt;/a&gt; to monitor what’s happening, and then a bunch of extra infrastructure to make sure this can’t be bypassed. The core part of this is requiring secure boot be enabled (ensuring that modified kernels can’t be used), using measured boot to verify that secure boot is enabled and which keys are used (to prevent you from just signing your own modified kernel), and then doing remote attestation, a mechanism where the TPM generates a signed copy of the boot measurements and passes that off to a server which verifies it came from a real TPM, verifies that you have secure boot enabled and are using the right keys, and presumably then allows you into the game.&lt;/p&gt;
&lt;p&gt;This is all fine as long as you can prove that the measurements provided are real, and that’s actually a lot harder than you might think. First, we can simply make up our own quote signed with our own key and say that it came from a TPM. This is avoided by every TPM having an Endorsement Key (or EK) and an associated certificate, with that certificate being signed by the TPM vendor. If you have a list of all the legitimate TPM vendors and their CA keys, you can verify that the measurements came from a real TPM. Easy enough. So we need to get the measurements from a real TPM, and the one on our motherboard contains the measurements that were generated by the firmware and bootloader, and we can’t reset those at runtime without resetting the TPM, which… oh huh there’s actually nothing stopping us from doing that at runtime, as long as we have access to the hardware. Many desktop boards have the TPM on a small plugin module with a standard pinout that includes a reset pin. Simply short that to ground briefly and the TPM is back in its initial state, and userland can write whatever measurements it wants to it. Boot a modified kernel which lies to the eBPF code? As long as you replay the expected log values from a boot with secure boot on and a trusted kernel, the TPM will still happily provide a legitimate set of measurements that’ll satisfy the checker.&lt;/p&gt;
&lt;p&gt;What if the TPM is less accessible, either because it’s mounted directly to the motherboard or it’s inside the CPU or chipset? That’s going to be trickier. But here’s the thing. The quote needs to come from &lt;em&gt;a&lt;/em&gt; TPM, but not necessarily the TPM on your motherboard. TPMs these days are usually connected via the &lt;a class="link" href="https://en.wikipedia.org/wiki/Serial_Peripheral_Interface" rel="noopener" target="_blank"&gt;Serial Peripheral Interface&lt;/a&gt;, usually referred to as SPI. Microchip make a &lt;a class="link" href="https://www.microchip.com/en-us/product/mcp2210" rel="noopener" target="_blank"&gt;USB to SPI bridge&lt;/a&gt;, and there’s a &lt;a class="link" href="https://github.com/daniel-santos/mcp2210-linux" rel="noopener" target="_blank"&gt;Linux driver&lt;/a&gt;. Wire one of those up with an appropriate header and you can plug in an easily available TPM module intended for plugging into a motherboard, and now we tell the kernel to ignore the motherboard TPM and make /dev/tpmrm0 point at the USB one and program it with a set of trusted measurements and once again everything is going to look just fine (yes obviously the eBPF code can look for this, but we’re running a modified kernel so we can just lie to the eBPF code).&lt;/p&gt;
&lt;p&gt;Remote attestation on PCs just doesn’t work that well in environments where you can’t associate a specific TPM with a specific system, which is basically everywhere except enterprises. But maybe that doesn’t matter and cheaters wouldn’t be willing to spend the $20 or so it’d take to produce one of these things? That would seem somewhat surprising, but it’s not impossible. And obviously any server-side cheat detection that triggers could then block that specific TPM, meaning they’d need to go and get another TPM, and maybe that ends up being enough to discourage people from bothering. From a practical level, this may be sufficient. But at a technical level? It’s not great.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://codon.org.uk/~mjg59/blog/p/epics-eac2-v2-seems-fairly-easily-bypassable/</guid>
      <pubDate>Thu, 15 Oct 2026 20:23:59 +0000</pubDate>
    </item>
    <item>
      <title>Adrian Vovk: Introducing GNOME OS Preview</title>
      <link>https://blogs.gnome.org/adrianvovk/2026/10/16/gnome-os-preview/</link>
      <description>&lt;p class="wp-block-paragraph"&gt;It’s been two years since &lt;a href="https://blogs.gnome.org/adrianvovk/2024/10/25/a-desktop-for-all/https://blogs.gnome.org/adrianvovk/2024/10/25/a-desktop-for-all/"&gt;my initial post&lt;/a&gt; about making GNOME OS an end-user general purpose OS. Today, we’re excited to announce that we’ve hit a major milestone!&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;TL;DR: We’re launching a new edition called “GNOME OS Preview”, which is built from the latest stable GNOME release. This means that GNOME OS is no longer &lt;em&gt;just&lt;/em&gt; a nightly OS for GNOME developers and testers!&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;The Road to Stable&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;Even though GNOME OS has been usable on real hardware for a few years now, its appeal was limited. We’ve only had the Nightly edition, which is constantly rebuilt to ship the latest git commit of every GNOME component (and a few others, like systemd and Flatpak). This form of GNOME OS is extremely useful, since GNOME developers and designers can daily-drive it to test the latest changes. However, it’s not something we’d recommend to non-developers.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Over the past year, we’ve seen a lot of adoption of GNOME OS Nightly amongst GNOME developers, especially following the success of last year’s &lt;a href="https://blogs.gnome.org/tbernard/2025/06/01/summer-of-gnome-os/"&gt;Summer of GNOME OS&lt;/a&gt; challenge. This has led to a significant uptick in contributions and initiatives aimed at improving user and developer experience. For instance:&lt;/p&gt;
&lt;ul class="wp-block-list"&gt;
&lt;li&gt;Thanks to Jonas Dreßler’s, Valentin David’s, and Sebastian Wick’s &lt;code&gt;zswap&lt;/code&gt; enablement efforts, GNOME OS now handles devices with limited amounts of RAM without OOM stalls. Jonas also found a hack that lets GNOME OS dynamically grow the usable on-disk swap space on-demand, which makes &lt;code&gt;zswap&lt;/code&gt; perform significantly better than usual.&lt;/li&gt;
&lt;li&gt;The recently released &lt;a class="external" href="https://flathub.org/en/apps/cx.modal.TestCenter"&gt;Test Center&lt;/a&gt; app allows you to install CI builds of Flatpak apps from a merge request, making it super easy to test experimental changes before they are even merged. On GNOME OS Nightly, Test Center can do the same with system components by applying them as a system extension.&lt;/li&gt;
&lt;li&gt;Jordan Petridis’s new &lt;a href="https://blogs.gnome.org/alatiera/2026/09/26/introducing-toolpak/"&gt;Toolpak&lt;/a&gt; project aims to provide a clean solution for distributing and installing command-line applications that developers need in a cross-distro fashion, similarly to how Flatpak and Flathub work for graphical apps.&lt;/li&gt;
&lt;/ul&gt;
&lt;p class="wp-block-paragraph"&gt;Of course, long-term our goal is an OS for the broader public. We’re working on this across a number of different fronts, including:&lt;/p&gt;
&lt;ul class="wp-block-list"&gt;
&lt;li&gt;Enablement for &lt;code&gt;systemd-homed&lt;/code&gt; across the stack, allowing for stronger per-user disk encryption and other benefits.&lt;/li&gt;
&lt;li&gt;Experimental work in the kernel to solve a bunch of limitations we’ve run into with filesystems. Ada Magicat went on a deep dive on her recent &lt;a class="external" href="https://youtu.be/c_mD9EMCyvM"&gt;All Systems Go talk&lt;/a&gt;!&lt;/li&gt;
&lt;li&gt;Deep integration between &lt;code&gt;systemd-homed&lt;/code&gt; and the session’s keyring, to increase security of the session’s lock screen. Dhanuka Warusadura gave a &lt;a class="external" href="https://youtu.be/amjaGmvr2uI"&gt;lightning talk at All Systems Go&lt;/a&gt; about his work on this.&lt;/li&gt;
&lt;li&gt;A new feature-complete installer, to replace the current placeholder installer. Julian Sparber also gave &lt;a class="external" href="https://youtu.be/biS6XaJ4ZTo"&gt;a talk about this at All Systems Go&lt;/a&gt;, with a live demo!&lt;/li&gt;
&lt;li&gt;Support for delta updates in &lt;code&gt;systemd-sysupdate&lt;/code&gt;, to avoid downloading a full 2 GB image every time.&lt;/li&gt;
&lt;li&gt;Better integration with the TPM, including a graphical TPM recovery UI. Currently, trying to type a TPM recovery key into Plymouth is rather difficult.&lt;/li&gt;
&lt;li&gt;Improved support for ARM hardware, including some specific models of phones. Abderrahim Kitouni gave a &lt;a class="external" href="https://youtu.be/13Jbnn7LH0I"&gt;lightning talk at GUADEC this year&lt;/a&gt; about the current installation process.&lt;/li&gt;
&lt;li&gt;Shipping our pre-installed apps as Flatpaks, and reworking the app release process to unify the build definitions between GNOME OS, the &lt;a class="external" href="https://nightly.gnome.org"&gt;GNOME Nightly Apps&lt;/a&gt; Flatpak repo, and Flathub.&lt;/li&gt;
&lt;li&gt;An STF project focused on Flatpak and Portals, which will enable broader app support on GNOME OS (like VPNs!). You can learn more from the &lt;a class="external" href="https://modal.cx/blog/announcing-flatpak-sta/"&gt;announcement blog post&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p class="wp-block-paragraph"&gt;Some of these areas require lots more work before they’re ready for prime time, and even once they’re ready it’s not clear that it’ll be possible to migrate existing GNOME OS installations to use these new features. At &lt;a href="https://blogs.gnome.org/adrianvovk/2026/02/18/gnome-os-hackfest-fosdem-2026/"&gt;FOSDEM this year&lt;/a&gt;, we discussed this issue and decided that we won’t declare GNOME OS as “stable” until we can confidently commit to maintaining a clear long-term upgrade path for existing installations.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;However, we also don’t think that all these things need to be in place before GNOME OS can be used by more people than it is today. It’s &lt;em&gt;not&lt;/em&gt; ready for the masses yet, but it is ready for early adopters that aren’t quite adventerous enough to run a nightly OS.&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Introducing GNOME OS Preview&lt;/h2&gt;
&lt;p class="wp-block-paragraph"&gt;GNOME OS Preview is the current GNOME OS Nightly, but without the “nightly” aspect. Instead, it’s built from the latest stable GNOME release (GNOME 51.1, at the time of writing). GNOME OS Preview lives in the same branches on &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-build-meta"&gt;GitLab&lt;/a&gt; as the stable &lt;code&gt;org.gnome.Platform&lt;/code&gt; Flatpak runtimes.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;GNOME OS Preview is only a few weeks old, so it has only seen limited real-life testing so far. We therefore expect people will uncover some issues initially. That said, Preview is significantly more stable than Nightly, which dozens of people have been daily driving without major issues for over a year. Thus, we’re feeling confident that Preview is going to be reliable enough for daily use by non-developer enthusiasts.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;In all likelihood, GNOME OS Preview will be with us for a few years. However, &lt;strong&gt;we are explicitly not promising updates in perpetuity&lt;/strong&gt;. If you’re not OK with re-installing your OS in a few years to switch to GNOME OS Stable, this is not for you yet. But if you’ve already been curious about giving GNOME OS a try, this is the moment!&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;GNOME OS Preview is available for download on the newly-refreshed &lt;a class="external" href="https://os.gnome.org"&gt;os.gnome.org&lt;/a&gt;! GNOME OS Nightly is still available from there too. As always, you can reach us on Matrix at &lt;a class="external" href="https://matrix.to/#/#gnome-os:gnome.org"&gt;#gnome-os:gnome.org&lt;/a&gt; or via the &lt;a class="external" href="https://discourse.gnome.org/tag/gnome-os"&gt;&lt;code&gt;gnome-os&lt;/code&gt; tag on Discourse&lt;/a&gt;&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/adrianvovk/2026/10/16/gnome-os-preview/</guid>
      <pubDate>Fri, 16 Oct 2026 17:47:07 +0000</pubDate>
    </item>
    <item>
      <title>Jakub Steiner: Liberec Dam</title>
      <link>https://blog.jimmac.eu/posts/liberec-dam/</link>
      <description>&lt;figure class="yt"&gt;
&lt;div class="yt__shell"&gt;
&lt;div class="yt__stage"&gt;
&lt;a class="yt__facade" href="https://www.youtube.com/watch?v=wiKVTD2or2s"&gt;
&lt;img alt="Liberec Dam 2026" class="yt__poster" height="720" src="https://i.ytimg.com/vi/wiKVTD2or2s/maxresdefault.jpg" width="1280"/&gt;
&lt;span class="yt__vignette"&gt;&lt;/span&gt;
&lt;span class="yt__play"&gt;&lt;/span&gt;
&lt;/a&gt;
&lt;/div&gt;
&lt;div class="yt__bar"&gt;
&lt;span class="yt__title"&gt;Liberec Dam 2026&lt;/span&gt;
&lt;a class="yt__watch" href="https://www.youtube.com/watch?v=wiKVTD2or2s" rel="noopener"&gt;Watch on YouTube&lt;/a&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/figure&gt;
&lt;p&gt;There's only a few places I get to take visiting friends to in Liberec. Sadly at the moment almost all of them are out of service. The city dam, Harcovská přehrada, is one of them. A fraction of the size of a neighboring Mšeno, it's set close to the middle of the city and is a wonderful walk/running place, despite only half having a foot path.&lt;/p&gt;
&lt;p&gt;In the autumn of 2022, a full reconstruction finally began, a mere century after the dam was built. Quite a massive operation, with 26,000 cubic meters of silt dug out, the original masonry  injected with a fresh waterproof jacket from a brand new gallery dug right under the dam, and the bottom outlets were swapped for beefier ones. Being a listed landmark, the dam got to keep its pretty face while the guts were replaced. A three-year job that -- in the finest local tradition -- took a bit longer and cost north of EUR 20 million. It's worth noting that Liberec is one if not the most indebted cities in Czechia.&lt;/p&gt;
&lt;p&gt;In the meantime the city had a moonscape where its living room used to be. I went to investigate the drained bowl like everyone else and came back with a portrait short of the eerie emptiness (mixed with some shots from the wider neighborhood).&lt;/p&gt;
&lt;figure class="yt"&gt;
&lt;div class="yt__shell"&gt;
&lt;div class="yt__stage"&gt;
&lt;a class="yt__facade" href="https://www.youtube.com/watch?v=ygFHgP8sbEU"&gt;
&lt;img alt="Empty Dam" class="yt__poster" height="720" src="https://i.ytimg.com/vi/ygFHgP8sbEU/maxresdefault.jpg" width="1280"/&gt;
&lt;span class="yt__vignette"&gt;&lt;/span&gt;
&lt;span class="yt__play"&gt;&lt;/span&gt;
&lt;/a&gt;
&lt;/div&gt;
&lt;div class="yt__bar"&gt;
&lt;span class="yt__title"&gt;Empty Dam&lt;/span&gt;
&lt;a class="yt__watch" href="https://www.youtube.com/watch?v=ygFHgP8sbEU" rel="noopener"&gt;Watch on YouTube&lt;/a&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/figure&gt;
&lt;p&gt;This year the water finally came back. Not yet finished, the lake is once again the city's front yard, has a refurbished beach, and a dam that's now rated to pass a 10,000-year flood. A figure I sincerely hope remains purely theoretical. To celebrate, I did the only reasonable thing: sent up a flying camera and cut the results to a tune. Sadly the dam claimed another one of my birds (currently the score is 2:0). A mistake had cost me one of older 5" as a broken OSD, ancient battery and water can lead to brisk ends. Luckily the tandem flight with a friend was done on my 4" and I have a video to share above.&lt;/p&gt;
&lt;p&gt;The soundtrack was composed, as is the tradition around here, on the &lt;a href="https://www.dirtywave.com" rel="external"&gt;Dirtywave M8&lt;/a&gt;. Should watching atmospheric drum &amp;amp; bass slowly materialize out of a tracker over the course of a couple of hours sound like your idea of an evening, the &lt;a href="https://www.youtube.com/watch?v=USO2ZSnFplQ" rel="external"&gt;recorded stream&lt;/a&gt; is up on YouTube.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blog.jimmac.eu/posts/liberec-dam/</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Sebastian Wick: Varlink observability</title>
      <link>https://blog.sebastianwick.net/posts/systemd-varlinkctl-monitor/</link>
      <description>&lt;p&gt;A few days ago &lt;a href="https://github.com/systemd/systemd/pull/42898"&gt;systemd gained tools&lt;/a&gt; which allow you to monitor Varlink traffic. A new Varlink service (&lt;code&gt;io.systemd.VarlinkMonitor&lt;/code&gt;) allows you to set up a ring buffer which will get filled with packets containing the traffic which matches the filters you provide. This provides the functionality that &lt;code&gt;org.freedesktop.DBus.Monitoring&lt;/code&gt; provides for D-Bus. A new &lt;code&gt;varlinkctl monitor&lt;/code&gt; verb allows you to use this feature in terminals and scripts. This provides the functionality that &lt;code&gt;dbus-monitor&lt;/code&gt; provides for D-Bus and uses &lt;code&gt;io.systemd.VarlinkMonitor&lt;/code&gt; under the hood. If you pass &lt;code&gt;--json short&lt;/code&gt; to &lt;code&gt;varlinkctl monitor&lt;/code&gt;, it produces JSON-seq which can be passed into &lt;code&gt;jq --seq&lt;/code&gt; to further process the captured data.&lt;/p&gt;
&lt;p&gt;I presented this in the broader context of observability with Varlink at All Systems Go. &lt;a href="https://cfp.all-systems-go.io/all-systems-go-2026/talk/FKWEC8/"&gt;Slides&lt;/a&gt; and &lt;a href="https://media.ccc.de/v/all-systems-go-2026-437-varlink-observability"&gt;video&lt;/a&gt; of the talk are available online.&lt;/p&gt;
&lt;p&gt;This is a good start, but I think we should add more tooling around it. Especially Bustle would be an interesting target because it would allow us to capture D-Bus and Varlink at the same time and get a global view of what is going on in our systems again.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blog.sebastianwick.net/posts/systemd-varlinkctl-monitor/</guid>
      <pubDate>Sun, 18 Oct 2026 13:37:00 +0000</pubDate>
    </item>
    <item>
      <title>Jonathan Blandford: Crosswords 0.3.19 — New Layout and Acrostic Editor</title>
      <link>https://blogs.gnome.org/jrb/2026/10/20/crosswords-0-3-19-new-layout-and-acrostic-editor/</link>
      <description>&lt;p&gt;Time for a new Crosswords release! This is a good one. This past cycle features two major changes: the game got a major visual overhaul, and the Acrostic Editor is no longer in Beta.&lt;/p&gt;
&lt;p&gt;This release is dedicated to Luciana. She contributed the adorable artwork for &lt;a class="external" href="https://libipuz.org/"&gt;libipuz&lt;/a&gt;, and is a budding cruciverbalist. She’s currently having a bit of a tough go of it healthwise, so please join me in sending her good wishes. We’re all rooting for you!&lt;/p&gt;
&lt;p&gt;&lt;a class="external" href="https://libipuz.org/"&gt;&lt;img alt="" class="logo alignnone" height="203" src="https://libipuz.org/libipuz-1.0/logo-thumb.png" width="229"/&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;New Game Layout&lt;/h2&gt;
&lt;p&gt;The game mode got a complete rework this cycle. We moved the &lt;em&gt;Across /Down&lt;/em&gt; labels into the header, and added independent header bars for each column. This work was designed by &lt;em&gt;“gnoman”,&lt;/em&gt; who did a fabulous initial mockup, and then provided a lot of additional feedback as we iterated through possibilities. The end result looks so much better than before, and is orders of magnitude better than anything I dreamed of when I started this project.&lt;/p&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_7786" style="width: 285px;"&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/mockup.png"&gt;&lt;img alt='Initial mockup from "gnoman"' class="wp-image-7786 size-medium" height="300" src="https://blogs.gnome.org/jrb/files/2026/10/mockup-285x300.png" width="285"/&gt;&lt;/a&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-7786"&gt;Initial mockup from “gnoman”&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;Every aspect of the game looks better, especially single-column mode. That now has a bottom drawer for the clues. Take a look at how it resizes:&lt;/p&gt;
&lt;div class="wp-video" style="width: 840px;"&gt;&lt;video class="wp-video-shortcode" controls="controls" height="445" id="video-7777-1" preload="metadata" width="840"&gt;&lt;source src="https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-16-36-11.webm?_=1" type="video/webm"/&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-16-36-11.webm"&gt;https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-16-36-11.webm&lt;/a&gt;&lt;/video&gt;&lt;/div&gt;
&lt;p&gt;I had to heavily adjust the reflow animation to deal with the updated appearance. For better or worse, this layout cannot be done with stock GTK/libadwaita containers and needs a complex custom layout widget. It’s a pain to edit, but it also means that we control every stage of the animation process. We handle things from reparenting buttons to panel changes.  The direction switching even cross-fades between the label and the toggle instead of snapping. It’s a small thing, but it makes the whole animation silky smooth.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;“Gnoman”&lt;/em&gt; also contributed animated SVGs for the “How to Play” dialog. Florian migrated us to the new GTK SVG animation framework, and we’ve ended up with an even slicker, charming intro screen.&lt;/p&gt;
&lt;h2&gt;Acrostic Editor Is No Longer Beta&lt;/h2&gt;
&lt;p&gt;A few years ago, Tanmay added acrostic support to the game. This puzzle type was fun-looking! But since we didn’t have a ready source of them, he started working on editor so we could write our own. He got something basic working but it wasn’t reliably usable. The problem was the grid autofill feature: it was just too slow. It worked by doing a DFS through the possible anagrams with a random answer shape. Sometimes it found results, most of the time it did not.&lt;/p&gt;
&lt;p&gt;This cycle, I went back to try and fix it and now have something usable. As sometimes is the case, the trick to get it working turned out to be really simple: We just had to try a new random shape after 30K iterations or so. It was a small change to the code — just a counter. But we ended up with something that could find grids with regularity.&lt;/p&gt;
&lt;p&gt;Once that started working I went back and fixed up the rest of the workflow. The Quote/Source entries are now instant apply and you can manually edit entries in the list. There’s an info panel that gives acrostic stats and an overlay pane to mark progress. It looks a lot better — and works! I’ve used it to create three acrostics already and have more coming. Take a look:&lt;/p&gt;
&lt;div class="wp-video" style="width: 840px;"&gt;&lt;video class="wp-video-shortcode" controls="controls" height="447" id="video-7777-2" preload="metadata" width="840"&gt;&lt;source src="https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-18-14-20.webm?_=2" type="video/webm"/&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-18-14-20.webm"&gt;https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-18-14-20.webm&lt;/a&gt;&lt;/video&gt;&lt;/div&gt;
&lt;h2&gt;New Generic Widgets&lt;/h2&gt;
&lt;p&gt;As part of working on the Acrostic Editor, I wrote some new widgets. These are not crosswords-specific, and are written so that people can cut-and-paste them into their app (if it’s GPLv3 compatible). They’re targeted for internal use but maybe would be useful for others.&lt;/p&gt;
&lt;p&gt;The more interesting of the two is &lt;tt&gt;XwdRichTextRow&lt;/tt&gt;. It’s an alternative for &lt;tt&gt;AdwEntryRow&lt;/tt&gt; that uses a &lt;tt&gt;GtkTextView&lt;/tt&gt; instead of a &lt;tt&gt;GtkEntry&lt;/tt&gt;. It has two features that the libadwaita widget doesn’t:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;An &lt;tt&gt;:n-rows&lt;/tt&gt; property to set the number of visible rows. If set to 1, it matches the pixel extents of AdwEntryRow. But larger numbers will provide additional lines of editable space. A vertical scrollbar is provided once the row count gets large enough.&lt;/li&gt;
&lt;li&gt;Rich text editing. It supports &lt;strong&gt;bold&lt;/strong&gt;, &lt;em&gt;italic&lt;/em&gt;, &lt;s&gt;strikethrough&lt;/s&gt; etc, and provides a convertor from pango markup to-and-from the widget. I wrote it in such a way that a markdown convertor could be written as well.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It’s not as comprehensive as &lt;tt&gt;AdwEntryRow&lt;/tt&gt; yet: it doesn’t support prefix/suffix widgets, emojis, or an apply button, and there are probably a lot of bugs. It also will never support &lt;tt&gt;GtkEditable&lt;/tt&gt;, due to the &lt;tt&gt;GtkTextBuffer&lt;/tt&gt; underpinnings. But it may be useful and fill a niche that I, at least, have felt a void for a while.&lt;/p&gt;
&lt;div class="wp-video" style="width: 804px;"&gt;&lt;video class="wp-video-shortcode" controls="controls" height="928" id="video-7777-3" preload="metadata" width="804"&gt;&lt;source src="https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-16-05-18.webm?_=3" type="video/webm"/&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-16-05-18.webm"&gt;https://blogs.gnome.org/jrb/files/2026/10/Screencast-From-2026-10-19-16-05-18.webm&lt;/a&gt;&lt;/video&gt;&lt;/div&gt;
&lt;p&gt;I also wrote &lt;tt&gt;XwdInfoButton&lt;/tt&gt;, which is basically a simple menu button that creates explanatory popovers. It should be used sparingly, but for a really complex app like the editor I think it can help demystify some sections. It takes a markdown string as its format.&lt;/p&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_7804" style="width: 300px;"&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/Screenshot-From-2026-10-19-14-01-57-border.png"&gt;&lt;img alt="" class="wp-image-7804 size-medium" height="287" src="https://blogs.gnome.org/jrb/files/2026/10/Screenshot-From-2026-10-19-14-01-57-border-300x287.png" width="300"/&gt;&lt;/a&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-7804"&gt;Info Popover&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;Let me know if you have any interest in using these widgets.&lt;/p&gt;
&lt;h2&gt;Non-Distro Builds, And a Plea For Help&lt;/h2&gt;
&lt;p&gt;Crosswords has built on macOS for a while thanks to Vinny’s heroics, but nothing stopped us from breaking it. He’s fixed that: we now have a macOS arm64 CI job, building against Homebrew with Apple clang. Now macOS-specific errors can be caught at commit time.&lt;/p&gt;
&lt;p&gt;Vinny also provided an &lt;a class="external" href="https://gitlab.gnome.org/jrb/crosswords/-/merge_requests/416"&gt;MR for building bundles&lt;/a&gt; as part of the build process! I’d love to have bundles available to go with the flatpaks we create. However, I have neither a Mac to test on, nor the skills to evaluate this MR. &lt;strong&gt;I would deeply appreciate if anyone can help test and evaluate this!&lt;/strong&gt;&lt;/p&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_7807" style="width: 300px;"&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/Screenshot_2026-10-19_at_2.41.55_PM-scaled.png"&gt;&lt;img alt="" class="wp-image-7807 size-medium" height="211" src="https://blogs.gnome.org/jrb/files/2026/10/Screenshot_2026-10-19_at_2.41.55_PM-300x211.png" width="300"/&gt;&lt;/a&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-7807"&gt;Crosswords running on a Mac&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;Florian also did another build of Crosswords for Android and &lt;a class="external" href="https://cloud.gnome.org/s/2YHjSe7tD6dLspm"&gt;created another APK&lt;/a&gt;. It’s still pretty buggy, but it’s significantly better than the previous release. I think we can get it usable with a little more effort.&lt;/p&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_7823" style="width: 135px;"&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/android.jpg"&gt;&lt;img alt="" class="wp-image-7823 size-medium" height="300" src="https://blogs.gnome.org/jrb/files/2026/10/android-135x300.jpg" width="135"/&gt;&lt;/a&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-7823"&gt;Android Build&lt;/figcaption&gt;&lt;/figure&gt;
&lt;h2&gt;Other Features&lt;/h2&gt;
&lt;p&gt;A grab bag of the rest:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The metadata tab now has rich text editing throughout and was reorganized into a vertical layout.&lt;/li&gt;
&lt;li&gt;The  Language and Country rows let you set the puzzle’s $LANG and Charset. A new layer warns about letters that aren’t in the alphabet. It was shockingly complex to write.&lt;/li&gt;
&lt;/ul&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_7813" style="width: 300px;"&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/Screenshot-From-2026-10-19-18-18-43-border.png"&gt;&lt;img alt="" class="wp-image-7813 size-medium" height="93" src="https://blogs.gnome.org/jrb/files/2026/10/Screenshot-From-2026-10-19-18-18-43-border-300x93.png" width="300"/&gt;&lt;/a&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-7813"&gt;Rows for setting $LANG&lt;/figcaption&gt;&lt;/figure&gt;
&lt;ul&gt;
&lt;li&gt;Word lists now show synonyms in clue definitions.&lt;/li&gt;
&lt;/ul&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_7814" style="width: 300px;"&gt;&lt;a href="https://blogs.gnome.org/jrb/files/2026/10/Screenshot-From-2026-10-19-18-26-41-border.png"&gt;&lt;img alt="" class="wp-image-7814 size-medium" height="99" src="https://blogs.gnome.org/jrb/files/2026/10/Screenshot-From-2026-10-19-18-26-41-border-300x99.png" width="300"/&gt;&lt;/a&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-7814"&gt;Definition and synonyms of “RAISE”&lt;/figcaption&gt;&lt;/figure&gt;
&lt;ul&gt;
&lt;li&gt;The Editor preview window uses the real game widget.&lt;/li&gt;
&lt;li&gt;We enabled large text for printing. Toluwaleke did most of the work already a few releases back, it just needed a template.&lt;/li&gt;
&lt;li&gt;Added support for the Czech &lt;tt&gt;CH&lt;/tt&gt; digraph, mirroring the existing Dutch &lt;tt&gt;IJ&lt;/tt&gt; digraph.&lt;/li&gt;
&lt;li&gt;Laureen has been steadily working on a grid generator for vocab puzzles. None of it is visible yet — it’s all generator code — but it’s a solid basis for the next game type.&lt;/li&gt;
&lt;li&gt;I fixed a massive leak with all the &lt;tt&gt;PuzzleTasks&lt;/tt&gt;. Turns out we weren’t freeing them at all due to a ref loop. Not a big deal with the normal autofill behavior, but once we started running it every keypress the leak grew fast.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Thanks!&lt;/h2&gt;
&lt;p&gt;This release, thanks to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Rosanna for tireless help with UI word-smithing and editing, as well as endless patience.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;“Gnoman”&lt;/em&gt; for the amazing design for the revamped play mode, the animated SVGs, and general design support.&lt;/li&gt;
&lt;li&gt;Tobias for design support and advice throughout the Circle process.&lt;/li&gt;
&lt;li&gt;Florian for the port to GTK4’s new SVG widget and other fixes.&lt;/li&gt;
&lt;li&gt;Vinny for macOS input method support and the macOS arm64 CI job, and in general amazing build gardening.&lt;/li&gt;
&lt;li&gt;Michel for build and license advice.&lt;/li&gt;
&lt;li&gt;Laureen for continued work on the vocab editor.&lt;/li&gt;
&lt;li&gt;Federico for general advice.&lt;/li&gt;
&lt;li&gt;Alice for general advice, and for fixing my issues with libadwaita.&lt;/li&gt;
&lt;li&gt;Eleanor, Sophia, Michael, and Rosanna for puzzle play-testing &lt;em&gt;(coming soon!)&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Peace&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/jrb/2026/10/20/crosswords-0-3-19-new-layout-and-acrostic-editor/</guid>
      <pubDate>Tue, 20 Oct 2026 13:00:26 +0000</pubDate>
    </item>
    <item>
      <title>Flathub: Flathub Discourse is now read-only</title>
      <link>https://docs.flathub.org/blog/discourse-deprecation</link>
      <description>&lt;p&gt;As of today, &lt;a class="" href="https://discourse.flathub.org/" rel="noopener noreferrer" target="_blank"&gt;Flathub Discourse&lt;/a&gt; is read-only.
Existing threads stay available, but it is no longer possible to start new
topics or reply.&lt;/p&gt;
&lt;p&gt;We opened the forum &lt;a class="" href="https://barthalion.blog/a-forum-for-flathub/" rel="noopener noreferrer" target="_blank"&gt;back in 2020&lt;/a&gt; as a place for asynchronous
communication that isn't GitHub issues or IRC. Realistically, it never took
off, becoming another issue tracker to keep an eye on. A forum where people
post and wait for an answer that never comes is worse than no forum at all.&lt;/p&gt;
&lt;p&gt;Here's where to go instead:&lt;/p&gt;
&lt;ul&gt;
&lt;li class=""&gt;&lt;strong&gt;Help with packaging and submissions&lt;/strong&gt;: the &lt;a class="" href="https://matrix.to/#/#flathub:matrix.org" rel="noopener noreferrer" target="_blank"&gt;Flathub Matrix
channel&lt;/a&gt;, or the &lt;a class="" href="https://matrix.to/#/#flatpak:matrix.org" rel="noopener noreferrer" target="_blank"&gt;Flatpak channel&lt;/a&gt; for
questions about Flatpak itself.&lt;/li&gt;
&lt;li class=""&gt;&lt;strong&gt;Problems with an app&lt;/strong&gt;: the issue tracker of its repository, linked as
"Manifest" on the app's Flathub page. Issues with Flathub itself go to
&lt;a class="" href="https://github.com/flathub/flathub/issues" rel="noopener noreferrer" target="_blank"&gt;flathub/flathub&lt;/a&gt;.&lt;/li&gt;
&lt;li class=""&gt;&lt;strong&gt;App requests&lt;/strong&gt;: Flathub doesn't take them. Ask the app's developers to
&lt;a class="" href="https://docs.flathub.org/docs/for-app-authors/submission"&gt;submit it&lt;/a&gt;, or do it yourself.&lt;/li&gt;
&lt;li class=""&gt;&lt;strong&gt;Runtime announcements&lt;/strong&gt;: runtime projects such as freedesktop-sdk are
welcome to post them on this blog.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Thanks to everyone who answered questions there over the years.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://docs.flathub.org/blog/discourse-deprecation</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>This Week in GNOME: #271 Good News</title>
      <link>https://thisweek.gnome.org/posts/2026/10/twig-271/</link>
      <description>&lt;p&gt;Update on what happened across the GNOME project in the week from October 16 to October 23.&lt;/p&gt;
&lt;h2 id="gnome-circle-apps-and-libraries"&gt;GNOME Circle Apps and Libraries&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/6a980031a26d87453f03a74d5423c26fc88007d29a4ccd0523a7e973406bc24c"&gt;Jan Lukas&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Newsflash 6.0 beta is available&lt;/p&gt;
&lt;p&gt;Lots of internal changes to clean up caches, improve performance, lower peak memory consumption, avoid crashes.
If you’re looking for user visible changes there is&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Pdf Export using Typst&lt;/li&gt;
&lt;li&gt;A new article list layout with larger thumbnails (the old layout is still available)&lt;/li&gt;
&lt;li&gt;A re-designed article view menu (thanks Tobias Bernard)&lt;/li&gt;
&lt;li&gt;Much improved Gtk HTML view&lt;/li&gt;
&lt;li&gt;Its now possible to continue listening to a podcast while browsing other content&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Lots of other goodies in the &lt;a href="https://gitlab.com/news-flash/news_flash_gtk/-/blob/main/data/io.gitlab.news_flash.NewsFlash.appdata.xml.in.in?ref_type=heads#L63"&gt;complete changelog&lt;/a&gt;. Check it out on the flathub beta channel.&lt;/p&gt;
&lt;p&gt;&lt;img height="1530" src="https://thisweek.gnome.org/_astro/QyhRpOEDHuXOVKYCkEMCCybw_Pastedimage.BtxKwWlR_ZHnaUh.webp" width="1868"/&gt;
&lt;/p&gt;
&lt;p&gt;&lt;img height="1466" src="https://thisweek.gnome.org/_astro/GxhWdriBlyPnWRgsrNPFUXLB_Dark.DnD3FOfN_1V2fTS.webp" width="2394"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="1466" src="https://thisweek.gnome.org/_astro/QZYXxWSUfnVqccbgsrHBunMV_Podcast.Dj1IP6LF_Z2dWXn5.webp" width="1858"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="gnome-core-apps-and-libraries"&gt;GNOME Core Apps and Libraries&lt;/h2&gt;
&lt;h3 id="gtk-"&gt;GTK &lt;a href="https://gitlab.gnome.org/GNOME/gtk"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Cross-platform widget toolkit for creating graphical user interfaces.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/367605ee3f1609c560f4c630be71e4f6e5769036f91a37e2abd06c3fafa30ac0"&gt;Felix&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This week, my first contributions to GTK were merged!&lt;/p&gt;
&lt;p&gt;GTK now &lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10380"&gt;implements&lt;/a&gt; the &lt;a href="https://developer.apple.com/documentation/appkit/nsapplicationdelegate/applicationshouldhandlereopen(_:hasvisiblewindows:)"&gt;&lt;code&gt;applicationShouldHandleReopen:hasVisibleWindows:&lt;/code&gt;&lt;/a&gt; delegate method on macOS. This method gets called when an app that is already running gets reactivated, for example when the user clicks its dock icon again, double-clicks the app in Finder, or clicks on the media controls in control center. This is important for apps that keep running after their window has been closed. A typical use case is a music player that continues playback in the background. Before this, reactivating such an app gave it no chance to respond, so there was no way to bring the window back. Now, the &lt;code&gt;GtkApplication&lt;/code&gt; now receives the &lt;code&gt;activate&lt;/code&gt; signal, just as it does on GNOME when an already running application gets launched again. Apps that already handle &lt;code&gt;activate&lt;/code&gt; by presenting or recreating their main window will get the expected behavior on macOS now as well without any platform-specific code.&lt;/p&gt;
&lt;p&gt;The second contribution is a &lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10381"&gt;small fix&lt;/a&gt;, which solves an issue that the native “traffic lights” controls (close, minimize and zoom) stayed visible, even when the window had asked for no window buttons to be shown.&lt;/p&gt;
&lt;p&gt;Maybe some of you can guess which app needed these fixes :)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="web-"&gt;Web &lt;a href="https://gitlab.gnome.org/GNOME/epiphany"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Web browser for the GNOME desktop.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/c100c9b389d534f2cb1c127af169fcc7c8068a1d4eddd38ca0f0d823f67177fb"&gt;adrian&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;A long-standing bug that caused the “unresponsive page” dialog to reappear forever when the page became responsive again while the dialog was shown &lt;a href="https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/2220"&gt;has been fixed&lt;/a&gt;. As an additional refinement, the dialog &lt;a href="https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/2236"&gt;will be closed automatically&lt;/a&gt; if WebKit reports that the page starts responding again.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="third-party-projects"&gt;Third Party Projects&lt;/h2&gt;
&lt;h3 id="fractal-"&gt;Fractal &lt;a href="https://gitlab.gnome.org/World/fractal"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Matrix messaging app for GNOME written in Rust.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/0bba5024ecb1c0c920590af124326a5643b54a4fbb247822d88077e3636ddac0"&gt;Kévin Commaille&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Several upstream dependencies released security fixes so we bundled them into Fractal 14.2 to make sure that everything runs smoothly until the next release!&lt;/p&gt;
&lt;p&gt;This version is available right now on &lt;a href="https://flathub.org/apps/org.gnome.Fractal"&gt;Flathub&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As usual, you can also help make sure the next major version is solid by using &lt;a href="https://gitlab.gnome.org/World/fractal#development-version"&gt;Fractal Nightly&lt;/a&gt;. Help on fixing &lt;a href="https://gitlab.gnome.org/World/fractal/-/issues/?label_name%5B%5D=1.%20Bug"&gt;our remaining bugs&lt;/a&gt; is of course always appreciated!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="solitaire-"&gt;Solitaire &lt;a href="https://gitlab.gnome.org/wwarner/Solitaire"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Play Patience Games&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/9d1ec84ce44929354b3a4ae336781b776cf26af387dbb7983b76a1143cb8d10d"&gt;Will Warner&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Solitaire 51.1 is out!
Here is what’s new:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added the Hungarian translation&lt;/li&gt;
&lt;li&gt;Updated translations: Slovenian, Ukrainian, Kazakh, Swedish&lt;/li&gt;
&lt;li&gt;Made the game centered vertically&lt;/li&gt;
&lt;li&gt;Made double-pressing move cards to the waste in Tri-Peaks&lt;/li&gt;
&lt;li&gt;Added a deletion button for unfinished games&lt;/li&gt;
&lt;li&gt;Made the card placeholder darker in the light theme&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/744734bb9e24ac02bccfabf509071b840f3b337cc1c8cc532708218ae1a33af2"&gt;Jan-Michael Brummer&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Saldo 0.9.0 is now available. Saldo is a FinTS banking application that connects to your bank and displays your balances and transactions.&lt;/p&gt;
&lt;p&gt;This release modernises the application’s user interface with current libadwaita widgets and redesigns the account creation, transfer, category and settings dialogs for a more consistent experience. It also introduces an option to reset the database, updates the FinTS bank database, and resolves several issues affecting background operation, password changes and account refreshing. Available at Flathub: &lt;a href="https://flathub.org/de/apps/org.tabos.saldo"&gt;https://flathub.org/de/apps/org.tabos.saldo&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;&lt;img height="690" src="https://thisweek.gnome.org/_astro/QJdHRgzrFORntRAGDRmQEleE_saldo-twig.l2yejTp-_1LjnGk.webp" width="1074"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/65e32ad306958fae73f6a8e9aefb6a43ae58ea5d70b79d274425529fede25a47"&gt;dabrain34&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;🎉 New Release Announcement: GstPipelineStudio v0.7.1 🎉&lt;/p&gt;
&lt;p&gt;GstPipelineStudio version 0.7.1 is out! This bugfix release refreshes the application icon, now drawn in the GStreamer colors, and makes pipeline import keep the links to pads created at runtime.&lt;/p&gt;
&lt;p&gt;What’s new in 0.7.1:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Application icon redrawn in the GStreamer red, green and blue, with the node graph running right to left&lt;/li&gt;
&lt;li&gt;Importing a gst-launch description keeps links to pads that only appear at runtime (urisourcebin, demuxer outputs)&lt;/li&gt;
&lt;li&gt;Big Buck Bunny preset switched to the AV1/Opus sample&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Highlights of the 0.7.x series:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New application icon&lt;/li&gt;
&lt;li&gt;Nodes colored by type: source, transform, sink&lt;/li&gt;
&lt;li&gt;Swap a node for an alternative element from its context menu&lt;/li&gt;
&lt;li&gt;Tags tab listing tags from bus messages&lt;/li&gt;
&lt;li&gt;Sortable columns in the element and pipeline lists&lt;/li&gt;
&lt;li&gt;Suggestions reuse a compatible free element already in the graph&lt;/li&gt;
&lt;li&gt;Space bar toggles play/pause, s stops the pipeline&lt;/li&gt;
&lt;li&gt;Explicit properties are kept when importing a pipeline&lt;/li&gt;
&lt;li&gt;German translation added&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Participants:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Stéphane Cerveau — maintainer and main contributor&lt;/li&gt;
&lt;li&gt;Translations contributed through &lt;a href="https://hosted.weblate.org/projects/gstpipelinestudio/"&gt;Weblate&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;🚀 Upgrade Now!&lt;/p&gt;
&lt;p&gt;To get the latest version of GstPipelineStudio, visit the project’s &lt;a href="https://gps.mooday.dev"&gt;page&lt;/a&gt; and check out the &lt;a href="https://gitlab.freedesktop.org/dabrain34/GstPipelineStudio/-/blob/main/ChangeLog.md"&gt;Changelog&lt;/a&gt; for more details.&lt;/p&gt;
&lt;p&gt;Happy streaming! 🎬📡
&lt;/p&gt;
&lt;p&gt;&lt;img height="1370" src="https://thisweek.gnome.org/_astro/TTqhZVJIPawkjjqBTCfiXPOd_gps_screenshot.DTkjNm6X_Z2d5AKy.webp" width="2560"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="shell-extensions"&gt;Shell Extensions&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/4d35df9867c6cb56c7863c86310e26c73e90bc6edd3c4af320824ca5ed41c191"&gt;storageb&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Create your own Quick Settings toggle buttons!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://storageb.github.io/custom-command-toggle/"&gt;Custom Command Toggle&lt;/a&gt; lets you add fully customizable toggle buttons to the Quick Settings menu. Turn shell commands, services, or your own scripts into toggles integrated directly into the GNOME panel.&lt;/p&gt;
&lt;p&gt;Key Features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Run commands or launch scripts from toggle buttons&lt;/li&gt;
&lt;li&gt;Configure initial toggle states and startup behavior&lt;/li&gt;
&lt;li&gt;Create custom dropdown menus from toggle buttons&lt;/li&gt;
&lt;li&gt;Synchronize toggle states with a command’s output&lt;/li&gt;
&lt;li&gt;Assign keyboard shortcuts to buttons&lt;/li&gt;
&lt;li&gt;Import and export button configurations&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The latest release adds support for creating dropdown menus on toggle buttons to run additional commands, adding even more functionality to your toggling experience. Italian, Dutch, and French translations have been added thanks to some contributions from the community. Other improvements include some under the hood bug fixes and performance improvements.&lt;/p&gt;
&lt;p&gt;The extension is available on &lt;a href="https://extensions.gnome.org/extension/7012/custom-command-toggle/"&gt;GNOME Extensions&lt;/a&gt;. For more information, see the &lt;a href="https://storageb.github.io/custom-command-toggle/"&gt;documentation&lt;/a&gt;.

&lt;/p&gt;
&lt;p&gt;&lt;img height="723" src="https://thisweek.gnome.org/_astro/tQHyQyzKnLAEHcENMkPnvcSU_custom-command-toggle-2.DyyZjAuI_OYzcD.webp" width="690"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="402" src="https://thisweek.gnome.org/_astro/PhsCppSBOsZlWuzTnaRawEQl_custom-command-toggle-1.PAiAT5U8_2hR01M.webp" width="400"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="events"&gt;Events&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/1aa2677b05d3d2d049b067c78b72357523eb5f07aa595d2ce3de841fcc88b9eb"&gt;Daniel Galleguillos Cruz&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;GNOME Latam 2026: Call for Participation&lt;/p&gt;
&lt;p&gt;We’re excited to announce GNOME Latam 2026, the regional gathering of the GNOME community in Latin America!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Dates: November 12–14, 2026&lt;/li&gt;
&lt;li&gt;Venue: Universidad Anáhuac Mayab, Mérida, Yucatán, Mexico&lt;/li&gt;
&lt;li&gt;Format: Hybrid (in-person sessions with online streaming and remote participation)&lt;/li&gt;
&lt;li&gt;Event page &amp;amp; registration: &lt;a href="https://events.gnome.org/e/latam2026"&gt;https://events.gnome.org/e/latam2026&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="about-the-event"&gt;About the Event&lt;/h4&gt;
&lt;p&gt;GNOME Latam 2026 brings together developers, system administrators, educators, designers, and open source enthusiasts from across Latin America. Building on previous regional collaborations, including our work with CCOSS, the event is more than a conference: it’s a community effort to grow, empower, and sustain the GNOME ecosystem in the region.&lt;/p&gt;
&lt;p&gt;The program will include keynotes, technical workshops, panel discussions, and networking sessions, both in person and online. Our goal is to share knowledge and build lasting collaboration across borders.&lt;/p&gt;
&lt;h4 id="our-mission"&gt;Our Mission&lt;/h4&gt;
&lt;p&gt;To drive the adoption, development, and sustainability of GNOME and its software ecosystem in Latin America, while promoting the core values of free software: freedom, collaboration, openness, and transparency.&lt;/p&gt;
&lt;p&gt;We believe access to technology should be universal, and that diverse perspectives, from experienced contributors to newcomers joining through community initiatives like CCOSS, are essential to inclusive innovation.&lt;/p&gt;
&lt;h4 id="goals"&gt;Goals&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Outreach: Showcase the latest developments, roadmaps, and releases in the GNOME ecosystem.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Learning: Offer sessions for everyone, from users getting started with free software to developers who want to contribute code, design, or QA to GNOME.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Regional community: Strengthen the network of free software communities in Latin America through mentorship and collaboration with partners such as CCOSS.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Accessibility and inclusion: Use a hybrid format to remove geographic barriers and welcome participants from all backgrounds.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="get-involved"&gt;Get Involved&lt;/h4&gt;
&lt;p&gt;Code of Conduct: All in-person and online activities follow the &lt;a href="https://conduct.gnome.org"&gt;GNOME Code of Conduct&lt;/a&gt; to ensure a safe, respectful, and harassment-free environment for everyone.&lt;/p&gt;
&lt;p&gt;We hope to see you in Mérida or online!&lt;/p&gt;
&lt;p&gt;GNOME Latam Team
latam@gnome,org&lt;/p&gt;
&lt;p&gt;&lt;img height="383" src="https://thisweek.gnome.org/_astro/GNOME_Latam_2026_2.CNaporoX_2gGwqr.webp" width="950"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="thats-all-for-this-week"&gt;That’s all for this week!&lt;/h2&gt;
&lt;p&gt;See you next week, and be sure to stop by &lt;a href="https://matrix.to/#/#thisweek:gnome.org"&gt;#thisweek:gnome.org&lt;/a&gt; with updates on your own projects!&lt;/p&gt;</description>
      <guid isPermaLink="false">https://thisweek.gnome.org/posts/2026/10/twig-271/</guid>
      <pubDate>Fri, 23 Oct 2026 19:59:27 +0000</pubDate>
    </item>
    <item>
      <title>Sam Thursfield: 25th October 2026</title>
      <link>https://samthursfield.wordpress.com/2026/10/25/25th-october-2026/</link>
      <description>&lt;p class="wp-block-paragraph"&gt;Hello,&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I started this blog 22 years ago now (I don’t recommend going back to the start), and for the last 5 years I wrote a monthly “status update” post, aiming to mainly write about interesting stuff I might have done in the world of open source software, which I hoped in turn would motivate me to do more interesting stuff in open source software.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;The world changed a lot in that time. If I started now this would probably be a podcast with 16 listeners, instead of being a WordPress blog with 16 subscribers. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I’ve spent a lot of time this year reading and thinking about the impact of large language models on the tech industry and open source. Its interesting because this feels like the moment, whether we like it or not, hacker culture goes mainstream. This week the world’s major news outlets had to figure out what PHP is.&lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;a href="https://samthursfield.wordpress.com/wp-content/uploads/2026/10/image.png"&gt;&lt;img alt="Clip of BBC website. Text: &amp;quot;Cyber correspondent Joe Tidy says he didn't know PHP existed until yesterday morning -- it's &amp;quot;one of those things we take for granted&amp;quot;, he says." class="wp-image-3718" height="839" src="https://samthursfield.wordpress.com/wp-content/uploads/2026/10/image.png?w=1024" width="1024"/&gt;&lt;/a&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;That the BBC’s cyber correspondent didn’t know PHP existed has caused some joking and debate online. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;24 years ago I was figuring out what PHP is. Jonathan Atkinson, who I met in a &lt;a href="https://noop.rocks/gdr/"&gt;forum&lt;/a&gt; that was nominally about writing video games in QBASIC, asked me to make a wiki in PHP. So I did.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;All I knew about wikis was that, it’s like a regular website except anyone can edit it. I named the project: &lt;em&gt;Wiki!&lt;/em&gt; Here’s a quote from the README:&lt;br/&gt;&lt;br/&gt;&lt;/p&gt;
&lt;div class="wp-block-code"&gt;
&lt;div class="cm-editor"&gt;
&lt;div class="cm-scroller"&gt;
&lt;pre&gt;
&lt;code&gt;&lt;div class="cm-line"&gt;How do I install it?&lt;/div&gt;&lt;div class="cm-line"&gt;It's best run in its own directory. Create it one. You'll also want a directory for nodes,&lt;/div&gt;&lt;div class="cm-line"&gt;or you could keep them in the base wiki dir. Either way, the nodes directory has to be&lt;/div&gt;&lt;div class="cm-line"&gt;chmod'ed to 777.&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p class="wp-block-paragraph"&gt;You might raise your eyebrows at that comment if you aren’t yourself a teenage hacker discovering web development.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;&lt;em&gt;Wiki! &lt;/em&gt;did have a login system, and the passwords were even stored as MD5 hashes rather than plain text, as I heard that was good practice. In hindsight, an attacker who knew how to set the HTTP &lt;code&gt;Cookie&lt;/code&gt; header could impersonate anyone, like this: &lt;code&gt;Cookie: wikiticket=admin&lt;/code&gt;. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Here is a snippet of the file &lt;code&gt;edit.php&lt;/code&gt;. Note that &lt;code&gt;$node&lt;/code&gt; and &lt;code&gt;$title&lt;/code&gt; are inputs you can set via a POST request, or even via URL parameters like &lt;code&gt;edit.php?title="/etc/passwd"&lt;/code&gt;:&lt;br/&gt;&lt;br/&gt;&lt;/p&gt;
&lt;div class="wp-block-code"&gt;
&lt;div class="cm-editor"&gt;
&lt;div class="cm-scroller"&gt;
&lt;pre&gt;
&lt;code&gt;&lt;div class="cm-line"&gt;$t=$title;&lt;/div&gt;&lt;div class="cm-line"&gt;if ($node) {&lt;/div&gt;&lt;div class="cm-line"&gt;&lt;/div&gt;&lt;div class="cm-line"&gt;	// Write new data&lt;/div&gt;&lt;div class="cm-line"&gt;	//&lt;/div&gt;&lt;div class="cm-line"&gt;	$file=fopen($nodedir.$t.".wiki", "w+");&lt;/div&gt;&lt;div class="cm-line"&gt;	$node=stripslashes(ereg_replace("(\r\n|\n|\r)","&amp;lt;br&amp;gt;", $node));	// Linebreak to &amp;lt;br&amp;gt;&lt;/div&gt;&lt;div class="cm-line"&gt;	fputs($file, $node."\n");&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p class="wp-block-paragraph"&gt;Even if you just learned what PHP is today, you might see that this is not an entirely secure design. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Anyway, at the time I was proud of my work, and I needed somewhere to host it. So, as you would in 2002, I registered the name “wiki” on sourceforge.net and uploaded the project code. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Sourceforge, for those who haven’t yet reached middle age, was the 2000’s equivalent of Github. It allowed projects to have their own website, as long as they included the Sourceforge logo somewhere, and the website could use PHP. Perfect, I thought, the project’s website will be a wiki!&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Looking back now through archive.org, I can see this code actually ran in public for many years. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Here it is around launch day in 2002: &lt;a href="https://web.archive.org/web/20021012080349/http://wiki.sourceforge.net/wiki"&gt;https://web.archive.org/web/20021012080349/http://wiki.sourceforge.net/wiki&lt;/a&gt;&lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;a href="https://samthursfield.wordpress.com/wp-content/uploads/2026/10/image-1.png"&gt;&lt;img alt="Screenshot of archive.org link above" class="wp-image-3728" height="585" src="https://samthursfield.wordpress.com/wp-content/uploads/2026/10/image-1.png?w=1024" width="1024"/&gt;&lt;/a&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;I have a local copy from around this time, which includes &lt;code&gt;indexjon.wiki&lt;/code&gt;:&lt;br/&gt;&lt;br/&gt;&lt;/p&gt;
&lt;pre class="wp-block-code"&gt;&lt;code&gt;
Sam, there are some serious bugs in this wiki. I keep on getting 'document contains no data' errors; get me on AIM.

Welcome to grove.swoo.net. You may or may not be interested in the [weblog].
JonathanA - 29/8/02 - 11:36 am
JonathanA - 29/8/02 - 07:36 am&lt;/code&gt;&lt;/pre&gt;
&lt;p class="wp-block-paragraph"&gt;&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Those bugs went unfixed forever, and six months later, the front page text had been replaced with two poems, one in Italian and one in Russian: &lt;a href="https://web.archive.org/web/20030420205758/http://wiki.sourceforge.net"&gt;https://web.archive.org/web/20030420205758/http://wiki.sourceforge.net&lt;/a&gt;&lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;a href="https://samthursfield.wordpress.com/wp-content/uploads/2026/10/image-3.png"&gt;&lt;img alt="Shot of above archive.org link" class="wp-image-3735" height="581" src="https://samthursfield.wordpress.com/wp-content/uploads/2026/10/image-3.png?w=1024" width="1024"/&gt;&lt;/a&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;One is &lt;em&gt;“Non chiederci la parola che squadri da ogni lato”&lt;/em&gt; by Eugenio Montale, written in 1923, and presumably posted by a fan. Does anyone know what it’s about? A machine translation suggests it might discuss “the crisis of certainty faced by contemporary man”. The other is &lt;a href="https://www.online-literature.com/wordsworth/2217/"&gt;“Anecdote for Fathers” by William Wordsworth&lt;/a&gt;, in Russian via an unnamed translator.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Let’s just sit with that for a moment. Imagine what happens in 2026 if a trivially exploitable PHP website hosted by a US corporation goes online: it’ll be mining bitcoin, serving pornography and drowning in racist and antisemitic spam, probably all within the same day.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;In 2003, over the course of six months, my naive implementation of a wiki was gifted with… two rather thoughtful poems.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Fast forward another year. I was about to turn 18 years old, was studying for A levels and mostly concerned with hanging out in the park drinking cheap cider and learning to play the guitar. I was certainly &lt;em&gt;not&lt;/em&gt; thinking about this rather flawed chunk of PHP code that I’d written two years earlier, but via the magic of archive.org we can see that various people were genuinely trying to use it as a wiki: &lt;a href="https://web.archive.org/web/20041121113508/http://wiki.sourceforge.net"&gt;https://web.archive.org/web/20041121113508/http://wiki.sourceforge.net&lt;/a&gt;&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;&lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;a href="https://samthursfield.wordpress.com/wp-content/uploads/2026/10/image-2.png"&gt;&lt;img alt="Screenshot of archive.org link above" class="wp-image-3732" height="976" src="https://samthursfield.wordpress.com/wp-content/uploads/2026/10/image-2.png?w=1024" width="1024"/&gt;&lt;/a&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;In hindsight, perhaps it attracted so much attention because I’d literally taken the subdomain: &lt;a href="http://wiki.sourceforge.net/" rel="nofollow"&gt;http://wiki.sourceforge.net/&lt;/a&gt;, unintentionally boosting the SEO reach quite a bit. The site was still active &lt;a href="https://web.archive.org/web/20070128173022/http://wiki.sourceforge.net"&gt;right up until 2007&lt;/a&gt;.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I can’t find it now, but I do remember receiving an email at some point from sourceforge.net noting that they’d taken down the wiki! website after discovering it was a major security risk. And at some point they must have (quite reasonably) reclaimed the project name as well, since &lt;a href="http://sourceforge.net/projects/wiki"&gt;http://sourceforge.net/projects/wiki&lt;/a&gt; no longer exists.  It will always live on in my heart, though, and for the moment at: &lt;a href="https://web.archive.org/web/20021014172056/http://sourceforge.net/projects/wiki/"&gt;https://web.archive.org/web/20021014172056/http://sourceforge.net/projects/wiki/&lt;/a&gt;&lt;/p&gt;
&lt;hr class="wp-block-separator has-alpha-channel-opacity"/&gt;
&lt;p class="wp-block-paragraph"&gt;The world has changed significantly since I was a teenage hacker. Some of what I learned in those days is completely obsolete, such as the QBASIC programming language and VGA graphics. I am a &lt;a href="http://www.petesqbsite.com/sections/tutorials/zines/qbcm/6-fonts.html"&gt;world expert&lt;/a&gt; in these irrelevant topics.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Other stuff that I picked up in the early 2000s has become the foundation of my career as an operating systems developer: C programming, Linux distributions and an gradual induction into open source desktop world via &lt;a href="https://planet.gnome.org/"&gt;Planet GNOME&lt;/a&gt;. And good old PHP, of course. Who knew that, a quarter way through the 21st century, PHP would be &lt;em&gt;&lt;a href="https://www.theguardian.com/technology/2026/oct/21/flaw-in-php-computer-language-leads-to-shutdown-of-websites-around-world"&gt;front page news&lt;/a&gt;&lt;/em&gt;?&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Age 18, I didn’t tell anyone in the real world that I’d written a wiki because it’d be the first time they’d &lt;em&gt;heard&lt;/em&gt; the word “wiki”. The word evoked exotic and mysterious feelings of Hawaii in 2002. Now it universally evokes Wikipedia. People are learning about password hygiene and PHP. The arrival of AI on the scene, to me, fits into this bigger picture that began in the last century: we, the Computer People, are becoming Mainstream.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://samthursfield.wordpress.com/2026/10/25/25th-october-2026/</guid>
      <pubDate>Sun, 25 Oct 2026 14:30:49 +0000</pubDate>
    </item>
    <item>
      <title>Hylke Bons: 1,447 emoji? We'll do it live</title>
      <link>https://planetpeanut.studio/post/2026/10/27/pidgin-emoji-twitch</link>
      <description>&lt;p&gt;One of the things you get to do after being &lt;a href="https://planetpeanut.studio/post/2026/06/13/hello-again-planet-gnome"&gt;laid off&lt;/a&gt; is a lot of reflection, but also to revisit all the old projects you used to contribute to.&lt;/p&gt;
&lt;p&gt;One of them was &lt;a href="https://pidgin.im"&gt;Pidgin&lt;/a&gt;: &lt;strong&gt;“the universal chat client”&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;br/&gt;&lt;/p&gt;
&lt;figure&gt;
&lt;a href="https://twitch.tv/planet_peanut_studio"&gt;
&lt;img src="https://planetpeanut.studio/assets/img/posts/pidgin-emoji-twitch.png"/&gt;
&lt;/a&gt;
&lt;figcaption&gt;The new Pidgin 3 app icon and a handful emoji&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;I designed the original emoticon set for version 2 and helped redesign the user interface when the project was renamed from &lt;strong&gt;Gaim&lt;/strong&gt; after a &lt;a href="https://en.wikipedia.org/wiki/Pidgin_(software)"&gt;legal dispute&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Meanwhile, after a &lt;a href="https://www.twitch.tv/rw_grim"&gt;huge rewrite&lt;/a&gt;, &lt;strong&gt;Pidgin 3&lt;/strong&gt; is making progress &lt;a href="https://discourse.imfreedom.org/t/pidgin-3-0-experimental-2-2-91-0-has-been-released/262"&gt;towards a first release&lt;/a&gt; and I’ve been helping out here and there with a new &lt;a href="https://planetpeanut.studio/icons#Pidgin"&gt;app icon&lt;/a&gt; and some &lt;a href="https://mastodon.social/@hbons/117338801380410565"&gt;status symbols&lt;/a&gt; for the development releases.&lt;/p&gt;
&lt;h2 id="emoji"&gt;Emoji&lt;/h2&gt;
&lt;p&gt;I’ve been meaning to start live streaming my &lt;a href="https://planetpeanut.studio/icons"&gt;weekly app icon&lt;/a&gt; work to share a look in the kitchen of the icon design process, but once I gathered the courage to start a test run, the experience wasn’t amazing.&lt;/p&gt;
&lt;p&gt;I need something I can return to consistently without needing a new plan every time…&lt;/p&gt;
&lt;p&gt;So why not create a base set of &lt;a href="https://en.wikipedia.org/wiki/List_of_emojis"&gt;1,447 emoji&lt;/a&gt; for Pidgin in &lt;a href="https://developer.gnome.org/hig/guidelines/app-icons.html"&gt;GNOME&lt;/a&gt;-style exclusively &lt;strong&gt;live on stream&lt;/strong&gt;? What could go wrong?&lt;/p&gt;
&lt;p&gt;Here’s the &lt;a href="https://www.figma.com/design/EZt7Rt0KKdzXVtga8pB2in"&gt;design file&lt;/a&gt; to keep me accountable, so I can’t sneakily make progress offline!&lt;/p&gt;
&lt;h2 id="twitch"&gt;Twitch&lt;/h2&gt;
&lt;p&gt;I’ll be chipping away at it a few times a week. Follow me &lt;a href="https://twitch.tv/planet_peanut_studio"&gt;on Twitch&lt;/a&gt; to get a notification when I go live. We’ll grab a cup of tea, put on some music, and get through the winter.&lt;/p&gt;
&lt;p&gt;If you want to support my design work for Free and Open Source projects, I’m always looking for more &lt;a href="https://planetpeanut.studio/sponsors"&gt;sponsors&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Or a “&lt;a href="https://planetpeanut.studio/sponsors"&gt;sub&lt;/a&gt;” as the kids call it these days.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://planetpeanut.studio/post/2026/10/27/pidgin-emoji-twitch</guid>
      <pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Justin Wheeler: DevConf US 2026: Lessons Learned About Reaching Students in Open Source &amp; Linux</title>
      <link>https://jwheel.org/blog/2026/10/devconf-us-2026/</link>
      <description>&lt;img alt="DevConf US 2026: Lessons Learned About Reaching Students in Open Source &amp;amp;amp; Linux" src="https://jwheel.org/blog/2026/10/devconf-us-2026.jpg"/&gt;&lt;div class="paragraph"&gt;
&lt;p&gt;Walking up to the Fedora &amp;amp; CentOS booth on the first day of DevConf US in Boston, I was not quite sure what to expect.
Although I have attended the Czech Republic variant of DevConf several times, this was my first time attending the US event.
I was there as part of Red Hat’s joint &lt;a href="https://jwheel.org/categories/fedora/"&gt;Fedora&lt;/a&gt; and CentOS community presence.
What I found over those two days was not just a chance to hand out stickers and talk to Fedora Linux users.
It was a useful reminder in what the Fedora event strategy needs to become.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="context"&gt;The setting: Red Hat tech on a university campus &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#context"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;&lt;a href="https://www.devconf.info/us/"&gt;DevConf US&lt;/a&gt; is a community conference focused on developers and &lt;a href="https://jwheel.org/categories/red-hat/"&gt;Red Hat&lt;/a&gt; technologies.
Being held on the Boston University campus during the academic semester meant we knew we would see students.
What I did not fully anticipate was how the increased student presence here would reshape what I thought our booth should accomplish.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Alongside my colleagues Shaun McCance, Matthew Miller, Amy Marrich, and To Hung Sze, we staffed a joint Fedora and CentOS table.
We kept the booth table light, compared to other events.
We did not have any laptop demos, elaborate staging, or any fancy technical displays.
We brought ourselves and our trusty &lt;a href="https://docs.fedoraproject.org/en-US/mindshare-committee/events/boxes/united-states/"&gt;Pelican event box&lt;/a&gt; full of stickers, lanyards, pins, and swag.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="ubuntu-generation"&gt;Meeting the "Ubuntu is Linux" generation &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#ubuntu-generation"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Most people who stopped by the table already knew Fedora, or at least recognized the logo.
Most were students, but not all.
We also met faculty members, industry professionals, and contributors to other open source projects.
However, there was an unmistakable pattern among the students who approached us.
For nearly all of them, their first real exposure to Linux happened in university computer science labs.
And in university labs, Ubuntu is almost universally the default.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;For these students, Ubuntu was not simply a distribution preference.
For them, Ubuntu &lt;em&gt;was&lt;/em&gt; Linux.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;What surprised me most was that they were not defensive about it.
They were genuinely curious.
They wanted to understand what else was out there, how different systems fit together, and why alternative distributions mattered.
The subsequent conversations with those students are some of the most interesting, fun conversations to have at a Fedora booth.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="mouth-of-the-river"&gt;Upstream at the mouth of the river &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#mouth-of-the-river"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;That curiosity opened the door to talk about Fedora’s foundational place in the broader Linux ecosystem.
When you use Fedora, you are standing directly at the upstream source of enterprise Linux &lt;em&gt;everywhere&lt;/em&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;For the curious, the pitch goes something like this.
Every three years, Fedora branches to become the foundation for CentOS Stream, which in turn feeds directly into Red Hat Enterprise Linux (RHEL).
However, the reach does not stop with Red Hat products, which is often unknown to most students.
Downstream enterprise rebuilds like AlmaLinux and Rocky Linux trace their lineage back through CentOS Stream to Fedora.
Furthermore, hyperscalers stand out as interesting downstream operating systems too.
For example, Amazon Linux is derived from Fedora Linux.
And this year, Microsoft announced that &lt;a href="https://github.com/microsoft/azurelinux"&gt;Azure Linux&lt;/a&gt;, their custom hypervisor container OS, will base its future architecture on Fedora.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;So, when you study and use Fedora, you are not just learning another distribution.
You are standing at the mouth of the river.
You see the innovations before they flow into every major cloud provider and enterprise datacenter in the world.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="career-conversations"&gt;The missing on-ramp &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#career-conversations"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The students understood that value proposition immediately.
They grasped the architectural power of being upstream.
However, the conversations that truly resonated were not about packaging flags or kernel versions.
They were about careers.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Students were asking how to build practical skills, how to level up beyond coursework, and what industry engineering teams actually look for.
A handful asked specifically about how to contribute to open source and get involved with Fedora.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;That is where I realized what our booth was missing.
&lt;strong&gt;We had no clear call to action&lt;/strong&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;We could explain the architecture, and we could illustrate the ecosystem on a whiteboard, but we could not smoothly shepherd someone from curiosity to contribution.
We lacked a concrete on-ramp.
We had no printed guide explaining the first three steps to take after leaving the venue.
We had no five-minute interactive exercise someone could complete right at the table to earn something tangible.
Instead, we offered a sprawling overview of "everything you can do in Fedora," which is paralyzing when you are just getting started.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="earning-a-stake"&gt;What hackathons taught me about student engagement &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#earning-a-stake"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Years ago, as a student &lt;a href="https://jwheel.org/tags/rochester-institute-of-technology/"&gt;at RIT&lt;/a&gt; and a Fedora Ambassador, I staffed more than a few Fedora booths at collegiate hackathons like &lt;a href="https://jwheel.org/blog/2016/10/hackmit-meets-fedora/"&gt;HackMIT&lt;/a&gt; and &lt;a href="https://jwheel.org/blog/2016/04/bitcamp-2016/"&gt;Bitcamp&lt;/a&gt;.
Back then, I learned a vital lesson about engaging students: they need hands-on, achievable activities.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Students need something doable, self-contained, and repeatable.
Most importantly, they need something they can &lt;strong&gt;earn&lt;/strong&gt;.
A unique reward, like an event badge or a milestone achievement, creates an enduring memory.
A standard sticker gets lost in a backpack; a challenge you solved at a booth creates a personal reason to stay connected to the community.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="modernized-playbook"&gt;Modernizing our student event strategy &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#modernized-playbook"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Executing a commercial trade-show booth strategy at a student-heavy venue does not work.
Commercial attendees often browse passively for vendor solutions; students are actively planning their futures and want to understand how distributed engineering collaboration functions in the real world.
Free Software and open source are precisely that, but we have to frame them to meet their goals.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;If we want to translate curiosity into long-term community contributors, our playbook needs three tangible upgrades:&lt;/p&gt;
&lt;/div&gt;
&lt;div class="ulist"&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Tailored on-ramp materials&lt;/strong&gt;:
Brief, well-structured guides that explain what our sub-projects do and provide clear first tasks for beginners.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Audience-specific talking points&lt;/strong&gt;:
Equipping booth ambassadors with prompts geared toward early-career engineers, highlighting the practical career value of public upstream contributions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Interactive booth challenges&lt;/strong&gt;:
Short, five-minute exercises that allow attendees to make a small contribution, file a test ticket, or solve a puzzle right at the table.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;So, should Fedora &amp;amp; CentOS return to DevConf US?
Absolutely.
DevConf US is a fantastic venue, but next time we must arrive prepared for the audience in the room.
The curiosity is already there.
We just need to build the bridge that lets them cross over into upstream work.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;</description>
      <guid isPermaLink="false">https://jwheel.org/blog/2026/10/devconf-us-2026/</guid>
      <pubDate>Tue, 27 Oct 2026 08:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Richard Hughes: SK-8855 in the year 2026</title>
      <link>https://blogs.gnome.org/hughsie/2026/10/27/sk-8855-in-the-year-2026/</link>
      <description>&lt;p&gt;I’ve been an unapologetic fan of the Lenovo “classic” 7 row keyboard in the ThinkPad X220 and have been using the external version of it ever since. This USB laptop keyboard chassis is called the &lt;a class="external" href="https://sharktastica.co.uk/wiki/lenovo-8855"&gt;SK-8855&lt;/a&gt; which was manufactured in the late 2000s and early 2010s and is now essentially unobtainium from everywhere. The SK-8855 features a &lt;a class="external" href="https://sharktastica.co.uk/wiki/trackpoint"&gt;TrackPoint&lt;/a&gt; but lacks a trackpad – which is actually a feature for me. It’s rarely available on eBay as new-old stock for several hundred dollars. Over the last 10 years I’ve replaced the keyboard several times due to literally wearing it out, and finding genuine NMB replacement keyboards is getting harder and harder — but not impossible.&lt;/p&gt;
&lt;p&gt;For the last 10 years I’ve dealt with a few little quirks. Sometimes the controller board essentially sh*ts itself and crashes, but it could always be coaxed back into life by removing and reinserting the USB-A plug. It’s also guilty of missing a quick left-shift press, so typing fast my sentences never get capitalized. Over the years a few people have commented on my lack of grammar skills and until very recently I had this controller board to blame.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blogs.gnome.org/hughsie/files/2026/10/lenovo8855_controller.jpg"&gt;&lt;img alt="" class="aligncenter size-full wp-image-10058" height="768" src="https://blogs.gnome.org/hughsie/files/2026/10/lenovo8855_controller.jpg" width="1024"/&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;After over 15 years of being blamed for all my typos, the controller board gave up completely. This gave me the “opportunity” to replace it with a &lt;a class="external" href="https://www.etsy.com/listing/1890016956/circuit-board-for-classic-laptop"&gt;modern converter board&lt;/a&gt; and bring it into the 2020s. A good analogy is putting a Tesla electric drive-train in a classic Ferrari with a blown engine.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blogs.gnome.org/hughsie/files/2026/10/pcb.jpg"&gt;&lt;img alt="" class="aligncenter size-full wp-image-10057" height="642" src="https://blogs.gnome.org/hughsie/files/2026/10/pcb.jpg" width="793"/&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This required removing some plastic supports, which made me feel like the worst computer peripheral conservator in existence. After removing the USB-C connector the new controller could be mounted and wired up to the existing USB wire. &lt;/p&gt;
&lt;p&gt;&lt;a href="https://blogs.gnome.org/hughsie/files/2026/10/PXL_20261025_135914459.MP_.jpg"&gt;&lt;img alt="" class="aligncenter size-large wp-image-10059" height="869" src="https://blogs.gnome.org/hughsie/files/2026/10/PXL_20261025_135914459.MP_-778x1024.jpg" width="660"/&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In most part it worked as a keyboard, but was set up with the &lt;code&gt;en_US&lt;/code&gt; keymap and didn’t do anything for the &lt;code&gt;#&lt;/code&gt; key for instance. I ran the provided non-free win32 tool in Wine but that just showed some really tiny Chinese text. It also crashed a lot and I couldn’t work out the pinmap format that it was writing.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blogs.gnome.org/hughsie/files/2026/10/Screenshot-From-2026-10-27-11-34-42.png"&gt;&lt;img alt="" class="aligncenter size-full wp-image-10065" height="169" src="https://blogs.gnome.org/hughsie/files/2026/10/Screenshot-From-2026-10-27-11-34-42.png" width="248"/&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;After being &lt;a href="https://blogs.gnome.org/uraeus/2026/10/15/aiandreverseengineerhardware/"&gt;inspired by Christian&lt;/a&gt;, I asked Claude to analyse the updater binary and tell me what it knew, and after allowing it device access it essentially reverse engineered the hardware. I actually bought &lt;em&gt;two&lt;/em&gt; new controller boards and so I was a little more comfortable letting Claude actually drive the keyboard itself — and every now and then it would ask me to press specific keys and tell it if certain LEDs were on or off. After a full day of Claude-ing (never leave a hardware geek alone with minimal chores for a weekend day…) I had two things:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blogs.gnome.org/hughsie/files/2026/10/screenshot.png"&gt;&lt;img alt="" class="aligncenter size-large wp-image-10060" height="342" src="https://blogs.gnome.org/hughsie/files/2026/10/screenshot-1024x530.png" width="660"/&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a class="external" href="https://github.com/hughsie/xykbms-gtk"&gt;xykbms-gtk&lt;/a&gt; is a GTK4 standlone version of the vendor tool that works in Linux using hidraw. Using this I could swap, remap and disable keys and change all the other parameters on the controller board. I’ve not submitted this to Flathub as it’s 80% AI generated and more than niche; if you’re soldering stuff into a SK-8855 then you’re more than qualified to do meson build. It does work remarkably well considering I had no kind of datasheet or firmware source code for the controller at all.&lt;/p&gt;
&lt;p&gt;The other thing was a fwupd plugin for this new keyboard controller. I actually manually created the fwupd plugin template with lots of &lt;code&gt;TODO&lt;/code&gt;s in the right place to define the structure and then pointed Claude at the protocol documentation it had created for the GTK4 tool and asked it to fix all the TODOs in the plugin. After another couple of hours of questions and &lt;em&gt;verb&lt;/em&gt;-ing from Claude &lt;a class="external" href="https://github.com/fwupd/fwupd/pull/11252"&gt;we had a fully functional fwupd plugin&lt;/a&gt; that could not only update the firmware on the controller but could also write a “pinmap” that could reconfigure the keyboard between &lt;code&gt;en_US&lt;/code&gt; and &lt;code&gt;en_GB&lt;/code&gt; etc. I think this worked so well because we have so many self tests and linters in fwupd; Claude was forced to do the right thing before it could even run &lt;code&gt;git commit&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The keyboard pinmap wasn’t really a “firmware” per-se, so I then also got Claude to create a WriteBlob method that allows fwupd to write a raw payload on a CFI-type device. This will also be super useful in the future to flash SPI devices with the existing &lt;a class="external" href="https://github.com/fwupd/fwupd/tree/main/plugins/wch-ch341a"&gt;CH341a&lt;/a&gt; and &lt;a class="external" href="https://github.com/fwupd/fwupd/tree/main/plugins/wch-ch347"&gt;CH347&lt;/a&gt; plugins. This is only available for CFI flash devices and for users that authenticate with the admin password – for obvious reasons.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blogs.gnome.org/hughsie/files/2026/10/Screenshot-From-2026-10-27-11-54-04.png"&gt;&lt;img alt="" class="aligncenter size-full wp-image-10068" height="388" src="https://blogs.gnome.org/hughsie/files/2026/10/Screenshot-From-2026-10-27-11-54-04.png" width="937"/&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I then wrote the GNOME Firmware code to be able to flash a CFI image from the GUI. It’s not beautiful yet and we probably need a dedicated app, or a dedicated “mode” in gnome-firmware to make flashing CFI devices safe and easy. I’ll add a screenshot when I’m happy with the UX.&lt;/p&gt;
&lt;p&gt;I’m using this keyboard right now, and maybe it can last &lt;em&gt;another&lt;/em&gt; 15 years of abuse from me.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/hughsie/2026/10/27/sk-8855-in-the-year-2026/</guid>
      <pubDate>Tue, 27 Oct 2026 12:01:46 +0000</pubDate>
    </item>
    <item>
      <title>Cassidy James Blaede: Updates to the Blog</title>
      <link>https://cassidyjames.com/blog/blog-updates-pagination-tags-import/</link>
      <description>&lt;p&gt;I’ve been wanting to get back into more frequent blogging instead of just posting half-thought-out toots to Mastodon, turning them into a rambling thread, and then losing the thought to the depths of social media… but every time I try to write something, there are a bunch of changes I want to make to my website so I get overwhelmed and do something else. 😅&lt;/p&gt;
&lt;p&gt;Between the recent Matrix Conference (another blog post I need to write…), travel, and taking a couple of days off of work to recover, I decided to tackle some of those changes to &lt;em&gt;hopefully&lt;/em&gt; reduce the mental block for the future: I finally added pagination and tags, plus imported a bunch of my writing from other sites! As long as I’m here, I figured I should document the changes as a blog post, too.&lt;/p&gt;
&lt;h3 id="pagination"&gt;Pagination&lt;/h3&gt;
&lt;p&gt;As my blog has grown (I have posts as from over a decade ago!), dropping every post onto a single index page has started to get a bit unwieldy. I knew Jekyll had a pagination plugin, but I hadn’t set it up. I finally did that, with nicely-styled back/forward buttons.&lt;/p&gt;
&lt;figure&gt;
&lt;source type="image/webp"/&gt;&lt;source type="image/png"/&gt;&lt;img alt="Newer button, page 4 of 7, older button" class="card" src="https://cassidyjames.com/img/blog/blog-updates-pagination-tags-import/pagination-720-eb22098e7.png"/&gt;
&lt;/figure&gt;
&lt;p&gt;It’s a little thing, but something I’d been putting off for too long.&lt;/p&gt;
&lt;h3 id="tags"&gt;Tags&lt;/h3&gt;
&lt;p&gt;With over a hundred and fifty posts, even paging through the blog is not a great experience if you’re looking for something specific. I went through and tagged every blog post by topic: e.g. &lt;a href="https://cassidyjames.com/blog/tags/gnome/"&gt;GNOME&lt;/a&gt;, &lt;a href="https://cassidyjames.com/blog/tags/design/"&gt;Design&lt;/a&gt;, &lt;a href="https://cassidyjames.com/blog/tags/flatpak/"&gt;Flatpak &amp;amp; Flathub&lt;/a&gt;, &lt;a href="https://cassidyjames.com/blog/tags/howto/"&gt;How-To&lt;/a&gt;, and &lt;a href="https://cassidyjames.com/blog/tags/webdev/"&gt;Web Development&lt;/a&gt;.&lt;/p&gt;
&lt;figure&gt;
&lt;source type="image/webp"/&gt;&lt;source type="image/png"/&gt;&lt;img alt="Tags on a post" class="card" src="https://cassidyjames.com/img/blog/blog-updates-pagination-tags-import/tags-800-97cdc326c.png"/&gt;
&lt;/figure&gt;
&lt;aside&gt;
&lt;p&gt;&lt;strong&gt;Fun accident:&lt;/strong&gt; the &lt;a href="https://cassidyjames.com/blog/tags/starwars/"&gt;Star Wars tag page&lt;/a&gt; gets the same styling as my &lt;a href="https://cassidyjames.com/starwars/"&gt;Star Wars pages&lt;/a&gt; section because of how I use path-based CSS classes for custom styling. It was a bug, but I kind of like how it’s a fun easter egg, so I kept it. 😉️&lt;/p&gt;
&lt;/aside&gt;
&lt;p&gt;I also wanted a way to format the tags nicely (e.g. &lt;code class="language-plaintext highlighter-rouge"&gt;Star Wars&lt;/code&gt; for the &lt;code class="language-plaintext highlighter-rouge"&gt;starwars&lt;/code&gt; tag) and provide some more context, so I added a data file to my Jekyll site to optionally provide a display name and description for each tag. Hover the tags to see the descriptions, or check out the new &lt;a href="https://cassidyjames.com/blog/tags/"&gt;tag listing&lt;/a&gt; to browse all of the available topics!&lt;/p&gt;
&lt;h3 id="importing-my-writing"&gt;Importing my writing&lt;/h3&gt;
&lt;p&gt;Pagination and tags help a lot because now because: my blog has &lt;em&gt;way&lt;/em&gt; more posts! I’ve imported my writing from elementary and Android Police so it’s all accessible from one place.&lt;/p&gt;
&lt;p&gt;I wrote a ton for the elementary Tumblr, Medium publication, and blog during the decade-plus I contributed and then worked full-time on elementary; release announcements, AppCenter Spotlights, design rationale, developer tips, and more. I’d copied &lt;em&gt;some&lt;/em&gt; of my work here in the past, but most of it was still only accessible on the elementary blog—or was lost to the depths of Medium and Tumblr. I finally spent the time to import the 80+ remaining posts I authored. Where the posts are still available on the elementary blog, I made sure to point the canonical URL there to avoid leeching any search engine juice from the original site; I just want to make it convenient to read my stuff in one place, but don’t want to mess up search engine ranking or anything. You can check out the entire archive on my site under the &lt;a href="https://cassidyjames.com/blog/tags/elementary/"&gt;elementary tag&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Similarly (though on a &lt;em&gt;much&lt;/em&gt; smaller scale), I contributed a few posts to &lt;a href="https://www.androidpolice.com/author/cassidy/"&gt;Android Police&lt;/a&gt; before they were bought out and strip-mined by Valnet—the company &lt;a href="https://androiddev.social/@ryne/113544768947181345"&gt;described by former writers as unethical&lt;/a&gt; that &lt;a href="https://kotaku.com/polygon-sold-vox-media-valnet-layoffs-digital-gaming-1851778655?ref=aftermath.site"&gt;acquires news sites and immediately lays off their staff&lt;/a&gt;, and &lt;a href="https://web.archive.org/web/20241125151535/https://twitter.com/joshtyler/status/1861066207270735989"&gt;threatens to sue journalists&lt;/a&gt; for reporting on them. Since the topics I wrote about may be of interest to readers of my blog, I added those posts as redirects (with the ability to serve them from the site directly if they ever disappear). You can peruse those posts under the &lt;a href="https://cassidyjames.com/blog/tags/android/"&gt;Android tag&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If I find more of my writing across the Internet, I plan to pull it into this blog in a similar way; either cross-posted directly or at least indexed here with a redirect to the original.&lt;/p&gt;
&lt;h3 id="whats-next"&gt;What’s next?&lt;/h3&gt;
&lt;p&gt;I know not to promise anything (especially timelines!) but here are some things I’d like to work on next for my blog:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Per-tag styling (e.g. a unique accent color)&lt;/li&gt;
&lt;li&gt;Find some of my more verbose Mastodon threads and turn them into blog posts&lt;/li&gt;
&lt;li&gt;Automatically-generated social cards by default&lt;/li&gt;
&lt;li&gt;Search while keeping everything static&lt;/li&gt;
&lt;li&gt;Address whatever other &lt;a href="https://github.com/cassidyjames/cassidyjames.github.io/issues"&gt;issues I’ve opened&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Write more!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If anything in this post sounded interesting, &lt;a href="https://github.com/cassidyjames/cassidyjames.github.io"&gt;my website is open source&lt;/a&gt;! Check out the source code or commit history to learn how I did things. I can’t promise I did everything the &lt;em&gt;right&lt;/em&gt; way, but it works!&lt;/p&gt;</description>
      <guid isPermaLink="false">https://cassidyjames.com/blog/blog-updates-pagination-tags-import/</guid>
      <pubDate>Wed, 28 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Jakub Steiner: I am playing Grid right now!</title>
      <link>https://blog.jimmac.eu/posts/udev-dualsense/</link>
      <description>&lt;p&gt;I never liked racing "sims" like Gran Turismo. So realistic! You can bounce off the guardrails like in a pinball. &lt;a href="https://en.wikipedia.org/wiki/Race_Driver:_Grid" rel="external"&gt;Grid&lt;/a&gt; on the other hand was a fantastic "arcade" racer with a brilliant damage model where mistakes were punished. And the camera work! And music. Boy, that was such a treat!&lt;/p&gt;
&lt;p&gt;Nostalgia stroke me fiercely and I needed to play that game in some form. Among a sea of weird remakes, there simply wasn't a platform you could play the proper original &lt;em&gt;Racedriver: Grid&lt;/em&gt; on, other than emulators. So I bit the bullet and dove into the craziness of &lt;a href="https://flathub.org/en/apps/net.rpcs3.RPCS3" rel="external"&gt;RPCS3&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;That UX is crazy, let me tell you. In the end you get a game playable even on an old workstation, which was a surprise in itself. A much bigger surprise was the support for network play. Obviously not a single soul is playing Grid in 2026, but it's a fun thought I might convince someone to play :)&lt;/p&gt;
&lt;img alt="Race Driver: Grid running in RPCS3" class="full full-bleed" height="593" src="https://blog.jimmac.eu/posts/udev-dualsense/racedriver-grid.webp" width="1635"/&gt;
&lt;div class="controller-view" id="controller-view"&gt;
&lt;/div&gt;
&lt;p class="controller-credit"&gt;&lt;em&gt;3D model: &lt;a href="https://sketchfab.com/3d-models/playstation-5-dualsense-878c1f882808477ab81c2fe86d5a3936"&gt;"Playstation 5 Dualsense"&lt;/a&gt; by AHarmlessPotato, CC-BY-4.0&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Anyway, the reason to post this is to remind myself in the future how to get my PS5 &lt;em&gt;DualSense&lt;/em&gt; controller to work on &lt;a href="https://os.gnome.org/" rel="external"&gt;GNOME OS&lt;/a&gt;. As always, a udev rule. Having this config in &lt;code&gt;/etc/udev/rules.d/70-dualsense.rules&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;# DualSense over USB (054c:0ce6)
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ce6", MODE="0660", TAG+="uaccess"
# DualSense over Bluetooth (054c:0ce5)
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ce5", MODE="0660", TAG+="uaccess"
KERNEL=="hidraw*", KERNELS=="*054C:0CE5*", MODE="0660", TAG+="uaccess"
# DualSense Edge over USB (054c:0df2) / Bluetooth (054c:0df4)
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0df2", MODE="0660", TAG+="uaccess"
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0df4", MODE="0660", TAG+="uaccess"
KERNEL=="hidraw*", KERNELS=="*054C:0DF4*", MODE="0660", TAG+="uaccess"
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Reload the rules and replug (the ACL is re-applied on every plug, so it persists across reboots and replugs):&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;run0 udevadm control --reload-rules &amp;amp;&amp;amp; run0 udevadm trigger
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Check things work from inside RPCS3's sandbox:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;flatpak run --command=sh net.rpcs3.RPCS3 -c 'test -r /dev/hidraw9 &amp;amp;&amp;amp; test -w /dev/hidraw9 &amp;amp;&amp;amp; echo OK'
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;But again, the experience of this monstrosity. Briefly looking over Alice' shoulder at what's she's cooking with &lt;a href="https://gitlab.gnome.org/World/highscore" rel="external"&gt;Highscore&lt;/a&gt;, the difference in experience and polish is night &amp;amp; day.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blog.jimmac.eu/posts/udev-dualsense/</guid>
      <pubDate>Fri, 30 Oct 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Sophie Herold: GNOME Fellowship October 2026</title>
      <link>https://blogs.gnome.org/sophieh/2026/10/30/gnome-fellowship-october-2026/</link>
      <description>&lt;p&gt;&lt;em&gt;The GNOME Foundation is supporting contributors with its &lt;a class="external" href="https://fellowship.gnome.org/"&gt;fellowship program&lt;/a&gt;. You can help expand the fellowship program with a &lt;a class="external" href="https://donate.gnome.org/"&gt;donation&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;After the release of GNOME 51 in the previous month, this month was the time were people noticed the first regressions and bugs. Hence, a lot of work went into bug fixes this month.&lt;/p&gt;
&lt;h2 id="rfc-process-landed"&gt;RFC Process Landed&lt;/h2&gt;
&lt;p&gt;GNOME now has a &lt;a class="external" href="https://gitlab.gnome.org/GNOME/rfcs"&gt;project-wide RFC process&lt;/a&gt;. There were a few changes that happened this month, which further simplified the process and removed the special role of teams.&lt;/p&gt;
&lt;p&gt;Since we have a consensus on a process now, I will supplement it with further documentation soon.&lt;/p&gt;
&lt;h2 id="glycin"&gt;glycin&lt;/h2&gt;
&lt;p&gt;The CMYK support &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/merge_requests/483"&gt;has been merged&lt;/a&gt;. You can check my &lt;a href="https://blogs.gnome.org/sophieh/2026/10/06/gnome-fellowship-september-2026/"&gt;last blog post&lt;/a&gt; for more details.&lt;/p&gt;
&lt;p&gt;Another big change this month is the move from libjxl to jxl-rs. This is the same decoder now used by Chromium and Firefox. Thanks a lot to Wonwoo for the &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/merge_requests/473"&gt;contribution&lt;/a&gt; and for all the people who fixed upstream issues that the GNOME implementation revealed.&lt;/p&gt;
&lt;p&gt;Other than that, there were a lot of smaller things to address in glycin, most due to the GNOME 51 release:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;ul&gt;
&lt;li&gt;Fix image loading getting stuck on systems with lowered &lt;code&gt;sysctl net.core.wmem_default&lt;/code&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/334"&gt;#334&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix libglycin’s &lt;code&gt;get_mime_types&lt;/code&gt; blocking main thread &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/merge_requests/487"&gt;!487&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix orientation not parsed correctly for some images with MakerNote Exif tag &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/332"&gt;#332&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix memory growth via filling up the channel in image-rs loader for animated images &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/338"&gt;#338&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix animation threads in image-rs not terminated until the loader process exits &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/merge_requests/491"&gt;!491&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Canonicalize loader paths when reading config &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/340"&gt;#340&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix Exif decoder panic I &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/329"&gt;#329&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Move JPEG XL loaders into the image-rs loader while keeping the C-based editor separate &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/merge_requests/495"&gt;!495&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix some .cur-files being detected as TGA files &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/345"&gt;#345&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix Exif decoder panic II &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/346"&gt;#346&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix libglycin panic in construction of &lt;code&gt;GlyPixelDensity&lt;/code&gt; with invalid data &lt;a class="external" href="https://gitlab.gnome.org/GNOME/glycin/-/work_items/347"&gt;#347&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="image-viewer-loupe"&gt;Image Viewer (Loupe)&lt;/h3&gt;
&lt;p&gt;Loupe benefits from the new CMYK support in glycin. Here is a comparison of nightly Loupe vs Loupe 50.&lt;/p&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_1336" style="width: 905px;"&gt;&lt;img alt="Loupe app window showing a dominantly green image with moss and a pink blurred flower in the background" class="wp-image-1336 size-full" height="498" src="https://blogs.gnome.org/sophieh/files/2026/10/loupe-cmyk-52.png" width="905"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-1336"&gt;Loupe with latest glycin showing the CMYK image correctly and indicating the CMYK color model under &lt;em&gt;Image Format&lt;/em&gt;.&lt;/figcaption&gt;&lt;/figure&gt;
&lt;figure class="wp-caption aligncenter" id="attachment_1337" style="width: 905px;"&gt;&lt;img alt="Very similar image to the previous one. Only difference being that the colors are oversaturated and &amp;quot;CMYK&amp;quot; isn't mentioned in the image properties." class="wp-image-1337 size-full" height="498" src="https://blogs.gnome.org/sophieh/files/2026/10/loupe-cmyk-51.png" width="905"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-1337"&gt;Loupe 51 showing wrong colors for a CMYK image with ICC profile. This ICC profile oversaturates the colors to print on uncoated paper that will absorb a lot of ink.&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;There are also some fixes that landed in Loupe this month:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;ul&gt;
&lt;li&gt;Set physical dimensions of generated intermediate PDF for printing correctly &lt;a class="external" href="https://gitlab.gnome.org/GNOME/loupe/-/work_items/417"&gt;#417&lt;/a&gt; &lt;a class="external" href="https://gitlab.gnome.org/GNOME/loupe/-/work_items/613"&gt;#613&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fix fractional scaling potentially blurring image rendering (see &lt;a href="https://blogs.gnome.org/gtk/2026/05/28/snapping/"&gt;“Snapping”&lt;/a&gt;) &lt;a class="external" href="https://gitlab.gnome.org/GNOME/loupe/-/work_items/326"&gt;#326&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Show if image uses CMYK color model &lt;a class="external" href="https://gitlab.gnome.org/GNOME/loupe/-/merge_requests/621"&gt;!621&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="other-work"&gt;Other Work&lt;/h3&gt;
&lt;p&gt;I &lt;a class="external" href="https://gitlab.gnome.org/Teams/Releng/AppOrganization/-/work_items/41"&gt;reviewed&lt;/a&gt; &lt;em&gt;Resources&lt;/em&gt;, which is currently incubating as a replacement GNOME Core app for &lt;em&gt;System Monitor&lt;/em&gt;. I found a few minor issues. Other than that, the app is close to being ready for GNOME Core. A review from the Design Team is still outstanding.&lt;/p&gt;
&lt;p&gt;A topic that has been causing me a headache for a while has been how to properly implement memory limitations for glycin and thumbnailer sandboxes. There currently &lt;a class="external" href="https://gitlab.gnome.org/Teams/Platform/General/-/work_items/1"&gt;is no perfect solution&lt;/a&gt;. It looks like I will go with cgroups outside Flatpaks created via &lt;code&gt;StartTransientUnit&lt;/code&gt;, at least for glycin. I’m happy that we finally have a decision.&lt;/p&gt;
&lt;h2 id="support-the-gnome-project"&gt;Support the GNOME Project&lt;/h2&gt;
&lt;p&gt;The GNOME Fellowships are funded by our community. If you would like to help the GNOME project to stay sustainable, please &lt;a class="external" href="https://donate.gnome.org/"&gt;consider donating&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a class="external" href="https://donate.gnome.org"&gt;&lt;img alt="Donate to GNOME" class="aligncenter wp-image-1300" height="367" src="https://blogs.gnome.org/sophieh/files/2026/08/donate-card-1-1024x683.png" width="550"/&gt;&lt;/a&gt;&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/sophieh/2026/10/30/gnome-fellowship-october-2026/</guid>
      <pubDate>Fri, 30 Oct 2026 15:41:12 +0000</pubDate>
    </item>
    <item>
      <title>Matthew Garrett: Getting Google Cast on my Soundbar</title>
      <link>https://codon.org.uk/~mjg59/blog/p/getting-google-cast-on-my-soundbar/</link>
      <description>&lt;p&gt;I have a Samsung Q800A soundbar. It ships with built-in support for the Apple Airplay protocol, but I’m not really an Apple kind of guy so that’s never been particularly helpful for me. So, instead, I have a Chromecast Audio plugged into it via TOSLINK, and that works fine - except for the fact that there’s no way to explicitly pick TOSLINK as the audio input. Instead, there’s a “Digital In” option that refers to both the optical in and eARC input from a TV. Not inherently a problem, given I’m unlikely to be watching TV while listening to music, but my TV is a Samsung Frame, a device that’s intended to display art whenever someone is standing nearby, and which infuriatingly generates an eARC signal even if it’s only in art mode and isn’t going to make any noise. This switches the soundbar away from optical and I get sad. I could plug a video cast device into the HDMI port on the soundbar and cast audio to that, but then the art would get replaced with album covers whenever I’m playing music, and again that’s not quite the ambience I want. Still, none of this is that important.&lt;/p&gt;
&lt;p&gt;Until I learned that the Australian version of the soundbar &lt;em&gt;does&lt;/em&gt; have Google Cast support. The firmware image was downloadable from Samsung support, so I grabbed that, but unfortunately found that it was encrypted. However, if I downloaded the firmware image for the US model, the encrypted blob was identical - there’s no difference in the underlying firmware between the two of them. So, how come one has support, and the other doesn’t?&lt;/p&gt;
&lt;p&gt;I’d need an unencrypted copy of the firmware to have a real chance of figuring this out, and the easiest way to get one was to just run an ebay watch for a broken model of the same series. Once I had one in my hands I used hot air to remove the eMMC storage from the device, cleaned up the chip, and then stuck it in &lt;a class="link" href="https://www.amazon.com/dp/B06Y55DKND" rel="noopener" target="_blank"&gt;one of these&lt;/a&gt; adapters to read it on a local system. Samsung uses a weird in-house filesystem called VDFS4 on some of their devices and this was one of them, so I needed to cobble together a kernel that was compatible with their source dump for this device (not all VDFS drivers seem to be able to read all VDFS filesystems), but eventually I had it all extracted, and then I got distracted by other stuff, so let’s fast forward to this week.&lt;/p&gt;
&lt;p&gt;Samsung makes use of a modified version of the &lt;a class="link" href="https://developer.android.com/tools/adb" rel="noopener" target="_blank"&gt;Android Debug Bridge&lt;/a&gt; called sdb, which is included in the Tizen SDK. The firmware showed that this device had sdbd on it, and it would be executed if a network device called “huart0” was plugged in. Samsung does, thankfully, provide the source code for their GPLed components, so I could dig through that to discover that drivers/net/usb/usbnet.c had a bunch of references to huart (which apparently stands for “HyperUART”). If CONFIG_SAMSUNG_USBNET_HYPERUART_IFNAME is set, and if the ethernet device is using either the asix or ax88179_178a drivers, and if “/opt/etc/HyperUART_IP_Addr”&lt;sup id="fnref:1"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:1"&gt;1&lt;/a&gt;&lt;/sup&gt; isn’t just “0”, it sets the interface name to “huart0” and in turn triggers sdbd startup. So now I just needed to figure out how to set /opt/etc/HyperUART_IP_Addr to something else.&lt;/p&gt;
&lt;p&gt;Some digging revealed a binary called wap-factory that referenced the file, which then led to /usr/share/mobile-mgr/jsons/com.samsung.audio.waapp-verification-test.json which mentioned a “SetUartOnOff” call, which brought me &lt;a class="link" href="https://github.com/travnie/wambridge/blob/0b8ad203ad36cbc3c5ce6e807b1cb36d1db4e8b6/docs/WAM_PROTOCOL.md?plain=1" rel="noopener" target="_blank"&gt;here&lt;/a&gt;&lt;sup id="fnref:2"&gt;&lt;a class="footnote-ref" href="https://codon.org.uk/~mjg59/blog/index.xml#fn:2"&gt;2&lt;/a&gt;&lt;/sup&gt;, which led me into a bit of a rabbit hole about the Samsung WAM protocol. Long story short, you connect to either port 55001 or 56001 and make two requests over the same connection:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre class="chroma" tabindex="0"&gt;&lt;code&gt;&lt;span class="lnt"&gt;1
&lt;/span&gt;&lt;span class="lnt"&gt;2
&lt;/span&gt;&lt;span class="lnt"&gt;3
&lt;/span&gt;&lt;span class="lnt"&gt;4
&lt;/span&gt;&lt;span class="lnt"&gt;5
&lt;/span&gt;&lt;span class="lnt"&gt;6
&lt;/span&gt;&lt;span class="lnt"&gt;7
&lt;/span&gt;&lt;span class="lnt"&gt;8
&lt;/span&gt;&lt;span class="lnt"&gt;9
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre class="chroma" tabindex="0"&gt;&lt;code class="language-fallback"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;GET /connect HTTP/1.1
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Host: 192.168.87.126:56001
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;User-Agent: SamsungMultiroom/1.0
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Connection: interactive
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;GET /UIC?cmd=%3Cname%3ESetUartOnOff%3C/name%3E%3Cp%20type%3D%22str%22%20name%3D%22uartOnOff%22%20val%3D%22on%22/%3E HTTP/1.1
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Host: 192.168.87.126:56001
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;User-Agent: SamsungMultiroom/1.0
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Connection: interactive
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;and then plug in an asix chipset ethernet adapter into the USB port (which on mine is micro-B, so I needed an OTG adapter), and suddenly it’s sitting there on 192.168.250.250 and will speak sdb to you. &lt;code&gt;sdb root on&lt;/code&gt; switches it into root mode, and &lt;code&gt;sdb shell&lt;/code&gt; now gives you a root shell. I was in, and now I could investigate what was happening.&lt;/p&gt;
&lt;p&gt;First up, there was a process called “com.samsung.audio.google-cast-control-app” running, which seemed like a good start. Unfortunately it wasn’t doing anything. After some tracing I found that it was making a call to Samsung at startup time, and getting back a response telling it that Cast support wasn’t available. The request (which was helpfully dumped to stdout when I ran this by hand) included the country code, in my case “US”. Repeating the request by hand with curl and changing the code to “AU” told me it &lt;em&gt;was&lt;/em&gt; supported, so now I needed to figure out how to get the soundbar to believe it was Australian. Some digging showed it was reading this from a config variable called db/comss/countrycode, and running&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre class="chroma" tabindex="0"&gt;&lt;code&gt;&lt;span class="lnt"&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre class="chroma" tabindex="0"&gt;&lt;code class="language-fallback"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;buxton2ctl set-string system db/comss/countrycode AU
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;got me past that gate. Now, however, it was complaining that it couldn’t provision a key. /usr/apps/com.samsung.audio.google-cast-control-app/shared/res included a bunch of encrypted blobs and an app called teeStoreKey.elf, and tracing com.samsung.audio.google-cast-control-app showed it was trying to call that, but it seemed like it was failing with a permissions issue. Running com.samsung.audio.google-cast-control-ap directly as root triggered key provisioning successfully, and a few seconds later the rest of the Cast API came up and I could talk to port 8443 with standard Cast API calls. Unfortunately it still wasn’t working as a Cast device, though - it wasn’t advertising itself via mDNS and so nothing could see it. Querying the /setup/eureka_info endpoint gave me a clue - the ’tos_accepted’ field was false. Normally this would be set as part of initial device setup, but the Samsung app wasn’t doing that because it didn’t think the device had Cast support. It turns out that POSTing some json with {“tos_accepted”: true} to setup/set_eureka_info made it work, and suddenly there was an additional Cast device available to me.&lt;/p&gt;
&lt;p&gt;(Update: I realised I didn’t mention anything about &lt;em&gt;why&lt;/em&gt; it was doing key provisioning in the first place! The Cast protocol doesn’t enforce cryptographic identity as such, but Google’s reference client implementation which is what almost everything uses verifies that the device is presenting an identity that chains back to Google. Unsurprisingly they don’t want the private key material to be easily extractable and used to produce clone devices, so it’s all supposed to be encrypted and only accessible to some sort of trusted execution environment, which is why keys here need to be loaded into Trustzone and never be visible in the clear to the main OS)&lt;/p&gt;
&lt;p&gt;Mission accomplished. Unfortunately the device vanished from my Smartthings home aferwards, presumably because there’s a mismatch between its reported country code and my account country. To get around that I’d somehow need to get com.samsung.audio.google-cast-control-app to either change the query without changing the global device country, or to ignore the response from Samsung (it does this every 24 hours, ugh), and that’s made more annoying by the fact that this thing will only execute signed binaries. Although, weirdly, one of the signed binaries shipped is a full Python interpreter, so if I cared enough I could probably cobble together enough Python to execute arbitrary binaries. I currently don’t.&lt;/p&gt;
&lt;p&gt;More modern soundbars don’t implement the listener on port 55001 or 56001. I don’t know how you get sdb working on them.&lt;/p&gt;
&lt;div class="footnotes"&gt;
&lt;hr/&gt;
&lt;ol&gt;
&lt;li id="fn:1"&gt;
&lt;p&gt;Yes, it reads a file directly from in-kernel &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:1"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id="fn:2"&gt;
&lt;p&gt;Good god I hate reading this kind of slop &lt;a class="footnote-backref" href="https://codon.org.uk/~mjg59/blog/index.xml#fnref:2"&gt;↩︎&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;</description>
      <guid isPermaLink="false">https://codon.org.uk/~mjg59/blog/p/getting-google-cast-on-my-soundbar/</guid>
      <pubDate>Fri, 30 Oct 2026 18:03:47 +0000</pubDate>
    </item>
    <item>
      <title>Jussi Pakkanen: A slightly better ThreadPoolExecutor in Pystd through types</title>
      <link>https://nibblestew.blogspot.com/2026/10/a-slightly-better-threadpoolexecutor-in.html</link>
      <description>&lt;p&gt;In the previous post we looked at a simple multithreaded task executor that behaves roughly like its Python standard library &lt;a href="https://docs.python.org/3/library/concurrent.futures.html#threadpoolexecutor"&gt;counterpart&lt;/a&gt;. The biggest missing feature was being able to return values from run tasks via future objects. In a fully dynamic language like Python this is fairly straightforward, whereas in a language with static typing, such as C++, things are trickier.&lt;/p&gt;&lt;p&gt;The simplest solution is merely to make your &lt;span style="font-family: courier;"&gt;Executor&lt;/span&gt; class a template, parameterized by the function you want to run. The obvious downside is code bloat. If your program has an &lt;span style="font-family: courier;"&gt;Executor&amp;lt;Foo&amp;gt;&lt;/span&gt; and &lt;span style="font-family: courier;"&gt;Executor&amp;lt;Bar&amp;gt;&lt;/span&gt;, all of their code is duplicated in the binary, even though 90% of it is probably the same. Also, due to the magic of template instantiation, compilation is slower. Another downside is that you can't run tasks that do different things, especially having different return value types, with one Executor.&lt;/p&gt;&lt;p&gt;I set about trying to solve both of these issues at the same time. It turned out that if you are willing to tolerate just a little bit of OO and one extra malloc per task, one can get a fairly nice solution. As a task executor is used for things that run for a long time and consume a lot of resources, the overhead is insignificant for most use cases. And if it absolutely, positively matters to someone, they are going to roll their own anyway. Trying to cater to those use cases would be a waste of effort in any case.&lt;/p&gt;&lt;p&gt;These requirements point to a fairly obvious solution. The executor deals with &lt;span style="font-family: courier;"&gt;TypeErasedFuture/Promise&lt;/span&gt; types that store all the task metadata via good ol' &lt;span style="font-family: courier;"&gt;void&lt;/span&gt; pointers and virtual functions. The concrete &lt;span style="font-family: courier;"&gt;Future&lt;/span&gt; and &lt;span style="font-family: courier;"&gt;Promise&lt;/span&gt; tasks are just type safe shims on top of them. The entire implementation required the use of only two &lt;span style="font-family: courier;"&gt;reinterpret_cast&lt;/span&gt;s, which is quite surprising. I would have expected more, but sometimes you get lucky, I guess.&lt;/p&gt;&lt;p&gt;The Executor gets to remain a concrete class. The only template in it is the submit method that preserves the type erased task and returns a typed future object.&lt;/p&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjn9wykImy0MJGde3kMRoyD1RKR5-5uH5Q4zJRepTdgcuNKDfUmcRougUWi5sXUsBDMVQDZuD_WRlpcSy0JGe6dcU8eg8Th9EfmjE7IBUyagP1w2RQ7tmbKIc1VDmOxPHQXe4Jm5BgTDaEDEG4OIS15wse0we4FvoYiO_n9bFluVkeGnjsElRFv9GB6RwE/s976/executor_template.png" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="159" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjn9wykImy0MJGde3kMRoyD1RKR5-5uH5Q4zJRepTdgcuNKDfUmcRougUWi5sXUsBDMVQDZuD_WRlpcSy0JGe6dcU8eg8Th9EfmjE7IBUyagP1w2RQ7tmbKIc1VDmOxPHQXe4Jm5BgTDaEDEG4OIS15wse0we4FvoYiO_n9bFluVkeGnjsElRFv9GB6RwE/w400-h159/executor_template.png" width="400"/&gt;&lt;/a&gt;&lt;/div&gt;&lt;p&gt;Using this is not quite a simple as its Python counterpart, but still fairly easy. After you have written a class that implements the executor's task interface, submitting work and consuming the results is done like this.&lt;/p&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgRGWaHfGKTe4lMAiOMULH4MWLbQcqQ1VrH56bIkyjQpKX0PYm4kw_pfZjqmyiT94UEo5toOnZRLGOHjRmjshd3n7XGQb7q73oSx3snzlgJD2yJ-DdR_JGqck4BXWaA9vfy7Z4ZExGOiV5Ft7_S95OwMIsmG09H4nAPWutC1gQPGxgO3cYU8ruiDpI2YwM/s838/executor_submit.png" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="205" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgRGWaHfGKTe4lMAiOMULH4MWLbQcqQ1VrH56bIkyjQpKX0PYm4kw_pfZjqmyiT94UEo5toOnZRLGOHjRmjshd3n7XGQb7q73oSx3snzlgJD2yJ-DdR_JGqck4BXWaA9vfy7Z4ZExGOiV5Ft7_S95OwMIsmG09H4nAPWutC1gQPGxgO3cYU8ruiDpI2YwM/w400-h205/executor_submit.png" width="400"/&gt;&lt;/a&gt;&lt;/div&gt;&lt;p&gt;If the return value had been something other than void, &lt;span style="font-family: courier;"&gt;.get()&lt;/span&gt; would return a reference to the result object. The tradeoff between the ease of use provided by maximal templateism and minimal code generation is clearly visible in the extra boilerplate code you need to write to get things going. But in return you get both reduced binary size and faster compile times. Whether that is an improvement or a detriment is up to you.&lt;/p&gt;&lt;p&gt;This code is not going to win any robustness prizes (though, in the modern day of AI garbage, you never know), but the end result is more than adequate for a single evening work. &lt;/p&gt;</description>
      <guid isPermaLink="false">https://nibblestew.blogspot.com/2026/10/a-slightly-better-threadpoolexecutor-in.html</guid>
      <pubDate>Fri, 30 Oct 2026 22:00:32 +0000</pubDate>
    </item>
    <item>
      <title>This Week in GNOME: #272 Shiny Icons</title>
      <link>https://thisweek.gnome.org/posts/2026/10/twig-272/</link>
      <description>&lt;p&gt;Update on what happened across the GNOME project in the week from October 23 to October 30.&lt;/p&gt;
&lt;h2 id="gnome-fellowship"&gt;GNOME Fellowship&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/78a55022fd487dd708fbc8b46a274879ddd95a53c11137fde5bd519ebf5699ab"&gt;Sophie (she/her)&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;GNOME RFC Process, many fixes in glycin, CMYK images in Loupe, and more: Learn about my &lt;a href="https://blogs.gnome.org/sophieh/2026/10/30/gnome-fellowship-october-2026/"&gt;work in October&lt;/a&gt; as part of the GNOME Fellowship.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="gnome-core-apps-and-libraries"&gt;GNOME Core Apps and Libraries&lt;/h2&gt;
&lt;h3 id="files-"&gt;Files &lt;a href="https://gitlab.gnome.org/GNOME/nautilus"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Providing a simple and integrated way of managing your files and browsing your file system.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/3606de80c06ea68cc8e3d583c3de14a574d6c6b6b5635ef381999e3dc3c532b5"&gt;Peter Eisenmann&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Many MRs have landed in Files since the 51.1 release! Here are some highlights:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Jakub Steiner made some ✨shiny✨ new placeholder icons&lt;/li&gt;
&lt;li&gt;Khalid Abu Shawarib removed blocking I/O, so Files feels snappier&lt;/li&gt;
&lt;li&gt;Khalid also added more file operation tests and fixed issues an automated audit turned up&lt;/li&gt;
&lt;li&gt;Sivaprasad Murali brought operation error messages in line with the HIG&lt;/li&gt;
&lt;li&gt;Corey Berla fixed a security issue with emptying the trash on removable devices&lt;/li&gt;
&lt;li&gt;Jordan Petridis set up automated testing on GNOME OS in GitLab CI&lt;/li&gt;
&lt;li&gt;“Programejt” made sure overly long content text in the properties dialog doesn’t get ellipsized&lt;/li&gt;
&lt;li&gt;Peter Eisenmann taught the “Open With” app search to also match executable names
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img height="544" src="https://thisweek.gnome.org/_astro/qEjlOTVdzwSlTsvTwQBoTJoU_image.PiRgMKjS_Z16KF0P.webp" width="547"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="software-"&gt;Software &lt;a href="https://gitlab.gnome.org/GNOME/gnome-software/"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Lets you install and update applications and system extensions.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/38fcb3d7ec47a7787c0e20673542111b1fc08f6b2223e45be83d79fae8ebaa83"&gt;Philip Withnall&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Thanks to sysprof profiling by Jeff Fortin and code review by Georges, gnome-software has had some nice speedups in icon loading and downloading this week, which should make icons show up a lot faster in app listings, and reduce bandwidth and disk usage. See &lt;a href="https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/2466"&gt;https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/2466&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="calendar-"&gt;Calendar &lt;a href="https://gitlab.gnome.org/GNOME/gnome-calendar/"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;A simple calendar application.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/d231c2150f01c075171bb3fb65d96ba33ab90ac8bbb38903373557e1a1b371af"&gt;Georges Stavracas (feaneron)&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;GNOME Calendar continues to evolve with a few user facing and accessibility improvements in the past week. Thank you to everyone who submitted patches that landed this week, and everyone who reviewed and gave feedback on them!&lt;/p&gt;
&lt;h2 id="folding-search-results"&gt;Folding Search Results&lt;/h2&gt;
&lt;p&gt;Previously, searching in Calendar showed all instances of matching recurring events. Last week, we managed to merge a long-awaited patch that improves this behaviour by folding all instances of a matching recurring event into a single row! This makes searching for events cleaner and easier to parse, as the results are no longer flooded with irrelevant duplicates.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/808"&gt;!808&lt;/a&gt;, by John Cardullo; reviewed by Niklas Wimmer, Alen Galinec, Zelda Ahmed, and Georges Stavracas&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;video controls="controls"&gt;&lt;source src="https://thisweek.gnome.org/posts/2026/10/twig-272/30474ad1f1e7265ea89e4563bfe11d3a588153042116223502225768448_ScreencastFrom2026-10-3013-01-06.webm" type="video/webm"/&gt;&lt;/video&gt;&lt;/p&gt;
&lt;h2 id="focus-selected-date-first"&gt;Focus Selected Date First&lt;/h2&gt;
&lt;p&gt;Continuing the long effort to make GNOME Calendar more keyboard accessible, we landed a small tweak that improves the behaviour when tabbing into the sidebar’s and event editor’s date chooser grid. Instead of focusing the first cell in the grid, focus is now properly moved to the currently selected date’s cell. This matches the expected behavior when tabbing into other grids or lists, to first focus the currently selected item.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/869"&gt;!869&lt;/a&gt;, by Hari Rana; reviewed by Niklas Wimmer&lt;/p&gt;
&lt;h2 id="improved-screen-reader-output"&gt;Improved Screen Reader Output&lt;/h2&gt;
&lt;p&gt;To make Calendar more accessible, grid cells in the month view and date chooser will announce the month and day of the cell when focused. Previously, these cells only announced the day of the month, which made it very difficult for users to identify which month they were currently in!&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/886"&gt;!886&lt;/a&gt; and &lt;a href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/887"&gt;!887&lt;/a&gt;, by Arak; reviewed by Hari Rana and Niklas Wimmer&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;video controls="controls"&gt;&lt;source src="https://thisweek.gnome.org/posts/2026/10/twig-272/15f051d8e5b7578c01df29e1b716fff6f21f9cfc2116223507124715520_ScreencastFrom2026-10-3013-24-37.webm" type="video/webm"/&gt;&lt;/video&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="glib-"&gt;GLib &lt;a href="https://gitlab.gnome.org/GNOME/glib"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;The low-level core library that forms the basis for projects such as GTK and GNOME.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/38fcb3d7ec47a7787c0e20673542111b1fc08f6b2223e45be83d79fae8ebaa83"&gt;Philip Withnall&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Support for XDG intents has landed in GLib, thanks to work by Ignacy Kuchciński (based on implementation work by Sebastian Wick and spec work by many others). This is the groundwork for allowing apps to register themselves as supporting opening commands in a terminal, or handling certain URI schemes. Work is ongoing to implement these specific intents. See the &lt;a href="https://specifications.freedesktop.org/intent-apps/latest/"&gt;specification&lt;/a&gt; and the &lt;a href="https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4797"&gt;implementation in GLib&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="gnome-circle-apps-and-libraries"&gt;GNOME Circle Apps and Libraries&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/3f7e56fd3e07a5d293b680946eb734c590035ba39d4a7db7ddfc048c9d97aad6"&gt;Alexander Vanhee&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Bazaar has hit half a million downloads on Flathub! To celebrate, I’ve fixed our most upvoted issue: the Bazaar Flatpak can now install apps from user remotes. Try it today with the beta on the GNOME Nightly remote, and report any issues you may face, especially on that niche distro only you and your grandma use.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="third-party-projects"&gt;Third Party Projects&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/5e1e0d37e8ce2018d1ff948c401051b0b087af81ebcc3f7e18701d807f090a97"&gt;Mark&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;GitY 2026.7 is now out!
No longer is GitY simply a git repository viewer you can now manage your repositories directly. Many features have been added this year to make it a modern version of GitG. The most recent changes include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Add tags and branches&lt;/li&gt;
&lt;li&gt;Remove tags, branches, and stashes&lt;/li&gt;
&lt;li&gt;Commit diffs show images being added, changed, or removed (if you’re curious on the technical details it uses glycin)&lt;/li&gt;
&lt;li&gt;Search branches, tags, and stashes with CTRL-SHIFT-F&lt;/li&gt;
&lt;li&gt;Live repository refresh is now available as an option (default off)&lt;/li&gt;
&lt;li&gt;Can turn off the summary of lines changed per diff&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Download from Flahub: &lt;a href="https://flathub.org/en/apps/com.markdeepwell.GitY"&gt;https://flathub.org/en/apps/com.markdeepwell.GitY&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;&lt;img height="1090" src="https://thisweek.gnome.org/_astro/PMNVSYdAwZuxVizapUnpXhMl_GitYimagesadded.C2GGMkWt_Z1TkSwb.webp" width="1548"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="1090" src="https://thisweek.gnome.org/_astro/BdxXJTeyAdPjkdqHlwqOPEXQ_GitYlinux.J5bIJkRR_ZoYAA4.webp" width="1548"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/7eb6937cd9d14a3ed2be5dd83e1f7410a353e83d3791a28d6379100c73b34755"&gt;Nathan Perlman&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href="https://github.com/SwordPuffin/Rewaita"&gt;Rewaita&lt;/a&gt; got an update to v1.1.8 this week! This update was mostly focused on adding new features and filling in some of the odd blanks in the theming.&lt;/p&gt;
&lt;p&gt;What’s new?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added gtksourceview theme support (the editor part Gedit and Builder)&lt;/li&gt;
&lt;li&gt;Finally added hot reloading for GTK4&lt;/li&gt;
&lt;li&gt;Fixed Firefox 157.0 theming issues&lt;/li&gt;
&lt;li&gt;Moved user guide to Github wiki&lt;/li&gt;
&lt;li&gt;Unrelated to GNOME but Rewaita now has Cinnamon desktop support&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Hope you all enjoy! Give Rewaita a try if you haven’t, once you get sucked in you’ll never want to go back. And if do you like it make sure to leave a star on &lt;a href="https://github.com/SwordPuffin/Rewaita"&gt;Github&lt;/a&gt;. Installs are available of &lt;a href="https://flathub.org/en/apps/io.github.swordpuffin.rewaita"&gt;Flathub&lt;/a&gt; and the &lt;a href="https://aur.archlinux.org/packages/rewaita"&gt;AUR&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;&lt;img height="795" src="https://thisweek.gnome.org/_astro/qMzewKRQXhxTTyFWoRYclISA_TWIG-Screenshot.BxK63YpA_Gtz5l.webp" width="1062"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/74c9ab59651088f54ee1bafdc747cd3603b51fbcf04a1395a4f193978fdbc88a"&gt;Rat Cornu&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href="https://flathub.org/en/apps/org.skaven.ratic"&gt;Ratic&lt;/a&gt; got a new version &lt;a href="https://gitlab.gnome.org/ratcornu/ratic/-/releases/v0.4.5"&gt;0.4.5&lt;/a&gt; this week!&lt;/p&gt;
&lt;p&gt;This is not a big update, but it greatly improve performances: it is now instantaneous to reload the datas already cached during previous launches. Furthermore, scrolling in the application no longer make it lag, and the image cache size can been limited to control RAM consumption.&lt;/p&gt;
&lt;p&gt;You can check the new version on &lt;a href="https://flathub.org/en/apps/org.skaven.ratic"&gt;Flathub&lt;/a&gt;, on the &lt;a href="https://gitlab.gnome.org/ratcornu/ratic"&gt;repo&lt;/a&gt;, or even come discuss with us on &lt;a href="https://matrix.to/#/#ratic:skaven.org"&gt;our matrix room&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;Thanks again for all the people that contribute to the localization on &lt;a href="https://hosted.weblate.org/projects/ratic/ratic/"&gt;weblate&lt;/a&gt;!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/729728ceeb003695c86ccf7fed21c023bd29c2bbae9cb8eb7c63fceeee0e9d9f"&gt;Anton Isaiev&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;RustConn 0.24 is out - a connection manager for SSH, RDP, VNC, SPICE, Telnet, Serial, Kubernetes, Web and Zero Trust, built with GTK4 and Libadwaita.&lt;/p&gt;
&lt;p&gt;Since 0.23:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Faster SSH connects (no process spawns on the UI thread) and a Bitwarden performance pass&lt;/li&gt;
&lt;li&gt;“Set Up Key Authentication…” - generate or reuse an SSH key, install it, verify, switch over&lt;/li&gt;
&lt;li&gt;Terminal &lt;code&gt;.rsc&lt;/code&gt; scripting + OSC 52 remote clipboard&lt;/li&gt;
&lt;li&gt;RDP clipboard direction control, QUIC proxy preset, richer MobaXterm import/export&lt;/li&gt;
&lt;li&gt;Embedded browser in the Snap (now on core26)&lt;/li&gt;
&lt;li&gt;Loopback-only tunnels and stdin-fed Bitwarden secrets&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Thanks to Christian Petri, Naim Shafiev and all the contributors and translators who drove this cycle. And thanks to everyone who files bugs and supports the project - this cycle was driven largely by the issues you reported. If you’d like to support development, the repo has a Sponsor link.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/totoshko88/RustConn"&gt;https://github.com/totoshko88/RustConn&lt;/a&gt;
&lt;a href="https://flathub.org/apps/io.github.totoshko88.RustConn"&gt;https://flathub.org/apps/io.github.totoshko88.RustConn&lt;/a&gt;
&lt;a href="https://snapcraft.io/rustconn/"&gt;https://snapcraft.io/rustconn/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;&lt;img height="2294" src="https://thisweek.gnome.org/_astro/zNMeWjjgycgpHWMNeBBXFBqc_image.C3Vj3XZi_Z2piQF5.webp" width="3284"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/e84cb666cb1a4cf6dea2d24ee537aba8f251eefd8fc397f8ab4c6e5e81f5b9e5"&gt;Daniel Elia&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Convey 51.0 has been released!&lt;/p&gt;
&lt;p&gt;Since 50.2-1 it has become a much more polished mail client; narrow windows and mobile layouts work better, notifications are clearer, with several showing at once, and spell-checking has proper dictionary support.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Subject shown above the conversation&lt;/li&gt;
&lt;li&gt;Per-address signatures, with images&lt;/li&gt;
&lt;li&gt;Drag to resize images in the composer&lt;/li&gt;
&lt;li&gt;Unread filter in the search bar&lt;/li&gt;
&lt;li&gt;Unsubscribe from mailing lists&lt;/li&gt;
&lt;li&gt;Reply to List action&lt;/li&gt;
&lt;li&gt;Local Starred folder for IMAP accounts&lt;/li&gt;
&lt;li&gt;Folders in a sidebar on mobile&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I’m working on adding a “Favourites” section to the sidebar, so folders from any account can be shown at the top of the sidebar, and there’s still bugs to be fixed, all planned for 51.1&lt;/p&gt;
&lt;p&gt;Lastly, a big thank-you the community for getting so involved with the development of Convey, its first release to Flathub was a little over a month ago, and it’s seen much more adoption than I expected!&lt;/p&gt;
&lt;p&gt;Check it out on &lt;a href="https://flathub.org/apps/net.donnybeelo.Convey"&gt;Flathub&lt;/a&gt;, and check out the repo &lt;a href="https://gitlab.gnome.org/donnybeelo/convey"&gt;here&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;&lt;img height="1030" src="https://thisweek.gnome.org/_astro/fvIvcUYbQPfsTROQuwzpyXyR_image.mMiOA5_W_Z1C2t7u.webp" width="948"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="1400" src="https://thisweek.gnome.org/_astro/UapQLJffcMkynCPJpQJOFfhp_main-window.Bpv7wj-Q_Z2uIprs.webp" width="2000"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="fractal-"&gt;Fractal &lt;a href="https://gitlab.gnome.org/World/fractal"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Matrix messaging app for GNOME written in Rust.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/0bba5024ecb1c0c920590af124326a5643b54a4fbb247822d88077e3636ddac0"&gt;Kévin Commaille&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Only a week went by since our previous security-related update, and several upstream dependencies released even more security fixes so we bundled them into Fractal 14.3 to make sure that everything keeps running smoothly until the next release!&lt;/p&gt;
&lt;p&gt;This version is available right now on &lt;a href="https://flathub.org/apps/org.gnome.Fractal"&gt;Flathub&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As usual, you can also help make sure the next major version is solid by using &lt;a href="https://gitlab.gnome.org/World/fractal#development-version"&gt;Fractal Nightly&lt;/a&gt;. Help on fixing &lt;a href="https://gitlab.gnome.org/World/fractal/-/issues/?label_name%5B%5D=1.%20Bug"&gt;our remaining bugs&lt;/a&gt; is of course always appreciated!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="crosswords-"&gt;Crosswords &lt;a href="https://gitlab.gnome.org/jrb/crosswords"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;A crossword puzzle game and creator.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/23c83f6f7894b45274925cff086b988be7986f73caa4f793cae28b1efbfbc853"&gt;jrb&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href="https://blogs.gnome.org/jrb/2026/10/20/crosswords-0-3-19-new-layout-and-acrostic-editor/"&gt;GNOME Crosswords 0.3.19 is out!&lt;/a&gt;
This version features a redesigned game layout, with smooth animations and a new bottom sheet for clues in mobile mode. In the editor, acrostics are now out of Beta, with a much faster generator and an easier grid-building workflow. Also new: rich text in puzzle metadata, synonyms in word lists, large print templates, and tons of bug fixes.&lt;/p&gt;
&lt;p&gt;A plea for help: We received an experimental merge request to build macOS bundles. As that’s outside my expertise, I’d love help testing the game and reviewing the changes. Please &lt;a href="https://gitlab.gnome.org/jrb/crosswords/-/merge_requests/416"&gt;take a look&lt;/a&gt; or let me know if you can help.&lt;/p&gt;
&lt;p&gt;Get it on &lt;a href="https://flathub.org/en/apps/org.gnome.Crosswords"&gt;Flathub!&lt;/a&gt; &lt;em&gt;(&lt;a href="https://flathub.org/en/apps/org.gnome.Crosswords.Editor"&gt;Editor&lt;/a&gt;)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;video controls="controls"&gt;&lt;source src="https://thisweek.gnome.org/posts/2026/10/twig-272/kLDkBPTygqNxloWWXUalizZA_ScreencastFrom2026-10-1918-14-20.webm" type="video/webm"/&gt;&lt;/video&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;video controls="controls"&gt;&lt;source src="https://thisweek.gnome.org/posts/2026/10/twig-272/DFysgPlhtIclfsVEAAJrilhh_ScreencastFrom2026-10-1916-36-11.webm" type="video/webm"/&gt;&lt;/video&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="gnome-websites"&gt;GNOME Websites&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/8774b72e06465b3258a9bbbc7a1aafd0c2b816e854547dd95ef05e56c1cb11f8"&gt;Philipp Sauberzweig&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The Inter font has been installed on the GNOME WordPress instance. You can now use it on your personal GNOME blog to ensure consistency with GNOME’s web typography standards.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="shell-extensions"&gt;Shell Extensions&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/69ec004f958ed06673021f6f05c730d6c9574387a02b39ba5774c0799736bafa"&gt;Tomáš Gažovič&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;RSS Feed v10&lt;/p&gt;
&lt;p&gt;&lt;a href="https://extensions.gnome.org/extension/948/rss-feed/"&gt;RSS Feed&lt;/a&gt; reached version 10, a jubilee release for the extension.&lt;/p&gt;
&lt;p&gt;The main new features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starred articles: kept in their own group, even after they drop out of the feed or the feed is removed&lt;/li&gt;
&lt;li&gt;Configurable article actions: up to three hover buttons per article and separate actions for the left, middle and right mouse button: open, mark as read or unread, star, dismiss, mark older as read, copy link&lt;/li&gt;
&lt;li&gt;Dismiss and restore: hide articles you do not want to see and bring them all back from the header menu&lt;/li&gt;
&lt;li&gt;Article history: articles stay stored after they drop out of the feed, up to a per-feed limit&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Since the extension was ported to modern GNOME Shell earlier this year, it has passed 1000 downloads. Thank you to everyone who installed it, reported issues and sent feedback!&lt;/p&gt;
&lt;p&gt;Missing something in your RSS workflow? Share your idea in &lt;a href="https://github.com/todevelopers/gnome-shell-extension-rss-feed/discussions/categories/feature-requests"&gt;Feature Requests&lt;/a&gt; on GitHub Discussions, I read every one.
&lt;/p&gt;
&lt;p&gt;&lt;video controls="controls"&gt;&lt;source src="https://thisweek.gnome.org/posts/2026/10/twig-272/VCoXiSrWViqjwlElhCOolvJt_rss-feed-twig.webm" type="video/webm"/&gt;&lt;/video&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="miscellaneous"&gt;Miscellaneous&lt;/h2&gt;
&lt;h3 id="gnome-os-"&gt;GNOME OS &lt;a href="https://os.gnome.org"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;The GNOME operating system, development and testing platform&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/d77b8a631f4b1f340750858b48692fef43b1e08aa3ba0a6c67fd14dc0c185004"&gt;Ada Magicat&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;It has been a busy week with tons of fixes and 2 new contributors! Welcome John Adams and Lars Ellinger. Check out what they worked on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Lars added support for the LDAC codec to our pipewire builds. This will provide higher audio quality for bluetooth headsets that support it. &lt;a href="https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/35267"&gt;!35267&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;John contributed 3 different fixes for Nvidia and snapd:
&lt;ul&gt;
&lt;li&gt;Adapting our firmware installation for the new 615 Nvidia driver. &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5122"&gt;!5122&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Making Nvidia graphics cards work inside snap applications. &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5146"&gt;!5146&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fixed a regression with snapd’s apparmour profiles. &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5123"&gt;!5123&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We haven’t been sitting still either:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Hari, Jonas and Valentin ironed out various issues with our zswap setup. &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5090"&gt;!5090&lt;/a&gt;, &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5101"&gt;!5101&lt;/a&gt;, &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5118"&gt;!5118&lt;/a&gt;, &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5135"&gt;!5135&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;While it used to be a nightly-only feature, we think it is now rebust enough for everyone, so we enabled zswap in OS Preview as well.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;We now enable the extra-codecs feature by default. This was introduced earlier this year to expand codec support, but it required users to enable it manually. &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5109"&gt;!5109&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Jonas enabled speaker support on the Dell XPS 14 and other modern Intel laptops. &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5119"&gt;!5119&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Our installer now offers to erase the user’s drive before installation. &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5112"&gt;!5112&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Valentin backported a few &lt;a href="https://openprinting.github.io/cups/"&gt;CUPS&lt;/a&gt; patches to fix printing &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5009"&gt;!5009&lt;/a&gt;, &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5097"&gt;!5097&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Minor documentation touchups by Hari, zyxhere, Jonas and Tobias &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/4994"&gt;!4994&lt;/a&gt;, &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5056"&gt;!5056&lt;/a&gt;, &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5092"&gt;!5092&lt;/a&gt;, &lt;a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/5105"&gt;!5105&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;h2 id="events"&gt;Events&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/f466c6ffcecdae942d1aefc65f376092b082b6df83d4873036b8105c022613d2"&gt;Evangelos “GeopJr” Paterakis 🏳️‍⚧️🏳️‍🌈&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Come visit us in FOSSCOMM, Athens!&lt;/p&gt;
&lt;p&gt;We will have a booth this weekend in the University of West Attica on 31st October and 1st November.&lt;/p&gt;
&lt;p&gt;There will be t-shirts, stickers and community members available to chat!&lt;/p&gt;
&lt;p&gt;&lt;a href="https://2026.fosscomm.gr/"&gt;https://2026.fosscomm.gr/&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="thats-all-for-this-week"&gt;That’s all for this week!&lt;/h2&gt;
&lt;p&gt;See you next week, and be sure to stop by &lt;a href="https://matrix.to/#/#thisweek:gnome.org"&gt;#thisweek:gnome.org&lt;/a&gt; with updates on your own projects!&lt;/p&gt;</description>
      <guid isPermaLink="false">https://thisweek.gnome.org/posts/2026/10/twig-272/</guid>
      <pubDate>Fri, 30 Oct 2026 22:08:41 +0000</pubDate>
    </item>
    <item>
      <title>GIMP: GIMP 3.2.8 Released</title>
      <link>https://www.gimp.org/news/2026/11/02/gimp-3-2-8-released/</link>
      <description>&lt;p&gt;We’re glad to announce the release of &lt;a href="https://www.gimp.org/downloads"&gt;&lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2.8&lt;/a&gt;!
This new stable release contains a number of bugfixes and security updates from
new and long-time contributors.&lt;/p&gt;
&lt;div class="toc"&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#general-updates-and-ux-improvements"&gt;General Updates and &lt;span class="caps"&gt;UX&lt;/span&gt; Improvements&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#highlighting-new-contributors-work"&gt;Highlighting New Contributor’s Work&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#system-specific-updates"&gt;System-specific Updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#security-updates"&gt;Security Updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#around-gimp"&gt;Around &lt;span class="caps"&gt;GIMP&lt;/span&gt;&lt;/a&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#documentation-for-resource-makers"&gt;Documentation for resource makers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#new-mirrors"&gt;New Mirrors&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#release-stats"&gt;Release Stats&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#downloading-gimp-328"&gt;Downloading &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2.8&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gimp.org/feeds/atom.xml#whats-next"&gt;What’s Next&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;p&gt;This news posts provides an overview of the changes since &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2.6. For a more detailed
review, check out the &lt;a href="https://gitlab.gnome.org/GNOME/gimp/-/blob/22b9608d8823bb5cb43f190367e580fcc4860803/NEWS"&gt;&lt;span class="caps"&gt;NEWS&lt;/span&gt;&lt;/a&gt; changelog.&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Wilber-o'-Lantern" src="https://www.gimp.org/news/2026/11/02/gimp-3-2-8-released/wilber-o-lantern.jpeg"/&gt;
&lt;figcaption&gt;
&lt;em&gt;Wilber-o’-Lantern, &lt;span class="caps"&gt;CC&lt;/span&gt; &lt;span class="caps"&gt;BY&lt;/span&gt;-&lt;span class="caps"&gt;SA&lt;/span&gt; 4.0, October 31st, 2026&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;h1 id="general-updates-and-ux-improvements"&gt;General Updates and &lt;span class="caps"&gt;UX&lt;/span&gt; Improvements&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#general-updates-and-ux-improvements" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The &lt;a href="https://docs.gimp.org/3.2/en/script-fu-addborder.html"&gt;Add Border&lt;/a&gt; filter now allows you
to create semi-transparent borders based on the color you choose in the filter.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Jehan&lt;/strong&gt; fixed a bug introduced in &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2.6 when we added better support for cutting/copying
from layer groups. Non-rectangular selections on layers within a layer group will now be copied
over correctly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Bruno Lopes&lt;/strong&gt; corrected an issue where the cursor coordinates did not always update in the
status bar when changing between different applications.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;denzjos&lt;/strong&gt; helped us identify a bug with the Levels tool where picking input levels with
the Color Picker tool would report incorrect values when working with non-destructive filters.
&lt;strong&gt;Jehan&lt;/strong&gt; then developed a fix for it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Harsh Verma&lt;/strong&gt; has implemented a new &lt;abbr title="Graphical User Interface"&gt;&lt;span class="caps"&gt;GUI&lt;/span&gt;&lt;/abbr&gt; testing suite in
&lt;span class="caps"&gt;GIMP&lt;/span&gt; so we can better check for regressions in the &lt;span class="caps"&gt;GUI&lt;/span&gt; during development. He is preparing a news post that
will go over this in more detail, which we will share soon!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Jehan&lt;/strong&gt; improved our font-loading code so that it can be cancelled early (for instance, when quitting
&lt;span class="caps"&gt;GIMP&lt;/span&gt; while the fonts are still loading). This should speed up our shut-down times.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Bruno Lopes&lt;/strong&gt; made improvements to some dialogs so they appear on the correct screen for users with multiple monitors.
In addition, the &lt;a href="https://docs.gimp.org/3.2/en/gimp-view-dot-for-dot.html"&gt;Dot to Dot&lt;/a&gt; setting now works again.
It was reporting wrong pixel density since &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.0.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Jacob Boerema&lt;/strong&gt; backported some fixes for the Metadata Editor and Viewer feature, as part of his larger work
in the development branch.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Alx Sa&lt;/strong&gt; and &lt;strong&gt;Bruno Lopes&lt;/strong&gt; added more definitions to our theme file so that &lt;span class="caps"&gt;GIMP&lt;/span&gt; looks the same on each platform.&lt;/p&gt;
&lt;h1 id="highlighting-new-contributors-work"&gt;Highlighting New Contributor’s Work&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#highlighting-new-contributors-work" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;All contributions to &lt;span class="caps"&gt;GIMP&lt;/span&gt; from the community are valued! We want to highlight work from some of
the newer contributors here.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Infinity&lt;/strong&gt; made several improvements to our text tool for this release! In particular, they
improved text cursor movement when editing Right-to-Left languages and mitigated issues when
editing text with negative &lt;a href="https://en.wikipedia.org/wiki/Kerning"&gt;kerning&lt;/a&gt;.&lt;br/&gt;
As a side effect of this bug fix, we actually get much better support of
&lt;abbr title="Right-to-Left"&gt;&lt;span class="caps"&gt;RTL&lt;/span&gt;&lt;/abbr&gt; text as well as of mix of &lt;abbr title="Left-to-Right"&gt;&lt;span class="caps"&gt;LTR&lt;/span&gt;&lt;/abbr&gt;
and &lt;span class="caps"&gt;RTL&lt;/span&gt; texts.
The on-canvas dialog now has two new icons for text directions, and the tool automatically detects
your base text direction, as defined by rule P2 of the &lt;a href="https://www.unicode.org/reports/tr9/#P2"&gt;Unicode Bidirectional
Algorithm&lt;/a&gt;, unless you manually override by clicking one
of the buttons.&lt;/p&gt;
&lt;figure&gt;
&lt;figcaption&gt;
&lt;em&gt;Showcasing improved support for &lt;span class="caps"&gt;RTL&lt;/span&gt; text - &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2.8&lt;/em&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;strong&gt;Aruius&lt;/strong&gt; improved our color picking display GUIs, so you see more minor changes in colors when editing.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Chiem Whua Ma&lt;/strong&gt; helped resolve an issue on Windows where the &lt;span class="caps"&gt;UI&lt;/span&gt; would appear to freeze when moving
the canvas after opening multiple images at once. They also fixed a bug where vector layers would be
offset incorrect after the &lt;a href="https://docs.gimp.org/3.2/en/gimp-image-resize.html"&gt;canvas was resized&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Manu Cornet&lt;/strong&gt; has focused on several performance fixes for &lt;span class="caps"&gt;GIMP&lt;/span&gt;. For this release, they improved
caching when drawing gradients larger than 6000 x 6000 pixels. They also made the “marching ants”
display for selections run more efficiently. Additionally, they improved how channels are displayed
in the Channel dock when a dark theme is set. Finally they sped up the display time for the Preferences dialog.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;balooii&lt;/strong&gt; made several fixes as well. For instance, they updated our external copy and paste code to
also pass along the &lt;abbr title="Dots per inch"&gt;&lt;span class="caps"&gt;DPI&lt;/span&gt;&lt;/abbr&gt; settings for the image; this means that other
software can properly rescale what you paste if they have a different setting that what you used in
&lt;span class="caps"&gt;GIMP&lt;/span&gt;. They also made our Debug dialog themeable and translatable (though we hope you don’t get the
opportunity to see their work in this area!)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MrYoranimo&lt;/strong&gt; fixed an oversight in our raw data import plug-in, where images were not loaded as
binary data on Windows. This is a bit technical, but it meant that some raw data might not be interpreted
correctly. Their fix ensures that the data is loaded consistently on Windows as it has been on other platforms.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Dimitriy Ryazantcev&lt;/strong&gt; has continued their work on Windows icon and animated cursors. In this release,
they have updated our loading code to match how Windows orders and groups icons in the file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;abderraouf&lt;/strong&gt; updated our &lt;span class="caps"&gt;HEIF&lt;/span&gt; loading code to allow for loading larger images.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Chomu&lt;/strong&gt; updated our menu code to allow plug-in and script developers to add submenus in named menu sections.
For instance the following code will add a submenu &lt;code&gt;Custom/&lt;/code&gt; below other &lt;code&gt;Paste as&lt;/code&gt; actions and your new plug-in action in it:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="n"&gt;gimp_procedure_add_menu_path&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;procedure&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;"&amp;lt;Image&amp;gt;/File/[Paste as]/Custom"&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;Also &lt;code&gt;gimp_plug_in_add_menu_branch()&lt;/code&gt; has been deprecated (though it was already not working properly anyway
so we expect nobody was using it).&lt;/p&gt;
&lt;h1 id="system-specific-updates"&gt;System-specific Updates&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#system-specific-updates" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Bruno Lopes&lt;/strong&gt; continues their work to improve &lt;span class="caps"&gt;GIMP&lt;/span&gt;’s integration on different platforms. To name a few updates:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;On macOS 27+, title bars are displayed with background colors again. Icons on the menu bar should also appear
accordingly. Since the release of &lt;a href="https://en.wikipedia.org/wiki/MacOS_Golden_Gate"&gt;Golden Gate&lt;/a&gt;, these were
being rendered transparently due to breaking changes on the macOS side.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On macOS 14+, we now use the &lt;a href="https://developer.apple.com/documentation/screencapturekit"&gt;ScreenCaptureKit &lt;span class="caps"&gt;API&lt;/span&gt;&lt;/a&gt;
for taking screenshots. &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On Intel-based macOS, &lt;span class="caps"&gt;GIMP&lt;/span&gt; should run without warnings from
&lt;a href="https://en.wikipedia.org/wiki/Gatekeeper_(macOS)"&gt;GateKeeper&lt;/a&gt; thanks to us now consistently notarizing Python. &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;We now display a 1/0 value for switches on macOS based on the “Differentiate without color” setting.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Transparency is retained when copying an image from certain apps to &lt;span class="caps"&gt;GIMP&lt;/span&gt;, instead of it showing as black.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The longstanding “Blank &lt;span class="caps"&gt;UI&lt;/span&gt;” bug that happened on startup for certain macOS computers should be finally fixed!&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Print Preview (aka Image Settings tab) should now work with the Windows 11 Unified Print Dialog on that platform.
In addition, Page Setup should now use the correct printer, not just the default one on Windows.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On Windows, “Merged title bar” settings now play nicer with system features such as minimizing from the task bar
and title bar shadowing effets.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The Screenshot feature now works better on &lt;span class="caps"&gt;HDR&lt;/span&gt; displays on Windows.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;AppImage compatibility was improved to support installing &lt;a href="https://pythonwheels.com/"&gt;Python Wheels&lt;/a&gt; from pip
like Flatpak and Snap.
Note, however, that our minimum version for 3.2 continues to be a distro released after Debian 13 (Trixie).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id="security-updates"&gt;Security Updates&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#security-updates" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;As many free and open source software projects can attest, we have continued to receive a large quantity of
security reports due to recent advances in software scanning and testing programs. &lt;strong&gt;Jacob Boerema&lt;/strong&gt; and
&lt;strong&gt;Alx Sa&lt;/strong&gt; along with new contributors &lt;strong&gt;Mike Gorse&lt;/strong&gt;, &lt;strong&gt;Dirk Müller&lt;/strong&gt;, and &lt;strong&gt;Alynx Zhou&lt;/strong&gt; have proactively
responded to and patched these reported issues when applicable.&lt;/p&gt;
&lt;p&gt;We take security seriously, but this is not quite as scary as it first sounds. There are no personal accounts
or banking information to exploit since we of course don’t access or store that information! The most common
report that we get is our older image plug-ins and legacy filters are too trusting of the image size information
provided by the image file, and if you intentionally alter this information, you could cause the plug-in (not &lt;span class="caps"&gt;GIMP&lt;/span&gt;
itself) to crash.&lt;/p&gt;
&lt;h1 id="around-gimp"&gt;Around &lt;span class="caps"&gt;GIMP&lt;/span&gt;&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#around-gimp" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="documentation-for-resource-makers"&gt;Documentation for resource makers&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#documentation-for-resource-makers" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Bruno Lopes&lt;/strong&gt; wrote two new tutorials on developer.gimp.org:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developer.gimp.org/resource/writing-a-plug-in/tutorial-i18n/"&gt;Internationalizing plug-ins&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.gimp.org/resource/writing-a-filter/i18n/"&gt;Internationalizing filters&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These articles should help plug-in and script developers who want to make their plug-ins translatable,
either by themselves or by members of the community. This will be especially helpful as we make progress
on creating an built-in Extension repo for easily downloading and installing plug-ins, filters, and more.
(More information on that coming soon!)&lt;/p&gt;
&lt;h2 id="new-mirrors"&gt;New Mirrors&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#new-mirrors" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Randhost, in Portugal, and &lt;span class="caps"&gt;ZEROLAG&lt;/span&gt;, in Romania, have graciously offered to serve mirrors for &lt;span class="caps"&gt;GIMP&lt;/span&gt; downloads.&lt;/p&gt;
&lt;p&gt;Mirrors help &lt;span class="caps"&gt;GIMP&lt;/span&gt; be available for download at high speeds wherever you are in the world.&lt;/p&gt;
&lt;p&gt;Does your organization wish to be one of our &lt;a href="https://www.gimp.org/donating/sponsors.html#official-mirrors"&gt;official mirror sponsors&lt;/a&gt;?
Create a &lt;a href="https://gitlab.gnome.org/Infrastructure/gimp-web/-/issues/new?description_template=New_Mirror"&gt;request to become an official mirror&lt;/a&gt;!&lt;/p&gt;
&lt;h1 id="release-stats"&gt;Release Stats&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#release-stats" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Since &lt;a href="https://www.gimp.org/release/3.2.6/"&gt;&lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2.6&lt;/a&gt;, in the main &lt;span class="caps"&gt;GIMP&lt;/span&gt; repository:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;82 reports were closed as &lt;span class="caps"&gt;FIXED&lt;/span&gt;.&lt;/li&gt;
&lt;li&gt;46 merge requests were merged.&lt;/li&gt;
&lt;li&gt;300 commits were pushed.&lt;/li&gt;
&lt;li&gt;11 translations were updated: Chinese (China), Dutch, Georgian, Kazakh, Lithuanian, Norwegian Bokmål, Norwegian Nynorsk, Slovenian, Swedish, Turkish, Ukrainian.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;27 people contributed changes or fixes to &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2.8 codebase (order
is determined by number of commits; some people are in several groups):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;10 developers to core code: Bruno Lopes, Jehan, Alx Sa, Harsh Verma, Manu Cornet, Chiem Whua Ma, balooii balooii, infinity, Chomu, aruius.&lt;/li&gt;
&lt;li&gt;11 developers to plug-ins or modules: Alx Sa, Bruno Lopes, Jacob Boerema, Dimitriy Ryazantcev, Alynx Zhou, Dirk Müller, Harsh Verma, Jehan, Mike Gorse, MrYoranimo, phoinix.&lt;/li&gt;
&lt;li&gt;11 translators: Anders Jonsson, Dick Groskamp, Kolbjørn Stuestøl, Martin, luming zh, Aurimas Aurimas Černius, Baurzhan Muftakhidinov, Ekaterine Papava, Kjartan Maraas, Yuri Chornoivan, Emin Tufan Çetin.&lt;/li&gt;
&lt;li&gt;1 theme designers: Alx Sa.&lt;/li&gt;
&lt;li&gt;4 build, packaging or &lt;span class="caps"&gt;CI&lt;/span&gt; contributors: Bruno Lopes, Jehan, Harsh Verma, Alx Sa.&lt;/li&gt;
&lt;li&gt;2 contributors on other types of resources: Jehan, Bruno Lopes.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Contributions on other repositories in the GIMPverse (order is determined by
number of commits):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;code&gt;gimp-test-images&lt;/code&gt; (unit testing repository) repository had 2 commits by 1 contributors: Jacob Boerema.&lt;/li&gt;
&lt;li&gt;The flatpak release had 12 commits by 2 contributors: Bruno Lopes, Jehan.&lt;/li&gt;
&lt;li&gt;Our main website (what you are reading right now) had 65 commits by 3 contributors: Bruno Lopes, Jehan, Alx Sa.&lt;/li&gt;
&lt;li&gt;Our &lt;a href="https://developer.gimp.org/"&gt;developer website&lt;/a&gt; had 56 commits by 5 contributors: Bruno Lopes, Jehan, Harsh Verma, Alx Sa, Denis Rangelov.&lt;/li&gt;
&lt;li&gt;Our &lt;a href="https://docs.gimp.org/"&gt;3.0 documentation&lt;/a&gt; had 197 commits by 8 contributors: Jacob Boerema, Dick Groskamp, Kolbjørn Stuestøl, Anders Jonsson, Marco Ciampa, Jehan, Balázs Úr, Yuri Chornoivan.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Let’s not forget to thank all the people who help us triaging in Gitlab, report
bugs and discuss possible improvements with us.
Our community is deeply thankful as well to the internet warriors who manage our
various &lt;a href="https://www.gimp.org/discuss.html"&gt;discussion channels&lt;/a&gt; or social
network accounts such as Ville Pätsi, Liam Quin, Michael Schumacher and Sevenix!&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Note: considering the number of parts in &lt;span class="caps"&gt;GIMP&lt;/span&gt; and around, and how we
get statistics through &lt;code&gt;git&lt;/code&gt; scripting, errors may slip inside these
stats. Feel free to tell us if we missed or mis-categorized some
contributors or contributions.&lt;/em&gt;&lt;/p&gt;
&lt;h1 id="downloading-gimp-328"&gt;Downloading &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2.8&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#downloading-gimp-328" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;You will find all our official builds on &lt;a href="https://www.gimp.org/downloads/"&gt;&lt;span class="caps"&gt;GIMP&lt;/span&gt; official website (gimp.org)&lt;/a&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Linux AppImages for x86 and &lt;span class="caps"&gt;ARM&lt;/span&gt; (64-bit)&lt;/li&gt;
&lt;li&gt;Linux Flatpaks for x86 and &lt;span class="caps"&gt;ARM&lt;/span&gt; (64-bit)&lt;/li&gt;
&lt;li&gt;Linux Snaps for x86 and &lt;span class="caps"&gt;ARM&lt;/span&gt; (64-bit)&lt;/li&gt;
&lt;li&gt;Universal Windows installer for x86 and &lt;span class="caps"&gt;ARM&lt;/span&gt; (64-bit)&lt;/li&gt;
&lt;li&gt;Microsoft Store for x86 and &lt;span class="caps"&gt;ARM&lt;/span&gt; (64-bit)&lt;/li&gt;
&lt;li&gt;macOS &lt;span class="caps"&gt;DMG&lt;/span&gt; packages for Intel/x86 and Apple/&lt;span class="caps"&gt;ARM&lt;/span&gt; hardware (64-bit)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Other packages made by third-parties are obviously expected to follow (Linux or *&lt;span class="caps"&gt;BSD&lt;/span&gt; distributions’ packages, etc).&lt;/p&gt;
&lt;h1 id="whats-next"&gt;What’s Next&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#whats-next" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;While we’ve been making periodic updates to the stable &lt;span class="caps"&gt;GIMP&lt;/span&gt; 3.2 branch, we’ve also been hard at work on developing
the next version of &lt;span class="caps"&gt;GIMP&lt;/span&gt;. There’s a lot of &lt;a href="https://floss.social/@GIMP/117501896938889952"&gt;cool things in progress&lt;/a&gt;,
and we look forward to sharing more about that with you all soon!&lt;/p&gt;
&lt;p&gt;Don’t forget you can &lt;a href="https://www.gimp.org/donating/"&gt;donate and personally fund &lt;span class="caps"&gt;GIMP&lt;/span&gt; developers&lt;/a&gt;, as a way to
give back and accelerate the development of &lt;span class="caps"&gt;GIMP&lt;/span&gt;. Community commitment helps the project to grow stronger!&lt;/p&gt;</description>
      <guid isPermaLink="false">https://www.gimp.org/news/2026/11/02/gimp-3-2-8-released/</guid>
      <pubDate>Sun, 01 Nov 2026 23:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Daniel García Moreno: I Know Kung Fu</title>
      <link>https://danigm.net/i-know-kung-fu.html</link>
      <description>&lt;p class="img"&gt;
&lt;img src="https://danigm.net/pictures/i-know-kungfu.jpg"/&gt;
&lt;/p&gt;
&lt;p&gt;In the first "The Matrix" movie we have the famous scene of Neo just
connected to the computer and opening his eyes and saying "I know kung
fu". Something that was really cool in early 2000 sounds like a
dystopia to me nowadays.&lt;/p&gt;
&lt;p&gt;I don't want to "know kung fu", I want to practice Kung Fu! So I
prefer "The Karate Kid" way:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;First learn stand, then learn fly. Nature rule, Daniel-san, not mine.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;And talking about movies, there are a lot of movies that shows the
&lt;a href="https://en.wikipedia.org/wiki/Hero%27s_journey"&gt;Hero's journey&lt;/a&gt; structure. And it's not relevant if Daniel-san win
the last fight or if Rocky defeats Apollo, because the important part
of the story is the journey, is the hero starting the adventure and
how the &lt;strong&gt;path changes him&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;And this exact principle applies to everything in live, everyone knows
that shortcuts doesn't have value. You can win, you can be faster,
stronger, bigger, but you are missing the point, you are missing that
"journey before destination" is always true for any &lt;a href="https://coppermind.net/wiki/Knights_Radiant/Immortal_Words#The_First_Ideal"&gt;Radiant Knight&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In The Matrix the hero's journey is not related to the Kung Fu, and
that was just some cool way of introducing the action, the learning is
in a different path because in other case we won't have any movie.&lt;/p&gt;
&lt;p&gt;Neo doesn't care about Kung Fu, it's just something nice to fight the
Agent Smith (What an irony). Daniel-san want's to learn to fight to
defend himself, but at the end, fighting is not important, at the end
he actually learns karate, and that changes him, and Miyagi and Daniel
care about karate.&lt;/p&gt;
&lt;p&gt;Gen AI "externalizes" the journey, and it's very tempting to take the
shortcut and go directly to get the trophy. But doing that we are
removing all the value from the output, we are not learning, we are
not doing the journey and we don't change at the end, so actually,
using Gen AI is like a waste of time.&lt;/p&gt;
&lt;h2&gt;No one cares... About something&lt;/h2&gt;
&lt;p&gt;I've been thinking lately about why people uses AI, because even with
all the advertisement and pressure I sincerely do not see any value in
using gen AI, I don't need this technology and the only outcome that
I'm seeing today is that's destroying everything that I loved or cared
about.&lt;/p&gt;
&lt;p&gt;But going to the point, if there are so many people using and
promoting this, maybe they see some value and thinking about it and
just talking with different kind of people I'm starting to see a
trend. Most of the people are okay with the usage of AI for anything
that they don't care, and of course, they are against the usage in
anything that they consider important, everything where they see
value.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Designers&lt;/strong&gt; will say that the AI is generating aberrant images, and
stealing the work of others, ignoring copyright and attribution and
depreciating the quality, but they will be okay to use it to generate
text, translate, write code, etc.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Writers&lt;/strong&gt; will say that any text generated with AI is poorly written,
but they won't see any problem in using a gen AI image for their blog
post.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Musicians&lt;/strong&gt; will be disgusted by the AI generated music, but maybe they
don't see any problem playing a vibe-coded video game.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Programmers&lt;/strong&gt;...&lt;/p&gt;
&lt;p&gt;Okay, maybe not everyone follows this pattern, or maybe that's exactly
what's happening. Maybe some devs don't care about coding but care
about reviewing, others don't care about testing but care about
coding, and others don't care at all and vibe-code everything.&lt;/p&gt;
&lt;p&gt;I don't see any value in &lt;em&gt;any&lt;/em&gt; gen AI usage because I usually care
about the output, but also about the process, and the how and why is,
most of the times, more relevant than the final outcome.&lt;/p&gt;
&lt;p&gt;That's why I try to use only free software, and I'm not using Windows
or Mac, that's why sometimes I choose to use a tool just because it's
written in python and not in java.&lt;/p&gt;
&lt;p&gt;So to me, the quality of code is not more important than the license,
it's not more important than technology used, and of course it's not
more important than who and why.&lt;/p&gt;
&lt;h2&gt;Because I care... And you should care too!&lt;/h2&gt;
&lt;p&gt;I've a "Software Engineer" university degree. But the final paper has
no value. What's important to me at the end is that I started that
career because my brother introduces me to debian and free software in
the 90's. What's important is my relation with peers, professors, my
activity in the local Linux User Group, days studying, the failure and
the success after understanding interesting math... I don't need an AI
generated title, and I don't want people with the "Software Engineer"
title, I just want more people to have the opportunity to experience
the same growth path, the journey.&lt;/p&gt;
&lt;p&gt;What's the value of music? It's just something to listen when you are
working, to hide the sound of life that surround you? Anyone that
had listen any musician in live sees the value, the difference. It
doesn't matter that you can make "better" music and record and play
without any mistake, but we value the live performance, because the
music is not the important part, the important part is the musician
and the listener, the communication. And it's not the same if you
listen the exact same song from someone that just lost his father.&lt;/p&gt;
&lt;p&gt;What's my job? It's just the code that I write? To me it's clear
that's not, and shouldn't be. My job is to create software, I don't
care if a gen AI can do that, other people can do that before I
started to be able to do it, and I'm not asking others to do it for
me.&lt;/p&gt;
&lt;p&gt;Of course, not caring about something is natural, no one is interested
in all the human activity and just delegate some parts to continue
working on what's important to them. But after thinking about it, I
can't just ignore it.&lt;/p&gt;
&lt;p&gt;Now, when I need an image, that I don't care enough to create myself,
I will care just a little to find someone who actually care and
delegate to him instead to a big corp AI. When I need some text to
read, I will look for someone who actually cares about the text. And,
of course, when I need any software or application , that I don't care
enough to create myself, I will look for some developer that actually
care about the code and for sure I won't ask any gen AI.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://danigm.net/i-know-kung-fu.html</guid>
      <pubDate>Wed, 04 Nov 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Michael Meeks: 2026-11-04 Wednesday</title>
      <link>https://meeksfamily.uk/~michael/blog/2026-11-04.html</link>
      <description>&lt;ul&gt; &lt;!-- --&gt;
&lt;li&gt;
		Catch up with Astor &amp;amp; Damien, Eloy, Julie, into Cambridge
	for a shared lunch - arriving an hour late: daylight saving joy.
	Caught up with the team, chat with Richard.
	&lt;/li&gt;
&lt;li&gt;
		Published the next strip: Blake gets on with it - a triumph for the community,
	although often whether he is part of the community seems rather context dependent
		&lt;center&gt;
&lt;a href="https://www.collaboraonline.com/torf/torf84"&gt;&lt;img alt="The Open Road to Freedom - strip#84 - Blake gets on with it" src="https://meeksfamily.uk/~michael/images/torf84-thumb.png"/&gt;&lt;/a&gt;
&lt;/center&gt;
&lt;/li&gt;
&lt;li&gt;
		Home, call with Anna, COOL TC meeting, out for a run
	with J. fine dinner, catch up with Dave.
	&lt;/li&gt;
&lt;li&gt;
		Worked late on reviews; endless text &amp;amp;
	spreadsheet-ness.
	&lt;/li&gt;
&lt;ul&gt;&lt;/ul&gt;&lt;/ul&gt;</description>
      <guid isPermaLink="false">https://meeksfamily.uk/~michael/blog/2026-11-04.html</guid>
      <pubDate>Wed, 04 Nov 2026 21:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Philipp Sauberzweig: Fellowship Update, 2026-11-06</title>
      <link>https://blogs.gnome.org/psauberz/2026/11/06/fellowship-update-2026-11-06/</link>
      <description>&lt;p&gt;&lt;span&gt;It’s&lt;/span&gt; &lt;span&gt;been&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;few&lt;/span&gt; &lt;span&gt;weeks&lt;/span&gt; &lt;span&gt;since&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;last&lt;/span&gt; &lt;span&gt;blog&lt;/span&gt; &lt;span&gt;post&lt;/span&gt; &lt;span&gt;about&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;work&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;GNOME&lt;/span&gt; &lt;span&gt;Design&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;Community&lt;/span&gt; &lt;span&gt;Management&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;part&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;Sovereign&lt;/span&gt; &lt;span&gt;Tech&lt;/span&gt; &lt;span&gt;Fellowship.&lt;/span&gt; &lt;span&gt;As&lt;/span&gt; &lt;span&gt;usual,&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;want&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;share&lt;/span&gt; &lt;span&gt;some&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;most&lt;/span&gt; &lt;span&gt;interesting&lt;/span&gt; &lt;span&gt;developments.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;Passkey Portal&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;Passkeys&lt;/span&gt; &lt;span&gt;are&lt;/span&gt; &lt;span&gt;an&lt;/span&gt; &lt;span&gt;easy&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;safe&lt;/span&gt; &lt;span&gt;way&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;sign&lt;/span&gt; &lt;span&gt;in,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;can&lt;/span&gt; &lt;span&gt;replace&lt;/span&gt; &lt;span&gt;passwords.&lt;/span&gt; &lt;span&gt;They’re&lt;/span&gt; &lt;span&gt;tied&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;website&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;issued&lt;/span&gt; &lt;span&gt;them,&lt;/span&gt; &lt;span&gt;so&lt;/span&gt; &lt;span&gt;they&lt;/span&gt; &lt;span&gt;can’t&lt;/span&gt; &lt;span&gt;be&lt;/span&gt; &lt;span&gt;phished.&lt;/span&gt; &lt;span&gt;Hackers&lt;/span&gt; &lt;span&gt;can’t&lt;/span&gt; &lt;span&gt;steal&lt;/span&gt; &lt;span&gt;them&lt;/span&gt; &lt;span&gt;from&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;website&lt;/span&gt; &lt;span&gt;because&lt;/span&gt; &lt;span&gt;its&lt;/span&gt; &lt;span&gt;servers&lt;/span&gt; &lt;span&gt;don’t&lt;/span&gt; &lt;span&gt;store&lt;/span&gt; &lt;span&gt;your&lt;/span&gt; &lt;span&gt;private&lt;/span&gt; &lt;span&gt;key.&lt;/span&gt; &lt;span&gt;You&lt;/span&gt; &lt;span&gt;can&lt;/span&gt; &lt;span&gt;learn&lt;/span&gt; &lt;span&gt;more&lt;/span&gt; &lt;span&gt;about&lt;/span&gt; &lt;span&gt;passkeys&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;how&lt;/span&gt; &lt;span&gt;they&lt;/span&gt; &lt;span&gt;work&lt;/span&gt; &lt;span&gt;at&lt;/span&gt; &lt;span&gt;&lt;a class="external" href="https://whatarepasskeys.info/"&gt;whatarepasskeys.info&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;People&lt;/span&gt; &lt;span&gt;have&lt;/span&gt; &lt;span&gt;been&lt;/span&gt; &lt;span&gt;working&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;bring&lt;/span&gt; &lt;span&gt;passkey&lt;/span&gt; &lt;span&gt;support&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;Linux&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;several&lt;/span&gt; &lt;span&gt;years,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;we’re&lt;/span&gt; &lt;span&gt;getting&lt;/span&gt; &lt;span&gt;closer&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;making&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;available&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;users.&lt;/span&gt; &lt;span&gt;Just&lt;/span&gt; &lt;span&gt;today,&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://github.com/flatpak/xdg-desktop-portal/pull/1889"&gt;&lt;span&gt;experimental&lt;/span&gt; &lt;span&gt;credentials&lt;/span&gt; &lt;span&gt;portal&lt;/span&gt;&lt;/a&gt; &lt;span&gt;was&lt;/span&gt; &lt;span&gt;merged&lt;/span&gt; &lt;span&gt;into&lt;/span&gt; &lt;span&gt;xdg-desktop-portal.&lt;/span&gt; &lt;span&gt;To&lt;/span&gt; &lt;span&gt;support&lt;/span&gt; &lt;span&gt;its&lt;/span&gt; &lt;span&gt;implementation&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;GNOME,&lt;/span&gt; &lt;span&gt;I’ve&lt;/span&gt; &lt;span&gt;spent&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;lot&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;time&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/Teams/Design/os-mockups/-/work_items/232"&gt;&lt;span&gt;researching&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;refining&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;design&lt;/span&gt; &lt;span&gt;of&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;credentials&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/Teams/Design/os-mockups/-/work_items/232"&gt;portal&lt;/a&gt;. &lt;/span&gt;&lt;span&gt;Below&lt;/span&gt; &lt;span&gt;is&lt;/span&gt; &lt;span&gt;an&lt;/span&gt; &lt;span&gt;excerpt&lt;/span&gt; &lt;span&gt;from&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; c&lt;span&gt;redentials portal&lt;/span&gt; &lt;span&gt;mockup. T&lt;/span&gt;&lt;span&gt;ake&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;look&lt;/span&gt; &lt;span&gt;at&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/Teams/Design/os-mockups/-/blob/master/portals/credentials-portal-philipp.png"&gt;&lt;span&gt;full&lt;/span&gt; &lt;span&gt;mockup&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;OS&lt;/span&gt; &lt;span&gt;mockups&lt;/span&gt; &lt;span&gt;repository&lt;/span&gt;&lt;/a&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;all&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;user&lt;/span&gt; &lt;span&gt;interaction&lt;/span&gt; &lt;span&gt;flows.&lt;/span&gt;&lt;/p&gt;
&lt;figure class="wp-caption alignnone" id="attachment_197" style="width: 2080px;"&gt;&lt;img alt="Detail of the credentials portal mockup showing the passkey creation" class="size-full wp-image-197" height="862" src="https://blogs.gnome.org/psauberz/files/2026/11/credentials-portal-excerpt.png" width="2560"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-197"&gt;Some details of the credentials portal mockup showing the passkey creation&lt;/figcaption&gt;&lt;/figure&gt;
&lt;h2&gt;Libadwaita&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;In&lt;/span&gt; &lt;span&gt;my&lt;/span&gt; &lt;span&gt;last&lt;/span&gt; &lt;span&gt;blog&lt;/span&gt; &lt;span&gt;post,&lt;/span&gt; &lt;span&gt;I&lt;/span&gt; &lt;span&gt;wrote&lt;/span&gt; &lt;span&gt;about&lt;/span&gt; &lt;span&gt;standardizing&lt;/span&gt; &lt;span&gt;scale&lt;/span&gt; &lt;span&gt;rows&lt;/span&gt; &lt;span&gt;in&lt;/span&gt; &lt;span&gt;libadwaita&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; &lt;span&gt;mentioned&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;code class="rounded bg-muted px-1.5 py-0.5 font-mono text-sm"&gt;ActionRow&lt;/code&gt; &lt;span&gt;would&lt;/span&gt; &lt;span&gt;likely&lt;/span&gt; &lt;span&gt;get&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;generic&lt;/span&gt; &lt;span&gt;bottom&lt;/span&gt; &lt;span&gt;child&lt;/span&gt; &lt;span&gt;widget&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;support&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;change.&lt;/span&gt; &lt;span&gt;This&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;now&lt;/span&gt; &lt;span&gt;landed&lt;/span&gt; &lt;span&gt;as&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;a class="external" href="https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/property.ActionRow.body.html"&gt;&lt;code class="rounded bg-muted px-1.5 py-0.5 font-mono text-sm"&gt;ActionRow:body&lt;/code&gt;&lt;/a&gt; &lt;span&gt;property,&lt;/span&gt; &lt;span&gt;and&lt;/span&gt; the calendar app &lt;a class="external" href="https://flathub.org/de/apps/org.gnome.gitlab.TitouanReal.Era"&gt;&lt;span&gt;Era&lt;/span&gt;&lt;/a&gt; &lt;span&gt;already&lt;/span&gt; &lt;span&gt;uses&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;a class="external" href="https://gitlab.gnome.org/TitouanReal/Era/-/merge_requests/189"&gt;&lt;span&gt;implement&lt;/span&gt; &lt;span&gt;its&lt;/span&gt; &lt;span&gt;participants&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://gitlab.gnome.org/TitouanReal/Era/-/merge_requests/189"&gt;row&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;figure class="wp-caption alignnone" id="attachment_200" style="width: 410px;"&gt;&lt;img alt="Screenshot of Era with a participants row based using the new ActionRow:body property" class="wp-image-200 size-full" height="1500" src="https://blogs.gnome.org/psauberz/files/2026/11/era-participants-row.png" width="820"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-200"&gt;Screenshot of the calendar app Era with a participants row based using the new ActionRow:body property&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;The new scale style has also &lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/1832"&gt;already landed&lt;/a&gt; in the upcoming libadwaita version.&lt;/p&gt;
&lt;figure class="wp-caption alignnone" id="attachment_208" style="width: 588px;"&gt;&lt;img alt="Screenshot of the new scale style with pill shaped knob" class="size-full wp-image-208" height="164" src="https://blogs.gnome.org/psauberz/files/2026/11/scale-style.png" width="1176"/&gt;&lt;figcaption class="wp-caption-text" id="caption-attachment-208"&gt;Screenshot of the new scale style with pill shaped knob&lt;/figcaption&gt;&lt;/figure&gt;
&lt;h2&gt;Other&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;If&lt;/span&gt; &lt;span&gt;you’ve&lt;/span&gt; &lt;span&gt;read&lt;/span&gt; &lt;span&gt;this&lt;/span&gt; &lt;span&gt;blog&lt;/span&gt; &lt;span&gt;before,&lt;/span&gt; &lt;span&gt;you&lt;/span&gt; &lt;span&gt;may&lt;/span&gt; &lt;span&gt;have&lt;/span&gt; &lt;span&gt;noticed&lt;/span&gt; &lt;span&gt;that&lt;/span&gt; &lt;span&gt;the&lt;/span&gt; &lt;span&gt;font&lt;/span&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;changed.&lt;/span&gt; &lt;a class="external" href="https://rsms.me/inter/"&gt;&lt;span&gt;Inter&lt;/span&gt;&lt;/a&gt; &lt;span&gt;has&lt;/span&gt; &lt;span&gt;been&lt;/span&gt; &lt;span&gt;installed&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;GNOME’s&lt;/span&gt; &lt;span&gt;WordPress&lt;/span&gt; &lt;span&gt;instance,&lt;/span&gt; &lt;span&gt;so&lt;/span&gt; &lt;span&gt;community&lt;/span&gt; &lt;span&gt;members&lt;/span&gt; &lt;span&gt;can&lt;/span&gt; &lt;span&gt;now&lt;/span&gt; &lt;span&gt;use&lt;/span&gt; &lt;span&gt;it&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;their&lt;/span&gt; &lt;span&gt;personal&lt;/span&gt; &lt;span&gt;GNOME&lt;/span&gt; &lt;span&gt;blogs&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;keep&lt;/span&gt; &lt;span&gt;their&lt;/span&gt; &lt;span&gt;typography&lt;/span&gt; &lt;span&gt;consistent&lt;/span&gt; &lt;span&gt;with&lt;/span&gt; &lt;a class="external" href="https://brand.gnome.org/"&gt;&lt;span&gt;GNOME’s&lt;/span&gt; &lt;span&gt;web&lt;/span&gt; &lt;/a&gt;&lt;span&gt;&lt;a class="external" href="https://brand.gnome.org/"&gt;standards&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks&lt;/span&gt; &lt;span&gt;for&lt;/span&gt; &lt;span&gt;reading!&lt;/span&gt; &lt;span&gt;Feel&lt;/span&gt; &lt;span&gt;free&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;leave&lt;/span&gt; &lt;span&gt;a&lt;/span&gt; &lt;span&gt;comment&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;this&lt;/span&gt; &lt;span&gt;blog&lt;/span&gt; &lt;span&gt;or&lt;/span&gt; &lt;span&gt;reach&lt;/span&gt; &lt;span&gt;out&lt;/span&gt; &lt;span&gt;to&lt;/span&gt; &lt;span&gt;me&lt;/span&gt; &lt;span&gt;on&lt;/span&gt; &lt;span&gt;Mastodon&lt;/span&gt; &lt;span&gt;or&lt;/span&gt; &lt;span&gt;Matrix.&lt;/span&gt;&lt;/p&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/psauberz/2026/11/06/fellowship-update-2026-11-06/</guid>
      <pubDate>Fri, 06 Nov 2026 16:22:35 +0000</pubDate>
    </item>
    <item>
      <title>Luis Villa: "What ride?": where libre software could go after LLMs</title>
      <link>https://lu.is/2026/11/what-ride-specifically/</link>
      <description>&lt;p&gt;&lt;em&gt;Blog post collecting in one place some thoughts from social media (&lt;a href="https://bsky.app/profile/lu.is/post/3mypzgveea22n"&gt;original post&lt;/a&gt;).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Armin Ronacher ran the same poll on Twitter, Bluesky, and Mastodon: &lt;a href="https://bsky.app/profile/mitsuhiko.at"&gt;&lt;em&gt;“Do you still write more than 20% of code by hand?”&lt;/em&gt;&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;My reaction, roughly: &lt;em&gt;sob.&lt;/em&gt; 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.&lt;/p&gt;
&lt;p&gt;In quoting Armin, I said I want to bring those folks “along for this ride”. &lt;a href="https://bsky.app/profile/harihareswara.net"&gt;Sumana&lt;/a&gt; asked the right question in reply: &lt;em&gt;what ride, specifically?&lt;/em&gt; 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?&lt;/p&gt;
&lt;p&gt;Here are some of the highlights:&lt;/p&gt;
&lt;h2 id="1-freedom-1-for-real-this-time"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#1-freedom-1-for-real-this-time" tabindex="-1"&gt;#&lt;/a&gt;1. Freedom 1, for real this time&lt;/h2&gt;
&lt;p&gt;Most important: I think we can get to a world where most users are actually empowered to take advantage of &lt;a href="https://www.gnu.org/philosophy/free-sw.html"&gt;Freedom 1&lt;/a&gt; — the freedom to study how a program works and change it to do what &lt;em&gt;you&lt;/em&gt; want.&lt;/p&gt;
&lt;p&gt;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 &lt;a href="https://github.com/cheeaun/phanpy"&gt;phanpy&lt;/a&gt;, and probably others I’m forgetting. That’s the promise we always wanted and I’m living it right now.&lt;/p&gt;
&lt;h2 id="2-higher-quality-because-best-practices-can-become-actual-practices"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#2-higher-quality-because-best-practices-can-become-actual-practices" tabindex="-1"&gt;#&lt;/a&gt;2. Higher quality, because best practices can become actual practices&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2 id="3-collaboration-can-better-include-non-coders"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#3-collaboration-can-better-include-non-coders" tabindex="-1"&gt;#&lt;/a&gt;3. Collaboration can better include non-coders?&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2 id="4-a-big-bad-guy-again"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#4-a-big-bad-guy-again" tabindex="-1"&gt;#&lt;/a&gt;4. A Big Bad Guy again&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2 id="5-finally-retiring-unsafe-by-design-c-and-c"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#5-finally-retiring-unsafe-by-design-c-and-c" tabindex="-1"&gt;#&lt;/a&gt;5. Finally retiring unsafe-by-design C and C++&lt;/h2&gt;
&lt;p&gt;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 &lt;a href="https://en.wikipedia.org/wiki/A_Deepness_in_the_Sky"&gt;&lt;em&gt;A Deepness in the Sky&lt;/em&gt;&lt;/a&gt;. 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.&lt;/p&gt;
&lt;h2 id="so--how-do-we-bring-folks-along"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#so--how-do-we-bring-folks-along" tabindex="-1"&gt;#&lt;/a&gt;So — how do we bring folks along?&lt;/h2&gt;
&lt;p&gt;None of these rides is guaranteed to happen, let alone to turn out well. They’re all &lt;em&gt;possibilities&lt;/em&gt; — and that’s exactly why I want a big tent of people coming along to steer them, and to keep us honest.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://lu.is/2026/11/what-ride-specifically/</guid>
      <pubDate>Sat, 07 Nov 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>This Week in GNOME: #273 Kanji &amp; Colons</title>
      <link>https://thisweek.gnome.org/posts/2026/11/twig-273/</link>
      <description>&lt;p&gt;Update on what happened across the GNOME project in the week from October 31 to November 7.&lt;/p&gt;
&lt;h2 id="gnome-fellowship"&gt;GNOME Fellowship&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/8774b72e06465b3258a9bbbc7a1aafd0c2b816e854547dd95ef05e56c1cb11f8"&gt;Philipp Sauberzweig&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;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 &lt;a href="https://blogs.gnome.org/psauberz/2026/11/06/fellowship-update-2026-11-06/"&gt;full blog post&lt;/a&gt;!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="gnome-core-apps-and-libraries"&gt;GNOME Core Apps and Libraries&lt;/h2&gt;
&lt;h3 id="gtk-"&gt;GTK &lt;a href="https://gitlab.gnome.org/GNOME/gtk"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Cross-platform widget toolkit for creating graphical user interfaces.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/7df920fab7cdd1252121773e182bce11c01f921f415b63c3c30459e074344e05"&gt;grorp&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;My first contributions to GTK were merged this week!&lt;/p&gt;
&lt;p&gt;&lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10455"&gt;The first change&lt;/a&gt; fixes a rare edge case where GTK would wrongly detect a swipe gesture and start scrolling, even though the user hadn’t actually swiped.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10376"&gt;The second merge request&lt;/a&gt; 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 :)&lt;/p&gt;
&lt;p&gt;Also, my &lt;a href="https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/5367#note_2925163"&gt;first patch for Mutter&lt;/a&gt; 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!&lt;/p&gt;
&lt;p&gt;This has actually been in the works for a long time, the awesome Carlos Garnacho worked on &lt;a href="https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/282"&gt;Wayland protocol support&lt;/a&gt; and more to make it happen. It seems there was just this small Mutter bugfix missing to get it working.&lt;/p&gt;
&lt;p&gt;These changes are motivated by the goal of eventually being able to use a Linux phone with GNOME :)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="blueprint-"&gt;Blueprint &lt;a href="https://jwestman.pages.gitlab.gnome.org/blueprint-compiler/"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;A markup language for app developers to create GTK user interfaces.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/3606de80c06ea68cc8e3d583c3de14a574d6c6b6b5635ef381999e3dc3c532b5"&gt;Peter Eisenmann&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Blueprint, the objectively best markup language for GNOME user interfaces, got even better this week.
Semicolons after &lt;code&gt;{}&lt;/code&gt; and &lt;code&gt;[]&lt;/code&gt; blocks &lt;a href="https://gitlab.gnome.org/GNOME/blueprint-compiler/-/merge_requests/328"&gt;are now optional&lt;/a&gt;! 🎆
This allows to change indentions of nested code without having to worry about placing semicolons in all the exactly right places.&lt;/p&gt;
&lt;p&gt;If you are using Blueprint as a subproject, you can already use this by updating to the latest commit.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="third-party-projects"&gt;Third Party Projects&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/87ef4a1980fb4e9b8acdd43a22f8af5a56fcd03abe3fbaaaf0f56fc099636a90"&gt;Haydn Trowell&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Available on Flathub: &lt;a href="https://flathub.org/apps/net.trowell.kotoba"&gt;https://flathub.org/apps/net.trowell.kotoba&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;&lt;img height="770" src="https://thisweek.gnome.org/_astro/TDhUIDWEkVqRAgnxktRGuUFt_light-kanji-composer.HEoNWtej_1bzUVD.webp" width="1010"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;video controls="controls"&gt;&lt;source src="https://thisweek.gnome.org/posts/2026/11/twig-273/iQpxkgJYNzIUpSfIkKQMfknF_kotoba_kanji-composer.webm" type="video/webm"/&gt;&lt;/video&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/65e32ad306958fae73f6a8e9aefb6a43ae58ea5d70b79d274425529fede25a47"&gt;dabrain34&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;🎉 New Release Announcement: GstPipelineStudio v0.7.3 🎉&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;What’s new in 0.7.3:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Drag elements, favorites and pipelines from the lists onto the graph&lt;/li&gt;
&lt;li&gt;Terminal tab in the bottom panel, toggled from View → Terminal (Linux and macOS)&lt;/li&gt;
&lt;li&gt;GPS tells you in the window title when a newer release is available, in the AppImage and the Windows and macOS builds&lt;/li&gt;
&lt;li&gt;Main window built on libadwaita&lt;/li&gt;
&lt;li&gt;Finnish translation; Italian, French, Portuguese, German and Spanish translations completed&lt;/li&gt;
&lt;li&gt;Space and s no longer steal keys from a focused text field&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Highlights of the 0.7.x series:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New application icon&lt;/li&gt;
&lt;li&gt;Nodes colored by type: source, transform, sink&lt;/li&gt;
&lt;li&gt;Swap a node for an alternative element from its context menu&lt;/li&gt;
&lt;li&gt;Tags tab listing tags from bus messages&lt;/li&gt;
&lt;li&gt;Sortable columns in the element and pipeline lists&lt;/li&gt;
&lt;li&gt;Suggestions reuse a compatible free element already in the graph&lt;/li&gt;
&lt;li&gt;Space bar toggles play/pause, s stops the pipeline&lt;/li&gt;
&lt;li&gt;Explicit properties are kept when importing a pipeline&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Participants:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Stéphane Cerveau — maintainer and main contributor&lt;/li&gt;
&lt;li&gt;Translations contributed through &lt;a href="https://hosted.weblate.org/projects/gstpipelinestudio/"&gt;Weblate&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;🚀 Upgrade Now!&lt;/p&gt;
&lt;p&gt;To get the latest version of GstPipelineStudio, visit the project’s &lt;a href="https://gps.mooday.dev/"&gt;page&lt;/a&gt; and check out the &lt;a href="https://gitlab.freedesktop.org/dabrain34/GstPipelineStudio/-/blob/main/ChangeLog.md"&gt;Changelog&lt;/a&gt; for more details.&lt;/p&gt;
&lt;p&gt;Happy streaming! 🎬📡
&lt;/p&gt;
&lt;p&gt;&lt;img height="1370" src="https://thisweek.gnome.org/_astro/TTqhZVJIPawkjjqBTCfiXPOd_gps_screenshot.DTkjNm6X_Z2d5AKy.webp" width="2560"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/579a4f3527aa9f46798ea4476441fef008f4a13ffad33b4822bae5de56028aa7"&gt;JumpLink&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href="https://jumplink.eu/Learn6502/en/"&gt;Learn 6502&lt;/a&gt; 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 🤖.&lt;/p&gt;
&lt;p&gt;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 &lt;a href="https://gjsify.org/gjsify/projects/node-gi/"&gt;@gjsify/node-gi&lt;/a&gt;, which provides &lt;code&gt;gi://&lt;/code&gt; imports that behave like GJS, plus a bundled GTK. On Android it runs in &lt;a href="https://nativescript.org/"&gt;NativeScript&lt;/a&gt;, where &lt;a href="https://gjsify.org/gjsify/adwaita/"&gt;@gjsify/adwaita-nativescript&lt;/a&gt; turns the same Blueprint files into native Android views styled like libadwaita.&lt;/p&gt;
&lt;p&gt;All of this comes from &lt;a href="https://gjsify.org/gjsify/"&gt;gjsify&lt;/a&gt;, 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 &lt;a href="https://gjsify.org/gjsify/projects/napi/"&gt;Node-API implementation&lt;/a&gt;. The gjsify toolchain itself runs on GJS, so Node.js is an option, not a dependency.&lt;/p&gt;
&lt;p&gt;How it works, and how AI fits into a project I started long before AI tools existed, is &lt;a href="https://jumplink.eu/en/blog/learn6502-everywhere/"&gt;on my blog&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Get it on &lt;a href="https://flathub.org/apps/eu.jumplink.Learn6502"&gt;Flathub&lt;/a&gt; or download the app for Linux, Windows, macOS and Android from the &lt;a href="https://jumplink.eu/Learn6502/en/"&gt;app page&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;&lt;img height="1205" src="https://thisweek.gnome.org/_astro/TzOknfEZYcbFVoWTfqWnmYcB_learn6502-everywhere-phones.CyZnPT46_ZvPu73.webp" width="1600"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/3fea16b34cb6c968b69cfb9aac18b7adac7f0ffd00132ff10c3e4104b63cf1e5"&gt;Barın Güzeldemirci&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;word-sys PDF Editor v1.12.0 (“Sign &amp;amp; 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.&lt;/p&gt;
&lt;p&gt;You can install word-sys PDF Editor from &lt;a href="https://flathub.org/apps/io.github.word_sys.word-sys-pdf-editor"&gt;Flathub&lt;/a&gt; or check out the release on &lt;a href="https://github.com/word-sys/word-sys-pdf-editor/releases/tag/v1.12.0"&gt;GitHub&lt;/a&gt;.

&lt;/p&gt;
&lt;p&gt;&lt;img height="827" src="https://thisweek.gnome.org/_astro/VWICninLPosNzsRIvKDOqpkc_screenshot1.BhdmqvjY_1uTs3e.webp" width="1209"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="811" src="https://thisweek.gnome.org/_astro/bDmgFsXlBjNSzclDCCqOHoyD_screenshot2.CXUx00sB_Z1NG5LE.webp" width="1209"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="shell-extensions"&gt;Shell Extensions&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/4b1938a3e242579fc2efda24b0afde17a686442c3f036fd86b3e7710a9f664d6"&gt;J G&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Accent Hold brings macOS-style press and hold to GNOME.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Many thanks to Manuele Conti for the discussions that shaped the press-and-hold design.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://extensions.gnome.org/extension/10265/accent-hold/"&gt;https://extensions.gnome.org/extension/10265/accent-hold/&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="miscellaneous"&gt;Miscellaneous&lt;/h2&gt;
&lt;h3 id="gnome-os-"&gt;GNOME OS &lt;a href="https://os.gnome.org"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;The GNOME operating system, development and testing platform&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/1cbcc511e6ca919ad647ad976ae4438db064eda941fbb2882a21d6e13044d34a"&gt;Bilal Elmoussaoui&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;oo7 0.7 is out! 🎉&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;Release notes: &lt;a href="https://github.com/linux-credentials/oo7/releases/tag/0.7.0"&gt;https://github.com/linux-credentials/oo7/releases/tag/0.7.0&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="events"&gt;Events&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/019ea3db22880010eab4ce387396c7fa3083f6a22caae6806ba58fa90fffbb7a"&gt;Guillaume Bernard&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;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…).&lt;/p&gt;
&lt;p&gt;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!&lt;/p&gt;
&lt;p&gt;To anyone interested, I will have GNOME t-shirts to sell to support the Foundation, supporting Foundation employees, contractors, and the Foundation’s missions!&lt;/p&gt;
&lt;p&gt;Take a look at: &lt;a href="https://capitoledulibre.org/"&gt;https://capitoledulibre.org/&lt;/a&gt; (in French)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="thats-all-for-this-week"&gt;That’s all for this week!&lt;/h2&gt;
&lt;p&gt;See you next week, and be sure to stop by &lt;a href="https://matrix.to/#/#thisweek:gnome.org"&gt;#thisweek:gnome.org&lt;/a&gt; with updates on your own projects!&lt;/p&gt;</description>
      <guid isPermaLink="false">https://thisweek.gnome.org/posts/2026/11/twig-273/</guid>
      <pubDate>Sat, 07 Nov 2026 08:30:12 +0000</pubDate>
    </item>
    <item>
      <title>Luis Villa: How San Francisco's Republican voters voted on November 3, 2026</title>
      <link>https://lu.is/2026/11/sf-gop-voters/</link>
      <description>&lt;p&gt;&lt;img alt="A San Francisco polling place set up in a residential garage: a row of voting booths on metal legs, a ballot-scanning machine in the foreground, and a table of voter rosters beside a red supply box, with storage boxes on shelves and in the rafters" src="https://lu.is/images/sf-garage-polling-place.jpg"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;“&lt;a href="https://www.flickr.com/photos/44094498@N03/4054545059"&gt;Voting in a Garage&lt;/a&gt;” by &lt;a href="https://www.flickr.com/photos/44094498@N03"&gt;coolmikeol&lt;/a&gt;, &lt;a href="https://creativecommons.org/licenses/by/2.0/"&gt;CC BY 2.0&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A few of us on Bluesky &lt;a href="https://bsky.app/profile/mattlaroche.com/post/3mzvk3kfays24"&gt;have been discussing what SF’s November 3 election results mean&lt;/a&gt;.
I have thoughts and speculations about what this means, so I dug in. One easy, accurate thing I saw and could share: what GOP voters in San Francisco voted for.&lt;/p&gt;
&lt;h2 id="who-are-we-talking-about-here"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#who-are-we-talking-about-here" tabindex="-1"&gt;#&lt;/a&gt;Who are we talking about here?&lt;/h2&gt;
&lt;p&gt;Six statewide races featured a Republican against a Democrat. 10% of SF’s mail ballots (details
&lt;a href="https://lu.is/rss.xml#how-this-was-measured"&gt;below&lt;/a&gt;) 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.&lt;/p&gt;
&lt;h2 id="what-am-i-not-claiming"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#what-am-i-not-claiming" tabindex="-1"&gt;#&lt;/a&gt;What am I not claiming?&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2 id="the-tables"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#the-tables" tabindex="-1"&gt;#&lt;/a&gt;The tables&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;SF GOP voters&lt;/strong&gt; = the 27,144 mail voters who meet the 5-of-6 test. &lt;strong&gt;Everyone else&lt;/strong&gt; = 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. &lt;strong&gt;Gap&lt;/strong&gt; = 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.&lt;/p&gt;
&lt;h3 id="where-gop-voters-and-everyone-else-disagreed-22-items"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#where-gop-voters-and-everyone-else-disagreed-22-items" tabindex="-1"&gt;#&lt;/a&gt;Where GOP voters and everyone else disagreed (22 items)&lt;/h3&gt;
&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Item&lt;/th&gt;&lt;th&gt;SF GOP voters&lt;/th&gt;&lt;th&gt;Everyone else&lt;/th&gt;&lt;th align="right"&gt;Gap (points)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-39"&gt;Prop 39, voter ID&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 89%&lt;/td&gt;&lt;td&gt;Oppose 89%&lt;/td&gt;&lt;td align="right"&gt;78&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-3"&gt;Prop 3, permanent top tax rates&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 85%&lt;/td&gt;&lt;td&gt;Support 84%&lt;/td&gt;&lt;td align="right"&gt;68&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-1"&gt;Prop 1, housing bond&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 78%&lt;/td&gt;&lt;td&gt;Support 86%&lt;/td&gt;&lt;td align="right"&gt;64&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-2"&gt;Prop 2, rainy-day fund&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 76%&lt;/td&gt;&lt;td&gt;Support 87%&lt;/td&gt;&lt;td align="right"&gt;63&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-h"&gt;SF H, Muni parcel tax&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 81%&lt;/td&gt;&lt;td&gt;Support 81%&lt;/td&gt;&lt;td align="right"&gt;62&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-j"&gt;SF J, close foreclosure tax exemption&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 73%&lt;/td&gt;&lt;td&gt;Support 88%&lt;/td&gt;&lt;td align="right"&gt;61&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-41"&gt;Prop 41, audit special taxes&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 86%&lt;/td&gt;&lt;td&gt;Oppose 71%&lt;/td&gt;&lt;td align="right"&gt;58&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-42"&gt;Prop 42, ban wealth taxes&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 89%&lt;/td&gt;&lt;td&gt;Oppose 68%&lt;/td&gt;&lt;td align="right"&gt;58&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-c"&gt;SF C, affordable housing fund&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 69%&lt;/td&gt;&lt;td&gt;Support 88%&lt;/td&gt;&lt;td align="right"&gt;57&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-rtm"&gt;RTM, regional transit sales tax&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 72%&lt;/td&gt;&lt;td&gt;Support 85%&lt;/td&gt;&lt;td align="right"&gt;56&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-43"&gt;Prop 43, 2/3 vote for local taxes&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 83%&lt;/td&gt;&lt;td&gt;Oppose 70%&lt;/td&gt;&lt;td align="right"&gt;53&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-5"&gt;Prop 5, recall process&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 72%&lt;/td&gt;&lt;td&gt;Support 77%&lt;/td&gt;&lt;td align="right"&gt;49&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-40"&gt;Prop 40, billionaire tax&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 87%&lt;/td&gt;&lt;td&gt;Support 60%&lt;/td&gt;&lt;td align="right"&gt;47&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-4"&gt;Prop 4, public campaign financing&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 87%&lt;/td&gt;&lt;td&gt;Support 59%&lt;/td&gt;&lt;td align="right"&gt;46&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-37"&gt;Prop 37, home-purchase bond&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 68%&lt;/td&gt;&lt;td&gt;Support 77%&lt;/td&gt;&lt;td align="right"&gt;46&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-g"&gt;SF G, reopen Great Highway to cars&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 75%&lt;/td&gt;&lt;td&gt;Oppose 70%&lt;/td&gt;&lt;td align="right"&gt;45&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-b"&gt;SF B, public bank&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 85%&lt;/td&gt;&lt;td&gt;Support 56%&lt;/td&gt;&lt;td align="right"&gt;41&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-45"&gt;Prop 45, CEQA fast-track&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 75%&lt;/td&gt;&lt;td&gt;Oppose 64%&lt;/td&gt;&lt;td align="right"&gt;39&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-i"&gt;SF I, transfer tax to housing&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 86%&lt;/td&gt;&lt;td&gt;Support 51%&lt;/td&gt;&lt;td align="right"&gt;37&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/insurance-commissioner"&gt;Insurance Commissioner&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Allen 65%&lt;/td&gt;&lt;td&gt;Kim 55%&lt;/td&gt;&lt;td align="right"&gt;21&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/u-s-representative-district-11"&gt;Congress, CA-11&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Chan 57%&lt;/td&gt;&lt;td&gt;Wiener 56%&lt;/td&gt;&lt;td align="right"&gt;13&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-d"&gt;SF D, raise initiative thresholds&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 51%&lt;/td&gt;&lt;td&gt;Support 56%&lt;/td&gt;&lt;td align="right"&gt;7&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id="where-gop-voters-and-everyone-else-agreed-5-items"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#where-gop-voters-and-everyone-else-agreed-5-items" tabindex="-1"&gt;#&lt;/a&gt;Where GOP voters and everyone else agreed (5 items)&lt;/h3&gt;
&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Item&lt;/th&gt;&lt;th&gt;SF GOP voters&lt;/th&gt;&lt;th&gt;Everyone else&lt;/th&gt;&lt;th align="right"&gt;Gap (points)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-e"&gt;SF E, City Administrator powers&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 62%&lt;/td&gt;&lt;td&gt;Support 65%&lt;/td&gt;&lt;td align="right"&gt;3&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-38"&gt;Prop 38, immunology research bond&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 65%&lt;/td&gt;&lt;td&gt;Oppose 62%&lt;/td&gt;&lt;td align="right"&gt;3&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-a"&gt;SF A, cut charter commissions&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 74%&lt;/td&gt;&lt;td&gt;Support 69%&lt;/td&gt;&lt;td align="right"&gt;5&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-f"&gt;SF F, mayor’s control of departments&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Support 72%&lt;/td&gt;&lt;td&gt;Support 59%&lt;/td&gt;&lt;td align="right"&gt;13&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href="https://www.openballot.app/elections/california-general-election-2026/ballot-items/proposition-44"&gt;Prop 44, clinic spending rule&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Oppose 72%&lt;/td&gt;&lt;td&gt;Oppose 87%&lt;/td&gt;&lt;td align="right"&gt;15&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2 id="how-this-was-measured"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#how-this-was-measured" tabindex="-1"&gt;#&lt;/a&gt;How this was measured&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;All analysis code was written by Claude Code (mix of Opus and Fable), with an adversarial audit by GLM-5.3.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Limitations:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mail ballots only.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The House race had no Republican.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Regrouping can make mistakes.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Small numbers redacted.&lt;/strong&gt; The Department withheld the votes on 24 cards (6 ballots) in very
small batches. I left them out.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="sources"&gt;&lt;a class="anchor-link" href="https://lu.is/rss.xml#sources" tabindex="-1"&gt;#&lt;/a&gt;Sources&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Cast vote record and results: San Francisco Department of Elections,
&lt;a href="https://www.sfelections.org/results/20261103w/index.html"&gt;November 3, 2026 results&lt;/a&gt;. The cast
vote record used here is the
&lt;a href="https://www.sfelections.org/results/20261103/data/20261108/CVR_Export_20261108134505.zip"&gt;November 8, 2026 release&lt;/a&gt;
(a 270 MB zip file).&lt;/li&gt;
&lt;/ul&gt;</description>
      <guid isPermaLink="false">https://lu.is/2026/11/sf-gop-voters/</guid>
      <pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Peter Eisenmann: Fellowship Report October 2026 (Lothlórien)</title>
      <link>https://blogs.gnome.org/p3732/fellowship-report-october-2026-lothlorien/</link>
      <description>&lt;p&gt;Spooky season is over, let’s see what scary changes I made last month &lt;img alt="🎃" class="wp-smiley" src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f383.png" style="height: 1em;"/&gt;&lt;/p&gt;
&lt;h2 class="wp-block-heading"&gt;Nautilus&lt;/h2&gt;
&lt;p&gt;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 &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4284"&gt;the default was changed&lt;/a&gt; 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 &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2164"&gt;dropped considering GTK3 settings&lt;/a&gt;, meaning fresh setups will finally see folders sorted before files by default &lt;img alt="🎉" class="wp-smiley" src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f389.png" style="height: 1em;"/&gt;&lt;/p&gt;
&lt;p&gt;Related to folder sorting, I was very excited to see Christian Hergert added &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10401"&gt;sections to GtkGridView&lt;/a&gt; in GTK. I long thought that sections would be very useful to have, as it allows to show folders and files separate. I &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2163"&gt;played around with them&lt;/a&gt; a bit, but still need to rework it before other maintainers are happy with it.&lt;/p&gt;
&lt;p&gt;&lt;img alt="" class="aligncenter size-full wp-image-238" height="758" src="https://blogs.gnome.org/p3732/files/2026/11/sections.png" width="591"/&gt;&lt;/p&gt;
&lt;p&gt;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 &lt;code&gt;&lt;span class="nf"&gt;AdwComboRow&lt;/span&gt;&lt;/code&gt; for the “Action to Open Items” doesn’t scale well to smaller sizes. After some feedback from Philipp Sauberzweig it now uses the new &lt;a class="external" href="https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/property.ActionRow.body.html"&gt;&lt;code&gt;&lt;span class="nf"&gt;AdwActionRow:body&lt;/span&gt;&lt;/code&gt; property&lt;/a&gt;. Philipp also suggested more adjustments for the performance section combo rows, making the dialog now look this &lt;img alt="🌟" class="wp-smiley" src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f31f.png" style="height: 1em;"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt="image" class="gfm js-lazy-loaded aligncenter" height="600" src="https://gitlab.gnome.org/-/project/1/uploads/1a0796a5970ab0c852c8f1a7bd7960a5/image.png" width="416"/&gt;&lt;/p&gt;
&lt;p&gt;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 &lt;img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" style="height: 1em;"/&gt;&lt;/p&gt;
&lt;p&gt;Other things&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Expanded nautilus CI with &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2149"&gt;Blueprint and meson formatting&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Assured &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2150"&gt;property dialogs are sized correctly&lt;/a&gt;&lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2150"&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Suggested to add Ctrl+Shift+L as a &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2155"&gt;shortcut to open the search filter&lt;/a&gt; popover&lt;/li&gt;
&lt;li&gt;Suggested to add Ctrl+Shift+R as an &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2168"&gt;alternative renaming shortcut&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fixed selection when &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2170"&gt;deleting the last item&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Together with Khalid Abu Shawarib &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2157"&gt;fixed scaling of thumbnails&lt;/a&gt; in the nightly version&lt;/li&gt;
&lt;li&gt;Some &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2156"&gt;CI fixes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Various cleanups regarding &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2208"&gt;includes&lt;/a&gt;, &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2202"&gt;gobject-linter&lt;/a&gt; and &lt;a class="external" href="https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/2167"&gt;more&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;!-- /wp:post-content --&gt;
&lt;!-- wp:heading --&gt;
&lt;h2 class="wp-block-heading"&gt;Sushi&lt;/h2&gt;
&lt;p&gt;During writing last month’s blog post I noticed and &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/178"&gt;fixed some graphical inconsistencies&lt;/a&gt; in the icon. I also made sure we only offer to copy error messages &lt;a class="external" href="https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/179"&gt;when we actually have any&lt;/a&gt;. Apart from that and a bug fix release, I mostly reviewed MRs from Tau Gärtli and Corey Berla.&lt;/p&gt;
&lt;p&gt;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 &lt;img alt="🌈" class="wp-smiley" src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f308.png" style="height: 1em;"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" class="wp-image-233 size-medium aligncenter" height="600" src="https://blogs.gnome.org/p3732/files/2026/11/rainbow-smiley-451x600.png" width="451"/&gt;&lt;/p&gt;
&lt;!-- /wp:heading --&gt;
&lt;!-- wp:paragraph --&gt;
&lt;figure class="wp-block-gallery has-nested-images columns-default is-cropped"&gt;
&lt;h2 class="wp-block-heading"&gt;libadwaita&lt;/h2&gt;
&lt;p&gt;I have once again stumbled upon issues with dialog sizing. Basically, what I expect dialogs to scale with their content. No problem, &lt;em&gt;AdwDialog:follows-content-size&lt;/em&gt; 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.&lt;/p&gt;
&lt;p&gt;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 &lt;em&gt;follows-content-size&lt;/em&gt; the dialog might often end up small, even in situations where that doesn’t really look all that great.&lt;/p&gt;
&lt;p&gt;What I implented as &lt;a class="external" href="https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/1843"&gt;a suggested workaround&lt;/a&gt; is to always strive for allocating at least the dialog’s &lt;em&gt;content-width&lt;/em&gt; and &lt;em&gt;content-height&lt;/em&gt;, even when &lt;em&gt;follows-content-size&lt;/em&gt; is set. If the dialog’s content grows beyond those dimensions, then it is still resized accordingly.&lt;/p&gt;
&lt;p&gt;&lt;img alt="" class="size-full wp-image-241 aligncenter" height="500" src="https://blogs.gnome.org/p3732/files/2026/11/dialog-follows-content-size.png" width="764"/&gt;&lt;/p&gt;
&lt;/figure&gt;
&lt;figure class="wp-block-gallery has-nested-images columns-default is-cropped"&gt;
&lt;h2&gt;Other&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;I fixed up a GTK MR from the previous month that adds &lt;code&gt;&lt;span class="nf"&gt;gdk_keyval_is_alias&lt;/span&gt;&lt;/code&gt;, a check that builds on the mechanism of the recently introduced &lt;code&gt;&lt;span class="nf"&gt;gdk_keyval_get_aliases&lt;/span&gt;&lt;/code&gt; which allows to &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10357"&gt;check for keyval alternatives&lt;/a&gt; (merged), e.g. to cover alternative numpad keys&lt;/li&gt;
&lt;li&gt;Fixed &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10357"&gt;a GVariant leak&lt;/a&gt; that caused one of the many CI pipeline failures this month&lt;/li&gt;
&lt;li&gt;I made &lt;em&gt;gobject-linter&lt;/em&gt; correctly &lt;a class="external" href="https://github.com/bilelmoussaoui/gobject-linter/pull/202"&gt;handle functions declared as &lt;code&gt;external&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;I fixed the &lt;em&gt;gexiv2 &lt;/em&gt;CI pipeline while &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gexiv2/-/merge_requests/103"&gt;changing the default branch name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Fixed &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/64"&gt;some leaks&lt;/a&gt; in gnome-autoar and made the &lt;a class="external" href="https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/65"&gt;CI GNOME OS-based&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Roadmap&lt;/h2&gt;
&lt;p&gt;&lt;img alt="" class="aligncenter size-full wp-image-194" height="275" src="https://blogs.gnome.org/p3732/files/2026/10/0926-chart.png" width="999"/&gt;&lt;/p&gt;
&lt;h2&gt;Support the GNOME Project&lt;/h2&gt;
&lt;p&gt;&lt;a class="external" href="https://donate.gnome.org/"&gt;&lt;img alt="GNOME Donation graphic" class="aligncenter size-full wp-image-66" height="712" src="https://blogs.gnome.org/p3732/files/2026/08/donate-card.png" width="1067"/&gt;&lt;/a&gt; The GNOME Fellowships are funded by our community. If you would like to help the GNOME project to stay sustainable, please &lt;a class="external" href="https://donate.gnome.org/"&gt;consider donating&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;span style="color: #fff0;"&gt;AI Summary&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="color: #fff0;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="color: #fff0;"&gt;Important note: All statements in this blog are fictional.&lt;img alt="" class="aligncenter size-full wp-image-229" height="500" src="https://blogs.gnome.org/p3732/files/2026/11/lothlorien-footer.png" width="1000"/&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/figure&gt;</description>
      <guid isPermaLink="false">https://blogs.gnome.org/p3732/fellowship-report-october-2026-lothlorien/</guid>
      <pubDate>Mon, 09 Nov 2026 23:21:08 +0000</pubDate>
    </item>
    <item>
      <title>Justin Wheeler: Copr, explained: the sandbox where Fedora packaging starts</title>
      <link>https://jwheel.org/blog/2026/11/fedora-copr-intro/</link>
      <description>&lt;img alt="Copr, explained: the sandbox where Fedora packaging starts" src="https://jwheel.org/blog/2026/11/fedora-copr-intro.jpg"/&gt;&lt;div class="paragraph"&gt;
&lt;p&gt;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.
&lt;strong&gt;Fedora Copr&lt;/strong&gt; made that first attempt far less stressful.
I wrote up that first package at the time: &lt;a href="https://jwheel.org/blog/2017/11/first-rpm-package-fedora/"&gt;&lt;em&gt;How I created my first RPM package in Fedora&lt;/em&gt;&lt;/a&gt;.
Copr remains one of the most useful tools in the Fedora contribution ecosystem.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="what"&gt;What Copr is &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#what"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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 &lt;a href="https://jwheel.org/tags/fedora-infrastructure"&gt;Fedora infrastructure&lt;/a&gt;.
You can use the public instance at &lt;a href="https://copr.fedorainfracloud.org"&gt;copr.fedorainfracloud.org&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;If you use Arch Linux, Copr is the closest parallel to the &lt;a href="https://wiki.archlinux.org/title/Arch_User_Repository"&gt;Arch User Repository (AUR)&lt;/a&gt;.
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.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="sect2"&gt;
&lt;h3 id="why"&gt;Why packagers use Copr &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#why"&gt;🔗&lt;/a&gt;&lt;/h3&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect2"&gt;
&lt;h3 id="enablement"&gt;Copr as an instant enablement path &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#enablement"&gt;🔗&lt;/a&gt;&lt;/h3&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Recently, I used Copr to package something new I was working on.
I packaged a set of Markdown files, each one an &lt;a href="https://agentskills.io/specification"&gt;Agent Skill&lt;/a&gt;, from the &lt;a href="https://forge.fedoraproject.org/ai-ml/skills-library"&gt;Fedora Agent Skills Library&lt;/a&gt; into a single RPM.
I published it in the &lt;a href="https://copr.fedorainfracloud.org/coprs/g/ai-ml/agent-skills/"&gt;AI/ML SIG Copr project&lt;/a&gt; and started sharing it for testing and use.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;My plan is to package &lt;code&gt;agent-skills&lt;/code&gt; 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.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="sandbox"&gt;Copr as a sandbox &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#sandbox"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Copr works well as a sandbox.
Several design choices make that true.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="ulist"&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Projects are separate&lt;/strong&gt;.
Packages in your Copr project do not enter Fedora’s official repositories.
Your experiments stay in your own repository.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Packaging rules are relaxed&lt;/strong&gt;.
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.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Projects can expire&lt;/strong&gt;.
You can set a project to delete itself after a number of days.
This suits short tests and one-off experiments.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Old builds are removed&lt;/strong&gt;.
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.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="innovation-lifecycle"&gt;Where Copr fits in the innovation discussion &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#innovation-lifecycle"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Fedora is discussing a &lt;a href="https://discussion.fedoraproject.org/t/draft-council-proposal-for-the-fedora-innovation-lifecycle/190996"&gt;Council proposal for an Innovation Lifecycle&lt;/a&gt;.
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.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="sect2"&gt;
&lt;h3 id="packaging-fallback"&gt;Packaging as a fallback &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#packaging-fallback"&gt;🔗&lt;/a&gt;&lt;/h3&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="getting-started"&gt;Getting started &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#getting-started"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;You need a FAS account, a project, and an SRPM or RPM spec.
These commands create a project for Fedora Rawhide and submit a build:&lt;/p&gt;
&lt;/div&gt;
&lt;div class="listingblock"&gt;
&lt;div class="content"&gt;
&lt;pre class="highlight"&gt;&lt;code class="language-bash"&gt;copr-cli create --chroot fedora-rawhide-x86_64 my-first-project
copr-cli build my-first-project ./my-package.spec&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;For more detail, read the &lt;a href="https://docs.copr.fedorainfracloud.org/user_documentation.html"&gt;Copr user documentation&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="sect1"&gt;
&lt;h2 id="final-thoughts"&gt;Final thoughts &lt;a class="hanchor" href="https://jwheel.org/rss/tags/fedora-planet/#final-thoughts"&gt;🔗&lt;/a&gt;&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;/div&gt;
&lt;hr/&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;&lt;em&gt;Featured image generated by LLM-gen-AI using the OpenAI image API&lt;/em&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;</description>
      <guid isPermaLink="false">https://jwheel.org/blog/2026/11/fedora-copr-intro/</guid>
      <pubDate>Tue, 10 Nov 2026 08:00:00 +0000</pubDate>
    </item>
    <item>
      <title>This Week in GNOME: #274 Fancy Statistics</title>
      <link>https://thisweek.gnome.org/posts/2026/11/twig-274/</link>
      <description>&lt;p&gt;Update on what happened across the GNOME project in the week from November 6 to November 13.&lt;/p&gt;
&lt;h2 id="gnome-fellowship"&gt;GNOME Fellowship&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/3606de80c06ea68cc8e3d583c3de14a574d6c6b6b5635ef381999e3dc3c532b5"&gt;Peter Eisenmann&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I wrote about the 🧟spooky👻 stuff I got up to as a GNOME fellow in October, read about it here 🎃 &lt;a href="https://blogs.gnome.org/p3732/fellowship-report-october-2026-lothlorien/"&gt;https://blogs.gnome.org/p3732/fellowship-report-october-2026-lothlorien/&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="gnome-core-apps-and-libraries"&gt;GNOME Core Apps and Libraries&lt;/h2&gt;
&lt;h3 id="gtk-"&gt;GTK &lt;a href="https://gitlab.gnome.org/GNOME/gtk"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Cross-platform widget toolkit for creating graphical user interfaces.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/367605ee3f1609c560f4c630be71e4f6e5769036f91a37e2abd06c3fafa30ac0"&gt;Felix&lt;/a&gt; says&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I’ve been working on some more GTK macOS fixes, which were merged this week!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;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. (&lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10667"&gt;!10667&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;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. (&lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10640"&gt;!10640&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Mouse back/forward buttons now work as expected. For example, pressing the back button in an app that uses &lt;code&gt;AdwNavigationView&lt;/code&gt; now goes back, just like it does on Linux. (&lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10625"&gt;!10625&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;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 &lt;code&gt;AdwNavigationView&lt;/code&gt; now also works on macOS. (&lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10617"&gt;!10617&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;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. (&lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10615"&gt;!10615&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Finally, I fixed a bug that caused some tooltips to be clipped. (&lt;a href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10614"&gt;!10614&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;h2 id="gnome-circle-apps-and-libraries"&gt;GNOME Circle Apps and Libraries&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/3f7e56fd3e07a5d293b680946eb734c590035ba39d4a7db7ddfc048c9d97aad6"&gt;Alexander Vanhee&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.



&lt;/p&gt;
&lt;p&gt;&lt;img height="1496" src="https://thisweek.gnome.org/_astro/kYRzBNpeVojQnNgQUkLQTiJN_bazaar-managment.2WSSBq6X_7r4zQ.webp" width="1730"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="1496" src="https://thisweek.gnome.org/_astro/ByzLoexNLYbpZeGHVOMqTZmN_bazaar-remove.IC_w18eJ_Z1TbCWf.webp" width="1730"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="1512" src="https://thisweek.gnome.org/_astro/rEeddiQhJcsnanHSzwRAQmmR_bazaar-graph.BVQV5Hso_198JNF.webp" width="1700"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="1512" src="https://thisweek.gnome.org/_astro/AKjIBFhFpDdeMCeRrITyQGPp_bazaar-distro.B5rTVFwK_2u9K1n.webp" width="1700"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="third-party-projects"&gt;Third Party Projects&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/cea48a5c74968b1345238e976852c785b64960eb4af0ad3d3c70cdb26df93ae7"&gt;Charalampos Kardaris&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href="https://flathub.org/en/apps/com.ckardaris.Klisi"&gt;Klisi&lt;/a&gt; is a callgrind profile viewer designed to fit nicely into the GNOME desktop.&lt;/p&gt;
&lt;p&gt;It is an alternative to &lt;a href="https://flathub.org/en/apps/org.kde.kcachegrind"&gt;KCachegrind&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;A &lt;a href="https://valgrind.org/docs/manual/cl-format.html"&gt;callgrind profile&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;What’s more, it is not a typical GTK4/Adwaita application.
It is written in Clojure using the excellent &lt;a href="https://java-gi.org/"&gt;java-gi&lt;/a&gt; bindings.&lt;/p&gt;
&lt;p&gt;You can read more about the why and how in a &lt;a href="https://ckardaris.com/blog/2026/08/15/klisi.html"&gt;blog post&lt;/a&gt; of mine from three months ago, written after the first release.&lt;/p&gt;
&lt;p&gt;I hope you find this useful and I am looking forward to your feedback.&lt;/p&gt;
&lt;p&gt;&lt;img height="2880" src="https://thisweek.gnome.org/_astro/main-view.CdG-j7UV_Z815yT.webp" width="5174"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;video controls="controls"&gt;&lt;source src="https://thisweek.gnome.org/posts/2026/11/twig-274/com.ckardaris.Klisi-video.mp4" type="video/mp4"/&gt;&lt;/video&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/bb8601901ccceaf74d979b8ad9c9cbbe56c953203ed092c29f27930258541c85"&gt;seja-arctic-fox&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Last week, I released a new version of &lt;a href="https://github.com/seja-arctic-fox/vidcom"&gt;VidCom&lt;/a&gt;, a video archival utility. The new version is nothing big, but brings some nice improvements to the user experience.&lt;/p&gt;
&lt;p&gt;Changes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Better window sizing and side-panel collapsing&lt;/li&gt;
&lt;li&gt;Various UI changes&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;Bug fixes adressing app stability, threading, encoding and GUI&lt;/li&gt;
&lt;li&gt;Fixes for AVC codec options, radio buttons and opening of output folders&lt;/li&gt;
&lt;li&gt;Added confirmation dialog for overwriting existing files (both GUI and CLI) and an option to always overwrite files on conflict&lt;/li&gt;
&lt;li&gt;VidCom now works on Windows as well&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;VidCom can be installed via &lt;a href="https://flathub.org/en/apps/io.github.seja_arctic_fox.vidcom"&gt;Flathub&lt;/a&gt; or AUR
&lt;/p&gt;
&lt;p&gt;&lt;img height="650" src="https://thisweek.gnome.org/_astro/EBDiDtYguvbeOOihJRMKbBdm_gallery3.DyrhZkGq_Zp5zvf.webp" width="1050"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/a31cc424ff392bd6e061341756d1fbd7e6796296147aa403cc26c083e11af39d"&gt;moosee&lt;/a&gt; reports&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I have two updates to share for &lt;a href="https://moooossee.github.io/"&gt;Moose&lt;/a&gt;, a GTK and libadwaita app for chatting with local AI models through Ollama or connecting to cloud services!&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/moooossee/moose/releases/tag/v0.8.0"&gt;Version 0.8.0&lt;/a&gt; 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!&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/moooossee/moose/releases/tag/v0.8.5"&gt;Version 0.8.5&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;You can try Moose on &lt;a href="https://flathub.org/apps/io.github.moooossee.Moose"&gt;Flathub&lt;/a&gt; and find the code on &lt;a href="https://github.com/moooossee/moose"&gt;GitHub&lt;/a&gt;. Feedback, bug reports and contributions are welcome!


&lt;/p&gt;
&lt;p&gt;&lt;img height="1266" src="https://thisweek.gnome.org/_astro/lpcMltAoMKwvqKZbXhikJPqK_1.ChBFC6-6_Z1X6pW.webp" width="1866"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="1266" src="https://thisweek.gnome.org/_astro/VVDgnsmDEWyIeiyFoAaiMKzc_3.CxK5ODl-_1aLG56.webp" width="1866"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="1266" src="https://thisweek.gnome.org/_astro/QYMivkohbtqgfbhOBKzqGdyb_2.CurMHj1b_Z1zFasS.webp" width="1866"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/55fdd2f7aeaa98465eecdd95d1f82da6cbb83f3b1f3e7060e822aec5521f61b8"&gt;Vlad Krupinski&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Errands&lt;/strong&gt; has been rewritten from &lt;strong&gt;Python&lt;/strong&gt; to &lt;strong&gt;C&lt;/strong&gt;. It was a 2-year effort and it’s finally here.
Many new features have been added, and many existing issues have been fixed.&lt;/p&gt;
&lt;p&gt;Here is the short list of changes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Much lower resources usage and memory consumption even with thousands of tasks&lt;/li&gt;
&lt;li&gt;Instant startup&lt;/li&gt;
&lt;li&gt;Reworked UI&lt;/li&gt;
&lt;li&gt;Recurrent tasks&lt;/li&gt;
&lt;li&gt;Task search and sorting&lt;/li&gt;
&lt;li&gt;Cancelled tasks&lt;/li&gt;
&lt;li&gt;Custom colors&lt;/li&gt;
&lt;li&gt;All Tasks view&lt;/li&gt;
&lt;li&gt;Reworked sync using Evolution Data Server&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Get the latest update on &lt;a href="https://flathub.org/apps/io.github.mrvladus.List"&gt;Flathub&lt;/a&gt;!

&lt;/p&gt;
&lt;p&gt;&lt;img height="750" src="https://thisweek.gnome.org/_astro/VPiqXpsYRJqAPTPYurEDVOCM_main.DNAn_bpO_Z2oqaGu.webp" width="1050"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img height="750" src="https://thisweek.gnome.org/_astro/aOnNiIZoRXwmdoetLtcSWAoV_properties.BDZMbphH_Z1jgV70.webp" width="1050"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="era-"&gt;Era &lt;a href="https://gitlab.gnome.org/TitouanReal/Era"&gt;↗&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Manage your time&lt;/p&gt;
&lt;p&gt;&lt;a href="https://thisweek.gnome.org/reporters/40f0dd7c6a66c7d4438a110671d4c5190e4fcea9d6aee2be03452c3043143873"&gt;Titouan Real&lt;/a&gt; announces&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Era 0.3.0 is out. &lt;a href="https://flathub.org/apps/org.gnome.gitlab.TitouanReal.Era"&gt;Download Era&lt;/a&gt; from Flathub now and &lt;a href="https://gitlab.gnome.org/TitouanReal/Era/-/work_items"&gt;report any bugs&lt;/a&gt; you can find.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Era is also available on &lt;a href="https://nightly.gnome.org/"&gt;GNOME Nightly&lt;/a&gt; for the latest features, bug fixes, and performance improvements.
&lt;/p&gt;
&lt;p&gt;&lt;img height="1500" src="https://thisweek.gnome.org/_astro/sWKnKyiqqtGqsFTDZXvGhaLZ_month.DSSKNBAl_Z26BJQL.webp" width="2100"/&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="thats-all-for-this-week"&gt;That’s all for this week!&lt;/h2&gt;
&lt;p&gt;See you next week, and be sure to stop by &lt;a href="https://matrix.to/#/#thisweek:gnome.org"&gt;#thisweek:gnome.org&lt;/a&gt; with updates on your own projects!&lt;/p&gt;</description>
      <guid isPermaLink="false">https://thisweek.gnome.org/posts/2026/11/twig-274/</guid>
      <pubDate>Fri, 13 Nov 2026 20:22:41 +0000</pubDate>
    </item>
    <item>
      <title>GIMP: Improved Graphical User Interface testing</title>
      <link>https://www.gimp.org/news/2026/11/16/gimp-ui-tests/</link>
      <description>&lt;p&gt;&lt;span class="caps"&gt;GIMP&lt;/span&gt; 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.&lt;/p&gt;
&lt;p&gt;To find these problems early, a new &lt;strong&gt;&lt;abbr title="Graphical User
Interface"&gt;&lt;span class="caps"&gt;GUI&lt;/span&gt;&lt;/abbr&gt; testing&lt;/strong&gt; platform was implemented. A typical &lt;span class="caps"&gt;GUI&lt;/span&gt;
test starts &lt;span class="caps"&gt;GIMP&lt;/span&gt;, clicks menus and buttons, and then checks the result.
These tests run automatically each time we merge contributor changes.&lt;/p&gt;
&lt;h3 id="why-we-need-them"&gt;Why we need them&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#why-we-need-them" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="caps"&gt;GIMP&lt;/span&gt; already has unit tests. A unit test checks one small part of the code,
for example how &lt;span class="caps"&gt;GIMP&lt;/span&gt; reads an &lt;span class="caps"&gt;XCF&lt;/span&gt; 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.&lt;/p&gt;
&lt;p&gt;Note that &lt;span class="caps"&gt;GIMP&lt;/span&gt; already had tests of &lt;span class="caps"&gt;GUI&lt;/span&gt; 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.&lt;/p&gt;
&lt;p&gt;&lt;span class="caps"&gt;UI&lt;/span&gt; tests check the program as a whole, in the same way as you use it.&lt;/p&gt;
&lt;h3 id="what-the-tests-do"&gt;What the tests do&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#what-the-tests-do" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Each test starts a real &lt;span class="caps"&gt;GIMP&lt;/span&gt; and does one small task. Then it reads the
result from &lt;span class="caps"&gt;GIMP&lt;/span&gt;. If the result is not correct, the test fails and tells us
what went wrong.&lt;/p&gt;
&lt;p&gt;We have 13 tests at this time. They check that:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span class="caps"&gt;GIMP&lt;/span&gt; starts and shows its main window.&lt;/li&gt;
&lt;li&gt;The Welcome dialog opens on the correct tab. It also stays hidden when you
  turn off “&lt;em&gt;Show on Start&lt;/em&gt;”.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File &amp;gt; New&lt;/strong&gt; makes an image with the size you set.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File &amp;gt; Export As&lt;/strong&gt; writes a correct &lt;span class="caps"&gt;PNG&lt;/span&gt; file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tools &amp;gt; Swap Colors&lt;/strong&gt; swaps the foreground and background colors.&lt;/li&gt;
&lt;li&gt;You can type a new foreground color in the &lt;strong&gt;Colors&lt;/strong&gt; dialog.&lt;/li&gt;
&lt;li&gt;You can add a layer and delete a layer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Undo&lt;/strong&gt; and &lt;strong&gt;Redo&lt;/strong&gt; work.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Zoom In&lt;/strong&gt; changes the zoom level.&lt;/li&gt;
&lt;li&gt;A click on a tool button in the toolbox selects that tool. The test then
  uses the Bucket Fill tool on the canvas.&lt;/li&gt;
&lt;li&gt;A change in &lt;strong&gt;Preferences&lt;/strong&gt; is saved when you click &lt;span class="caps"&gt;OK&lt;/span&gt;.&lt;/li&gt;
&lt;li&gt;A menu action, &lt;strong&gt;Image &amp;gt; Flatten Image&lt;/strong&gt;, does its job.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="how-they-work"&gt;How they work&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#how-they-work" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;The tests do not need a screen. Each test starts a small, hidden desktop,
runs &lt;span class="caps"&gt;GIMP&lt;/span&gt; in it, and removes it at the end. Because of this, the tests can
run on our &lt;abbr title="Continuous Integration"&gt;&lt;span class="caps"&gt;CI&lt;/span&gt;&lt;/abbr&gt; servers, where
no screen is available.&lt;/p&gt;
&lt;p&gt;To find a button or a menu, the tests do not look at the pixels on the
screen. They use the accessibility information that &lt;span class="caps"&gt;GIMP&lt;/span&gt; gives to tools
such as screen readers. This has one more good result: when we make &lt;span class="caps"&gt;GIMP&lt;/span&gt;
easier to test, we also make it easier to use with a screen reader,
hence improve the software accessibility.&lt;/p&gt;
&lt;p&gt;The tests use &lt;a href="https://gitlab.com/dogtail/dogtail"&gt;dogtail&lt;/a&gt;, a Python tool
for &lt;span class="caps"&gt;UI&lt;/span&gt; tests. To run &lt;span class="caps"&gt;GIMP&lt;/span&gt; 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.&lt;/p&gt;
&lt;p&gt;At this time, the tests run only on Linux (both X11 and Wayland) since
&lt;code&gt;dogtail&lt;/code&gt; does not support Windows or macOs.&lt;/p&gt;
&lt;p&gt;Adding even these few simple tests considerably increases confidence
that the &lt;span class="caps"&gt;GIMP&lt;/span&gt; build has worked, and also shows the test infrastructure
is working and useful.&lt;/p&gt;
&lt;h3 id="credits"&gt;Credits&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#credits" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Harsh Verma&lt;/strong&gt; wrote the &lt;span class="caps"&gt;UI&lt;/span&gt; tests and the new dogtail feature.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Jehan&lt;/strong&gt; reviewed the &lt;span class="caps"&gt;UI&lt;/span&gt; tests.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Michal Odehnal&lt;/strong&gt; reviewed the new dogtail feature.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can read the full change in
&lt;a href="https://gitlab.gnome.org/GNOME/gimp/-/merge_requests/2909"&gt;merge request !2909&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id="how-you-can-help"&gt;How you can help&lt;a class="headerlink" href="https://www.gimp.org/feeds/atom.xml#how-you-can-help" title="Permanent link"&gt;⁠&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;13 tests is a good start, but &lt;span class="caps"&gt;GIMP&lt;/span&gt; has many more dialogs and tools. If you
want to help, you can write a test for the part of &lt;span class="caps"&gt;GIMP&lt;/span&gt; that you use the most.&lt;/p&gt;
&lt;p&gt;We wrote a guide that shows how to write a new test and how to find the
cause when a test fails:
&lt;a href="https://developer.gimp.org/core/debug/ui-tests/"&gt;&lt;span class="caps"&gt;UI&lt;/span&gt; tests on developer.gimp.org&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We hope this work will help us find bugs earlier and keep &lt;span class="caps"&gt;GIMP&lt;/span&gt; working well
for everyone.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://www.gimp.org/news/2026/11/16/gimp-ui-tests/</guid>
      <pubDate>Sun, 15 Nov 2026 23:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Sam Thursfield: 16th November 2026</title>
      <link>https://samthursfield.wordpress.com/2026/11/16/16th-november-2026/</link>
      <description>&lt;p class="wp-block-paragraph"&gt;I was watching a meme-heavy video there entitled &lt;a href="https://www.youtube.com/watch?v=cM1ubk7JQ3E"&gt;“Bad Gear – BIG BRANDS have a PROBLEM!!!”&lt;/a&gt; which ended on the following insight:&lt;/p&gt;
&lt;blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"&gt;
&lt;figure class="wp-block-image size-medium"&gt;&lt;a href="https://samthursfield.wordpress.com/wp-content/uploads/2026/11/image.png"&gt;&lt;img alt="We were promised flying cars but all we got was a dystopia with cheap synths - and I'm only partly complaining" class="wp-image-3772" height="168" src="https://samthursfield.wordpress.com/wp-content/uploads/2026/11/image.png?w=300" width="300"/&gt;&lt;/a&gt;&lt;/figure&gt;
&lt;/blockquote&gt;
&lt;p class="wp-block-paragraph"&gt;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.)&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Music technology always involved proprietary platforms and locked-down devices. Macbooks everywhere. Copy protection schemes with hardware dongles (see: &lt;a href="https://gearspace.com/threads/ilok-again.1169941/"&gt;iLok&lt;/a&gt;). Copyright sting operations against small studios (see: &lt;a href="https://gearspace.com/threads/waves-anti-piracy-studio-sting-operation.158340/"&gt;Waves Audio&lt;/a&gt;. Read &lt;a href="https://web.archive.org/web/20160202001449/http://libremusicproduction.com/articles/lmp-asks-6-interview-markus-schmidt"&gt;Markus Schmidt of Calf Audio’s story&lt;/a&gt; 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. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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 &lt;a href="https://reverb.com/news/fv-1-chip-history-5-pedals"&gt;how many guitar pedals use the Spin FV-1&lt;/a&gt; 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 &lt;a href="https://www.thomann.es/akai_professional_mpc_xl.htm"&gt;costs over 2 grand&lt;/a&gt;. 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 &lt;em&gt;waaaay&lt;/em&gt; above what I’ve seen anywhere else in the tech industry… but that’s a whole other blog post).&lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;a href="https://samthursfield.wordpress.com/wp-content/uploads/2026/11/image-2.png"&gt;&lt;img alt="Akai MPC XL, a big slab with many knobs and pads" class="wp-image-3777" height="482" src="https://samthursfield.wordpress.com/wp-content/uploads/2026/11/image-2.png?w=732" width="732"/&gt;&lt;/a&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;Open, hackable devices exist but have always been pretty niche. Have you been to a gig where someone played the &lt;a href="https://monome.org/docs/norns/"&gt;Monome Norns&lt;/a&gt;? Or maybe an &lt;a href="https://critterandguitari.com/products/organelle-m"&gt;Organelle&lt;/a&gt; concert?&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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 &lt;a href="https://open.m-vave.com/"&gt;an online IDE&lt;/a&gt;, and &lt;a href="https://github.com/m-vave/fm1_open"&gt;an open SDK&lt;/a&gt;. It’s arrived at a moment when LLM coding tools are heavily subsidized by the AI bubble, and at time of writing there are &lt;em&gt;two hundred and nineteen&lt;/em&gt; alternative firmwaves available for this thing. There’s a &lt;a href="https://thefirmwarehub.com/"&gt;website hosting them all&lt;/a&gt;. 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. &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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 &lt;em&gt;7 years&lt;/em&gt;, the &lt;a href="https://korginc.github.io/logue-sdk/unit-index/"&gt;official list of plugins&lt;/a&gt; grown to about… 200 plugins, many of which are from pro plugin makers. By comparsion, the FM-1 was released &lt;em&gt;in June of this year&lt;/em&gt;, that is, not even 7 &lt;em&gt;months&lt;/em&gt; have passed yet.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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 &lt;a href="https://www.youtube.com/watch?v=4NExTWq_wvk"&gt;“Vibecoding in Plato’s Cave (AI, Music Tech, and Star Trek)”&lt;/a&gt;, which in turn links to an editorial from audionewsroom.net under &lt;a href="https://audionewsroom.net/2026/10/why-the-open-source-hardware-revolution-is-a-lie.html"&gt;“Why the open source hardware revolution is a lie”&lt;/a&gt;. 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 &lt;a href="https://samthursfield.wordpress.com/2026/01/24/ai-predictions-for-2026/"&gt;“AI predictions for 2026”&lt;/a&gt;.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;Maybe I’m in an optimistic mood, especially as we might be seeing the first signs of the AI bubble bursting, thanks to &lt;a href="https://pivot-to-ai.com/2026/11/12/jensen-huang-resigns-the-end-of-the-affairs/"&gt;Jensen Huang accidentally having sex with a Chinese spy&lt;/a&gt;, 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 &lt;em&gt;are&lt;/em&gt; 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 &lt;em&gt;&lt;a href="https://samthursfield.wordpress.com/2026/10/25/25th-october-2026/"&gt;were terrible&lt;/a&gt;&lt;/em&gt; 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.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;I think the booming FM-1 firmware scenes shows that we are missing a bigger point point. What effect do AI coding tools have for &lt;em&gt;people who use computers but never felt empowered to hack them before&lt;/em&gt; ?&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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 &lt;em&gt;really really good song&lt;/em&gt;). If you brick the device — and people &lt;a href="https://github.com/Quixotic7/MvaveFM1Unbricker"&gt;are doing that&lt;/a&gt; — 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.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;We need to see this as an entirely new way to interface with a computer. &lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;a href="https://samthursfield.wordpress.com/wp-content/uploads/2026/11/image-3.png"&gt;&lt;img alt="" class="wp-image-3786" height="880" src="https://samthursfield.wordpress.com/wp-content/uploads/2026/11/image-3.png?w=1024" width="1024"/&gt;&lt;/a&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;The oldest computers dealt with binary numbers, one bit at a time. Modern computers do exactly the same thing! They &lt;em&gt;look &lt;/em&gt;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.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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, &lt;a href="https://pivot-to-ai.com/2026/11/11/but-the-ai-is-super-good-at-updating-code-well-no-it-isnt/"&gt;that’s a terrible way to make systems software&lt;/a&gt;, 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.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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.&lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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 &lt;a href="https://lucumr.pocoo.org/2026/6/6/communities-of-not/"&gt;Communities of Not&lt;/a&gt;: “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). &lt;/p&gt;
&lt;p class="wp-block-paragraph"&gt;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.&lt;/p&gt;
&lt;figure class="wp-block-image size-large"&gt;&lt;a href="https://samthursfield.wordpress.com/wp-content/uploads/2026/11/image-4.png"&gt;&lt;img alt="Front page from FM-1" class="wp-image-3788" height="512" src="https://samthursfield.wordpress.com/wp-content/uploads/2026/11/image-4.png?w=1024" width="1024"/&gt;&lt;/a&gt;&lt;/figure&gt;
&lt;p class="wp-block-paragraph"&gt;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.&lt;/p&gt;</description>
      <guid isPermaLink="false">https://samthursfield.wordpress.com/2026/11/16/16th-november-2026/</guid>
      <pubDate>Mon, 16 Nov 2026 12:17:54 +0000</pubDate>
    </item>
  </channel>
</rss>
