fidzu : Fedora

03 Dec 2025 9:00pm GMT

It is not every day that I get the opportunity to write about bringing back a project to life, but today, finally, happens to be one such day, and Fedora Badges happens to be one such project. It feels surreal to be finally opening up about this to folks apart from those who have been actively contributing to the project, given just how many highs and lows this initiative has seen in the past three years or so. While we have not yet reached the finishing line just yet, it is with great pleasure that I want to let you know that we are closer than ever to getting there. This post captures just what we have been up to all this time and where we plan on taking this initiative next from here on out. You have been warned, though - this post would be a long one, so I would not really blame you if an LLM tool helped you cut to the chase.

Brainstorming and prioritisation

Back in early 2019, Clement Verna and Justin Wheeler kicked off the discussion of user stories for Fedora Badges from the perspective of various user personas. Requirements from stakeholders, including but not limited to artwork designers, project maintainers, badge administrators, project contributors, codebase developers, service users and community members were accounted for. This was done to identify and resolve technical blockers that slowed down the Fedora Badges development within the community, and that would, in turn, ensure that the project continues to be actively maintained even when the Community Linux Engineering (prev. Community Platform Engineering) team is occupied with responsibilities of (relatively speaking) greater importance and higher priority.

While the Fedora Design team had been (and still is) active in churning out artworks for the badges, the technical blockers limited the activities for which badges could be awarded. This necessitated an active participation with the Fedora Project leadership to both incentivise developer contribution to the technological stack as well as encourage individual contributors to seek engagement opportunities. While the discussions seemed to have become inactive and the mentioned project board seemed to have become inaccessible, the progress made then helped shape the path that we would choose next. For the curious bunch, the recording of the user stories discussions can be found on YouTube, featuring the likes of Clement Verna, Mairin Duffy, Michal Konecny and Mohan Boddu.

How about Discourse?

Around in late 2021, Matthew Miller kicked off the discussion on whether we would want to have Fedora Badges in Fedora Discussion. While there was some interest in this Discourse feature (~35% voters), a majority of folks (~53% voters) voted against the idea. Ryan Lerch remarked that the frontend did not seem to be a maintenance problem, and instead, the badges awarding backend service would need work. He further elaborated on the required changes to the backend architecture while gathering feedback on having Discourse as the frontend for the Fedora Badges stack. One of the suggestions that we incorporated was to mirror Fedora Badges assets on Fedora Discussion, thus organically including them in the conversations on the primary communication channels of the Fedora Project.

For what it is worth, moving over to Discourse definitely seemed to be the right approach here at that time, given just how letting it do the heavy lifting on the frontend side allowed us to be able to focus solely on the badges awarding backend service. As much as this was something that we wanted to work on, the Community Linux Engineering (prev. Community Platform Engineering) team had their hands full with maintaining the Fedora Infrastructure and Release Engineering responsibilities. Just like the previous attempts to rejuvenate Fedora Badges, this managed to move things further (with the inclusion of assets from Fedora Badges showing up on Fedora Discussion), but here again, there was only so much possible with the limited number of hands that we had on deck at that time.

Fulfilling forward momentum

Back in mid 2022, Vipul Siddharth sent out the call for participation to maintain the Fedora Badges project on behalf of the Community Linux Engineering (prev. Community Platform Engineering) team. With Kevin Fenzi's assistance, Erol Keskin and Sandro joined in the efforts to improve the state of the codebase for the badges awarding backend service. At around that time, I was looking into its technological stack myself, so Michal Konecny and I went ahead to propose the Advanced Reconnaissance Crew report on the Fedora Badges Revamp Project. The activities around the project were finally on the rise with the talks on translations related accolades and gathering contributor testimonials, before the Fedora Badges regular meetings were scheduled by Ellen O'Carroll and Justin Wheeler.

