The Pope Wrote About AI and Self-Hosters Should Care

A few weeks ago, Pope Leo XIV released a 52-page document on artificial intelligence. The document is titled Magnifica Humanitas of His Holiness Pope Leo XIV on Safeguarding the Human Person in the Time of Artificial Intelligence. Yes, the Vatican has its own top-level domain. Yes, the Pope quoted Gandalf. No, this is not satire. The document is a serious case against unregulated AI growth, and three passages land especially hard for self-hosters. The same week, a severe Gitea vulnerability needed patching right away. The combination tells a story about where the self-hosted world sits in 2026: patching on time, debating with care, and shipping useful tools.

If you run your own stack, here is what you actually need to know.

What the Pope got right about AI

Three passages from the document are worth quoting. They are not theological, they are practical, and they apply directly to anyone running language models on a homelab.

First, the document notes that current AI systems are more “cultivated” than “built,” because developers do not directly design every detail but instead create a framework within which the intelligence “grows.” If you have trained a small language model on your own data, you have seen this firsthand. You pick the base model, you set the hyperparameters (the configuration values that control how the model learns, like learning rate and batch size), you curate the training data, and the model that emerges is partly shaped by choices you made and partly by patterns you did not anticipate. The Pope’s framing is correct, and it matters because it shifts accountability away from “the model did something bad” and toward “the people who built the framework are responsible for the behavior that emerged.”

Second, the document argues that development is not truly human if it increases consumption for some while shifting costs and burdens onto others. This applies to AI in three concrete ways. The environmental cost of training large models is concentrated in a handful of data centers. The labor cost of the human data workers who label training examples is mostly hidden. The social cost of replacing human labor with automated systems falls on the workers, not on the companies that deploy the automation. Self-hosters who run small models on their own hardware are not contributing to the environmental cost in any meaningful way, but they are participating in the broader social question of what AI is for.

Third, the document argues that the apparent objectivity of AI responses can lead us to overlook the fact that they reflect the cultural assumptions of those who designed and trained them. Data is the product of many contributors and should not be treated as something to be sold off or entrusted to a select few. This is the passage that matters most for self-hosters, because the entire premise of running your own model is that you want some control over the data and the inference. If you are running Ollama (a tool that downloads and runs open-weight large language models on local hardware) with an unmodified base model, you are inheriting the assumptions of the people who trained it. If you are fine-tuning (taking a pre-trained model and continuing its training on a smaller, task-specific dataset) on your own data, you are taking partial ownership of those assumptions.

Simon Willison has a clean highlights post that condenses the document if you do not want to read all 52 pages.

The Gitea vulnerability you should have patched by now

While the Pope was writing about AI, security researchers were finding a severe vulnerability in Gitea (an open-source, self-hostable code-hosting platform similar to GitHub) and Forgejo (its community-governed fork). The vulnerability exposed private images on misconfigured instances. If you self-host either of these, the fix has been out for weeks and you should have updated already. If you have not, do that first and then come back to this article.

Forgejo is the fork many self-hosters prefer because it has fully open governance, so the fix should land quickly on both projects. The underlying lesson is the one we keep relearning: do not expose Gitea or Forgejo to the open internet without a reverse proxy (a server that sits in front of your application to handle TLS encryption, authentication, and rate limiting), authentication, and a real backup plan. A one-line apt upgrade or image pull is the difference between a quiet week and a leak.

Three smaller stories worth knowing

The same newsletter that covered the Pope’s document and the Gitea vulnerability also surfaced three smaller stories that are easy to miss but useful for anyone running their own stack.

Homarr (a self-hosted dashboard for organizing all your homelab services into one page) trimmed its memory footprint after public complaints a few months ago. If your Homarr dashboard used to feel heavy, give it another try. The kind of low-effort responsiveness that produced this fix is what makes open source worth using.

Hypermind-Swarm is a new P2P chaos tool from the creator of Hypermind, this time with built-in social features. P2P chaos tools are weird, niche, and occasionally indispensable. Worth a bookmark if you run any kind of distributed setup.

A small newsletter reader is doing more community work in the self-hosting space. The exact project was cut off in the original feed, but Self-Host Weekly consistently surfaces these small announcements, and that is how the wider community stays healthy.

Why this week felt bigger than usual

There is a pattern here. A religious leader publishes a thoughtful critique of AI, a self-hosted code-hosting platform ships a critical security fix, and the indie tools keep shipping. The self-hosted world is no longer a counterculture. It is the part of the internet that still patches on time, debates with care, and respects the people building it.

That said, the week also surfaced three concrete trade-offs that are worth naming.

• Reading a 52-page PDF is not realistic for most self-hosters. Simon Willison’s highlights post is the practical entry point. Five minutes gets you the substantive passages.
• Gitea and Forgejo security updates only help if you actually pull them. A container that has not been restarted in six months is not a patched container, regardless of what your package manager reports.
• P2P tools are fun but unreliable. Treat Hypermind-Swarm like a toy until the protocol stabilizes. Bookmark it, do not depend on it.

A five-minute action list

The single most important action this week is to update Gitea or Forgejo on every host you run, restart the container, and verify the version in the web UI. That one action closes a known security vulnerability and takes five minutes. Everything below is optional but useful.

Anyone with a few more minutes should skim Simon Willison’s highlights of the papal AI document. It is the most concise version available and the framing applies to anyone running local models. The five-minute read is worth the time, especially if you have not thought about AI policy in your homelab context before.

Readers with an hour can do the housekeeping that has been sitting on the list:

• Pull the latest Homarr image if you used to run it. The memory footprint complaint has been addressed in the latest release.
• Star Hypermind-Swarm on GitHub so you remember to check back when it has more than a handful of users. P2P tools live and die on whether anyone bookmarks them.
• Skim the Self-Host Weekly issue from May 29 for one story you missed. The newsletter surfaces small announcements that do not make it to the bigger feeds.
• Forward the Self-Host Weekly to one friend who has been meaning to self-host something. That is how the community grows.

Bottom line

The AI debate is no longer optional reading for self-hosters. You do not have to take a side, but you should know what the conversation looks like when it reaches your family group chat. Patch your code-hosting tools, read the highlights, and remember that the self-hosted world is at its best when it treats the hard questions seriously and the easy fixes casually.

If I could send a message to the version of me that was running an unpatched Gitea instance three weeks ago, I would say: the 52 pages from the Pope are interesting, but the five minutes you spend running apt upgrade matters more for your homelab this week. Do that first.