Calls were initially planned to be fortnightly in nature from December onwards. The year closed down with Matthew Miller's proposal on accolade progression using the Badge Path feature, before 2023 began with the Fedora Badges ARC investigation and the Fedora Badges Frontend Decision. Jefferson Oliveira and Bogomil Shopov, Marie Nordin and Emma Kidney also joined. With monthly meetings, a structure for engineering and design teams was made. We started moving our repos over to the Fedora Project's GitLab namespace, thereby using the features like Kanban, Epics, Milestones, etc., to our advantage. On the side, Smera Goel and Marie Nordin also kicked off the Outreachy Mentorship project on Fedora Badges artwork design with Chris Onoja Idoko and Roland Taylor.

Yet another fall

From the start 2023, with the discussion around directory structures, slug formats, naming conventions and developer database, we had folks like Robert Wright and Onuralp Sezer join our star cast. Matthew Miller continued chipping away at unifying Fedora Badges and Fedora Discussion. Everything seemed to be progressing just right on all sides, but then we slowly started losing numbers in the second half of the year. Folks who were previously contributing actively either had to context switch temporarily or step away permanently. This had quite an impact on those who stayed back due to the accumulating work pressure. While I kept progressing with Sandro and Onuralp Sezer, it became virtually impossible to lead this besides working on the Git Forge Move Initiative and Pagure Exporter.

If you have been keeping the count, this marked the third time when the efforts seemed to have fizzled out again. It was beyond annoying that we could not get more people actively engaged (and hence, have the agency to pass the torch when needed) while we had the momentum. With the impending end of support date for Fedora Badges' host OS, Red Hat Enterprise Linux 7, approaching, Aurelien Bompard took the responsibility to port the technological stack from Pyramid to Flask, which kept the service going, but it felt horrible to have left things undone. Before we met for the last time (for a while) in June 2024, I gathered as many learnings as possible from all these endeavours so that whenever we ended up revisiting the project in the future, we would not make the same mistakes again.

Four leaf clover

While I could not make it to the Fedora Council as an elected representative, I managed to get elected to the Fedora Mindshare during the Fedora Linux 42 Release Cycle in May 2025. As contribution retention had been one of the notable issues I wanted to address during my tenure in the committee, I wanted to make the best use of my representation to push the Fedora Badges Revamp Project back on its feet. While the repositories were out in the open, I resisted the temptation of making any public announcements on Fedora Discussion as the Fedora Badges project was not the priority at the moment. That way, I could contribute to the project at the pace that suited me the best, and others could join in asynchronously too, while both they and I were busy with our respective commitments on the side.

After almost a year-long hiatus away, I decided to create a project board and throw my plans at it. Nothing serious and nothing pressuring - But something that everyone could explore around and contribute to whenever they felt like it. We had contributors like Shounak Dey, Aurelien Bompard, Xavier Lamien, and Michael Scherer rolling in gradually, with varied degrees of contribution extent. As I was mostly working on the revamp project for approximately 20% of my work hours, there was a certain peace in the experience. With almost 70 items on the project board, around 60 commits made and 90 files changed, things might actually end up working this time around. Scratch that - it will cross the finish line this time, I am sure of it, just lend me your hands with whatever you want or can to help with.

Showcase

Enough of the contextual background for now, I suppose - let's move over to some groundwork. After all, there is nothing like getting awarded the Dancing With Toshio badge during Flock To Fedora 2025, which gets you wanting to work on the Fedora Badges Revamp Project, right? Here is a walkthrough for those four of you who want this badge for yourselves from the person themselves, Toshio Kuratomi.

Exhibition

The test deployment can be found on https://badges.gridhead.net/. This is set up on a Fedora Linux 42 QEMU x86 virtual machine with 8GiB virtual RAM, 4 virtual cores and reverse proxied through Cloudflare. If things look broken there, some work is likely being done at that time on the deployment, but if it stays down for longer than a couple of hours, please reach out to me at @t0xic0der:fedora.im .

If you have signed the Fedora Project Contributor Agreement, you should also be able to access the administration page after logging in using your staging Fedora Accounts credentials. As the database provided here is a snapshot copy of that of the production Fedora Badges deployment on 01 December 2025, people can feel free to play around with the test deployment to see what the service is capable of.

Comparison

Here is a catalogue of images that show what the user interface looks like at the moment in the legacy deployment and what it would end up looking like down the road. Please note that the Fedora Badges Revamp Project is still in development, so these elements are not representative of the final quality. As always, we welcome all feedback, big or small, on #badges:fedoraproject.org Matrix chatroom.

Landing page

Can be accessed through
https://badges.gridhead.net/

Collection page

Can be accessed through
https://badges.gridhead.net/assembly

Recently page

Can be accessed through
https://badges.gridhead.net/recently

Rankings page

Can be accessed through
https://badges.gridhead.net/rankings/y/2025/m/11

Leaderboards page

Can be accessed through
https://badges.gridhead.net/rankings

Identity page

Can be accessed through
https://badges.gridhead.net/identity/t0xic0der

Userpast page

Can be accessed through
https://badges.gridhead.net/userpast/t0xic0der

Accolade page

Can be accessed through
https://badges.gridhead.net/accolade/dancing-with-toshio

Curatorium

While a bunch of user interface elements were overhauled to offer a refreshed look and enhanced feel, it did not make sense to have some of them around anymore. Please note that the Fedora Badges Revamp Project is still in development, so these elements are not representative of the final quality. As always, we welcome all feedback, big or small, on #badges:fedoraproject.org Matrix chatroom.

Global search

Supports lookup for users and badges

Dark mode

Native support for system theming preferences

Digital vibrance

Offering custom colours for custom personalities

Streamlined administration

Easy and effective control over service

Rarities

One of the new features coming to Fedora Badges as a part of the Revamp Project is computing rarities for activated accolades. Inspired by video games, this provides users with the means to find accolades with varied rates of awarding, which, in turn, should help them find renewed avenues for contributions. Here are some glimpses of what the feature would end up looking like when implemented.

Foundational

Apart from the shiny changes, there have also been a bunch of robust changes to the foundational aspects of the Tahrir and Tahrir API projects. Please visit the GitHub repositories associated with the Fedora Badges Revamp Project in order to learn more about them. Like always, please feel free to take the projects for a spin locally, and when ready, you can contribute to the upstream in any way possible.

Contribution

If you are moved by the efforts put in by the folks since three years and/or are impressed by the aforementioned changes, now is the best time to begin contributing to the project if you have not already. We could honestly use all the help we could get and would provide the mentorship required for the contributors in ensuring that the project ends up crossing the finishing line satisfactorily.

Resources

• Fedora Badges Frontend - Fedora Infra - GitHub
• Fedora Badges Database API - Fedora Infra - GitHub
• Fedora Badges Backend Service - Fedora Infra - GitHub
• Fedora Badges Artworks - Pagure
• Fedora Badges Category - Fedora Discussion
• Fedora Badges Chatroom - Fedora Chat

01 Dec 2025 6:30pm GMT

I keep not having time to work on documentation, and it's so very important, so in an effort to see what progress I can make I am going to try and submit / merge at least one doc pull-request or close / comment on at least one docs ticket every day in december.

I'm going to concentrate on the infrastructure docs of course, but I might branch out into other areas where I could help.

When we moved our docs over to https://pagure.io/infra-docs-fpo/ we also created tickets to review all our standard operating procedures, and I can definitely work on cutting those down.

I also might miss some days, but then again I might do more on some other days, but I am going to try and do something every day in december. The most challenging days are likely to be in the next few weeks before the holdays as I am trying to get a datacenter move done and finish things up.

I'm just doing this myself, but if others would like to join in feel free to do so! I'd also love to have folks reviewing the pr's I submit also.

Should be fun!

Comments/replies:

https://fosstodon.org/@nirik/115634308295278960

29 Nov 2025 5:54pm GMT

Here is a short shell script to show last logins from SSH, XRDP, SUDO and Cockpit. In addition it show potential disk problems from S.M.A.R.T.

#!/bin/sh

default_since='-1days'
default_priority=info

read -r -d "" data << END_OF_DATA
System login         ^ systemd-logind          ^ info  ^         ^ New session 
XRDP                 ^ xrdp-sesman             ^ debug ^ -5days  ^ logged in|Received system login request
Cockpit login        ^ cockpit-session         ^       ^         ^ session opened
SUDO                 ^ sudo                    ^       ^         ^ session opened
Storage problems     ^ smartd                  ^       ^ -1days  ^ uncorrectable|unreadable
END_OF_DATA

trim() {
    local s="$*"
    
    # remove leading whitespace
    s="${s#"${s%%[![:space:]]*}"}"
    
    # remove trailing whitespace
    s="${s%"${s##*[![:space:]]}"}"
    
    printf '%s' "$s"
}

IFS="^"
echo "$data" | while read title slid priority since grep; do
        effective_since=$default_since
        effective_priority=$default_priority
        
        [[ -n "$(trim $since)" ]] && effective_since="$(trim $since)"
        [[ -n "$(trim $priority)" ]] && effective_priority="$(trim $priority)"

        echo "$(trim $title)"
        journalctl \
                --no-pager \
                --no-tail \
                --since $effective_since \
                --priority $effective_priority \
                --reverse \
                --grep "$(trim $grep)" \
                -- SYSLOG_IDENTIFIER="$(trim $slid)"

        echo; echo
done

I made it with the help of Cockpit Logs feature that shows the actual command being executed based on how you configure it.

The most important part of the script is the journalctl command. Everything else are defaults, the list of desired syslog identifiers and what to extract from them, and output formatting.

29 Nov 2025 1:36pm GMT

Hoy me acordé de lo útiles que son los atajos de Readline.

Estaba tecleando un comando larguísimo y me equivoqué al final. En lugar de borrar todo, usé Ctrl + A y Ctrl + E para saltar, y Ctrl + W para borrar palabras. ¡Chido! Readline es la librería que hace que Bash sea tan poderoso. Con sus atajos, editas líneas como un pro, sin mouse. La neta, una vez que los aprendes, no vives sin ellos.

28 Nov 2025 4:00pm GMT

Prá quem quer investir em criptomoedas, e tem estômago, e tem tempo para esperar, e sabe fazer, e sabe guardar por longo prazo, talvez agora seja um bom momento para começar pois o preço do Bitcoin caiu bastante nos últimos dias e parece estar retomando o crescimento (mas ninguém sabe do futuro).

Lembre-se que Bitcoin é ativo escasso, que tem expectativa de valorização (ou não), e diversos países já o usam como reserva de valor. Exatamente como ouro. Você pode não compreendê-lo, achar que é moda inútil, que gasta muita energia minerá-lo - exatamente como o ouro tem todas essas características -, mas fato inegável é que há um mercado mundial pujante que paga imediatamente e legalmente o valor em Reais que aparece na imagem por 1 bitcoin, se você o colocar à venda. Novamente, exatamente como é o ouro e outros metais e pedras preciosas, com a única diferença de que o Bitcoin só precisa da Internet para existir e ser transportado.

Bitcoin em si jamais vai substituir dinheiro, exatamente da mesma forma como ouro não é aceito no caixa do supermercado - precisa ser vendido/convertido antes de usar. Outras criptomoedas têm dinâmicas, propostas e finalidades diferentes, algumas muito interessantes. Mas acima de tudo você deve evitar as memecoins, pois não tem valor intrínseco nem utilidade nenhuma.

Colecionar ou guardar relógios, arte, jóias, selos ou criptomoedas são práticas muito parecidas do ponto de vista psicológico. Todos ativam algum valor diferente no imaginário humano. Status por beleza, status intelectual pelo valor histórico ou status por status mesmo. Nada disso coloca comida na mesa, não te salva de um cataclisma apocalíptico nem dá paz de espírito. Mas são todas coisas que a psique humana valoriza de alguma forma. Vai entender.

Também no meu LinkeIn.

28 Nov 2025 12:39pm GMT

26 Nov 2025 7:00am GMT

Getting a start on your holiday shopping this weekend? Give the gift of knowledge to yourself or the people you love! Use promo code save50 at pragprog.com through December 1 to save 50% on every ebook title (except The Pragmatic Programmers).

Not sure what you should get? If you don't have a copy of Program Management for Open Source Projects, now's a great time to get one. I've been a technical reviewer for a few other books as well:

• Forge Your Future with Open Source by VM Brasseur
• Designing Data Governance from the Ground Up by Lauren Maffeo
• Guiding Star OKRs by Staffan Nöteberg
• Business Success with Open Source by VM Brasseur

I've read (or have in my stack to read) other books as well:

• Manage It! by Johanna Rothman
• Real-World Kanban by Mattias Skarin
• Hands-On Rust by Herbert Wolverson
• Advanced Hands-On Rust by Herbert Wolverson
• Powerful Command-Line Applications in Go by Ricardo Gerardi

With hundreds of titles to choose from, there's something for you and the techies in your life.

The post Pragmatic Bookshelf half-off sale! appeared first on Duck Alignment Academy.

25 Nov 2025 9:49pm GMT

Hoy me acordé cuando un compa me pidió ayuda con su laptop llena de virus y lentitud. La neta, Windows es como una novia celosa: te controla todo y te deja sin libertad. Pero GNU/Linux es abierto, gratis y bien chingón. Vamos a migrar paso a paso para que no te pierdas en el camino.

25 Nov 2025 4:00pm GMT

It's finally here. We have an end date for OpenID in Fedora. The date is 1st May 2026. You can see it on the banner on https://id.fedoraproject.org/openid and it will be shown to you every time when trying to authenticate with OpenID. The date 1st May 2026 should give anybody still using OpenID authentication enough time to migrate to OpenID Connect.

We started our move to OpenID Connect and away from old OpenID authentication 4 years ago. This was a long road with plenty of obstacles on the way. We first ported all apps we own in Fedora Infrastructure to OpenID Connect. That took time, but we had at least control over these applications.

After porting all our applications we started to look at the application using OpenID authentication outside of Fedora ecosystem. This proved to be really difficult as those clients don't need to register with Fedora Authentication System.

After some failures to contact the projects that we at least identified to use OpenID in Fedora, we decided that the best course of option is to separate the OpenID authentication system (the service that is providing it is called Ipsilon, which we want to decommission as well). I spent the last two months working on separating the OpenID authentication from OpenID Connect and SAML2. You can see the result on https://id.fedoraproject.org/openid.

This will now allow us to replace Ipsilon for both OpenID Connect and SAML2 and as most of the separation logic is in proxies, we should have no issue to reuse that for the new solution. This should resolve plenty of issues we are experiencing with current authentication system and let us remove one service from the portfolio of services we own in Fedora Infrastructure. We are looking forward to brighter future!

The post End of OpenID in Fedora appeared first on Fedora Community Blog.

25 Nov 2025 3:10pm GMT

¿Quieres aprender Vim?

Vim es un editor de texto muy perro que ha estado por ahí desde hace décadas. La neta, al principio parece complicado, pero una vez que lo dominas, ¡tu productividad se dispara! En este artículo, te cuento lo básico de Vim y unos consejos útiles para que empieces.

24 Nov 2025 4:00pm GMT

OK, Zoo might slightly be overstating it.

Let's start at the beginning.

In March 2019, we moved from Barcelona into the countryside.
While I grew up in a village and studied in a small town, my recent life I spend in London and Barcelona.
It was also my first house, farmhouse even, having lived in flats most of my life.

So clearly, I thought about how I could complete my cosplaying of country life.

"A dog and a cat would be nice at some point"

A couple of months later…

Cheeky & Foggy - July 2019

I planned to clean out our small barn, and to my surprise discovered a litter of kittens.

I remembered that I saw a bigger cat going through or garden, which might have been pregnant.

She picked up most of the litter, but left Cheeky (black one) and Foggy (white one) back.

They got used to us and the house quickly. Cats are great, they understand potty training on their own. They stay clean on their own.

We obviously bought all the toys, feeding station, and a cat flap once they got a little bigger.

When they were small, they climbed on top of me and my shoulders while watching telly.

Now they are more attached to my partner and just tolerate me.

I thought: "Two cats, that's great. At least they can play together. Maybe a dog at some point".

A couple of months later…

Hoover - October 2019

I was in Barcelona on a Friday for Future protest when my partner called me. She had found an injured dog in the road and naturally picked him up. It took me a while to get back with train and bicycle. When I arrived, I was greeted by a sad and hurt beagle.

We found a 24h vet clinic in the next town and got him checked out.

He might have been attacked by other dogs or wild animals. He was in a pretty bad shape.

We got him fixed up and also removed a growth on his leg.

He was chipped, but the chip was not registered.

I came up with the name Hoover, as he had a cone of shame for a while, and he did look like a vacuum cleaner when doing the sniffing around. He reacted directly to the (new) name.

After a while, we wanted to register him with the town. That's when we learned about the previous owner. He was known to the town hall, and apparently not great with animals, they would have preferred not to give the dog back.

In Spain, if you find a dog and then return it to the owner, the owner has to pay for any vet expenses. Since we had paid exceeding 1000 Euro by now, the owner decided that he didn't want Hoover back (his original name was Bruno).

He got used to us so quickly, and is now the most cuddly dog you can imagine.

He gets along with the cats well.

Me: "This is great. A dog and two cats. Pet achievement reached"

Quite a few months later…

Yuki - February 2021

When we are travelling, we leave our dogs at a local dog hostel. We are friends with the owner, and she thought of us when she came across an abandoned dog.

The dog was called Mia at the time, which is a very common name. We renamed her Yuki after asking Reddit for suggestions.

She was super undernourished and needed a good clean.

She didn't really get along with me, or maybe men in general. She did like Hoover and my partner. The cats, not so much.

So obviously, we cared for her, fed her well, and made sure she felt at home with us.

Me: "OK, two dogs, two cats. This is perfect."

A few weeks later…

Yukitos - March 2021

She was gaining weight, which was great. At some point on one of our walks, noticing Yuki's size, I said to my partner: "I think she is pregnant".

A trip to the vet and an X-ray confirmed this. The same vet hadn't noticed anything just two weeks ago. Hidden in Yuki's tummy were eight little puppies.

We had a home birth in our living room. There were still COVID-19 restrictions in place and we were working from home.

We had to feed them with bottles, as Yuki was too undernourished to provide for them.

Sadly, three of them didn't make it. I am sure we did something wrong.

I now also have a lot more respect for parents. The bottle feeding continued for two months, and I don't think I slept at all during this time. My brain was not really functioning when at work.

The five that grew were quite fun, active, and destructive. Our living room didn't survive them.

One, we gave to my partner's parent: Seven.

One went to a village nearby with lots of space to roam: Lola.

In what turned out to be a big mistake … which I probably would make again, we kept three of them: Neo, Baty, and Crash.

And that it is for now. I ended up with four dogs and two cats. They are exhausting and have changed our life. I wouldn't change a thing.

A few months later…

I am just kidding.

We did temporarily take in a cat, which sadly died in our care. I was really fond of Charlie.

And we sometimes host other dogs for a while.

For all other pets, we encounter, we have found the original owners.

As I said in the beginning, that "zoo" is overstating it a bit, and that is true. We do have constant visits from other animals in our garden: other cats, birds, snakes, badgers, foxes, rabbits, mice, rats, martens, …

If I learned anything from all of this, then it is that I am not good at saying no to an animal in need. Since we have a crowded house already, I have to be better at it.

24 Nov 2025 10:23am GMT

There have been a few discussions about what Flathub should do to push developers to maintain their apps on the latest versions of the published runtimes. But most of those lack important details around how this would actually happen. I will not discuss in this post the technical means that are already in place to help developers keep their dependencies up to date. See the Flathub Safety: A Layered Approach from Source to User blog post instead.

The main thing to have in mind is that Flathub is not a commercial entity like other app stores. Right now, developers that put their apps on Flathub are (in the vast majority) not paid to do so and most apps are under an open source license.

So any discussion that starts with "developers should update to the latest runtime or have their apps removed" directly contradicts the social contract here (which is also in the terms of most open source licenses): You get something for free so don't go around making demands unless you want to look like a jerk. We are not going to persuade overworked and generally volunteer developers to update their apps by putting pressure on them to do more work. It's counter productive.

With that out of the way, how do we gently push developers to keep their apps up to date and using the latest runtime? Well, we can pay them. Flathub wants to setup a way to offer payments for applications but unfortunately it's not ready yet. So in the meantime, the best option is to donate to the projects or developers working on those applications.

And make it very easy for users to do so.

Now we are in luck, this is exactly what some folks have been working on recently. Bazaar is a Flathub first app store that makes it really easy to donate to the apps that you have installed.

But we also need to make sure that the developers actually have something set up to get donations.

And this is were the flatpak-tracker project comes in. This project looks for the donation links in a collection of Flatpaks and checks if there is one and if the website is still up. If it's not, it opens issues in the repo for tracking and fixing. It also checks if those apps are using the latest runtimes and open issues for that as well (FreeDesktop, GNOME, KDE).

If you want to help, you can take a look at this repo for apps that you use and see if things needs to be fixed. Then engage and suggest fixes upstream. Some of this work does not require complex technical skills so it's a really good way to start contributing. This is probably one of the most direct way to enable developers to receive money from their users, via donations.

Updating the runtime used by an app usually requires more work and more testing, but it's a great way to get started and to contribute to your favorite apps. And this is not just about Flathub: updating a Qt5 app to run with Qt6, or a GNOME 48 app to 49, will help everyone using the app.

We want to build an App Store that is respectful of the time developers put into developing, submitting, publishing, testing and maintaining their apps.

We don't want to replicate the predatory model of other app stores.

Will some apps be out of date sometimes? Probably, but I would rather have a sustainable community than an exploiting one.

23 Nov 2025 11:00pm GMT

Just a quick post to note my blogiversery.

22 years ago in 2003 I posted my first entry here.

Back then I was running a very new version of something called wordpress, then switched to wordpress-mu, then back to wordpress when multiuser came back into core wordpress and then finally to nikola.

It may be that blogs are out of vouge these days, but I still find them nice for longer thoughts that seem way too busy for social media.

23 Nov 2025 6:14pm GMT

¡Heytale! ¿Quieres saber sobre Podman?

Podman es un motor de contenedores sin daemon para desarrollar, gestionar y ejecutar contenedores OCI en Linux. ¡A diferencia de Docker, no necesita un daemon corriendo, lo que lo hace más seguro y eficiente! Es compatible con imágenes Docker y se integra con Kubernetes para despliegues en la nube.

# podman con systemd
## iniciar contenedor
podman run -di --name cs10-systemd centos:stream10

## instalar systemd y postgresql
podman exec cs10-systemd dnf -y install systemd postgresql-server sudo

## limpiar
podman exec cs10-systemd dnf clean all

## commitear a imagen
podman commit -s cs10-systemd cs10-systemd

## borrar contenedor
podman rm -f cs10-systemd

## correr con systemd
podman run -dt -p 127.0.0.1:5432:5432 --name=cs10-systemd localhost/cs10-systemd /usr/sbin/init

## configurar postgresql
podman exec cs10-systemd postgresql-setup --initdb

## habilitar e iniciar postgresql
podman exec cs10-systemd systemctl enable --now postgresql

## crear usuario y db
podman exec cs10-systemd sudo -u postgres createuser -dRS --no-replication renich
podman exec cs10-systemd sudo -u postgres createdb renich
podman exec cs10-systemd sudo -u postgres psql -c "ALTER USER renich WITH PASSWORD 'MySuperPass';"

## crear pg_hba.conf
cat << EOF > pg_hba.conf
local all all peer
host all renich 127.0.0.1/32 scram-sha-256
host all renich ::1/128 scram-sha-256
EOF

podman cp pg_hba.conf cs10-systemd:/var/lib/pgsql/data/pg_hba.conf
rm -f pg_hba.conf

## verificar
podman exec cs10-systemd systemctl restart postgresql
podman exec cs10-systemd systemctl status postgresql

PGPASSWORD='MySuperPass' psql -h 127.0.0.1 -l

# limpieza
podman rm -f cs10-systemd
podman rmi cs10-systemd

23 Nov 2025 6:00pm GMT

Another busy week in fedora infrastructure. Here's my attempt at a recap of the more interesting items.

22 Nov 2025 8:48pm GMT