Notices by Codeberg (codeberg@social.anoxinon.de)

This is somewhat of an "experiment" to see if we can use the official Mastodon account to motivate others to contribute (in a productive manner :D).

If you're looking for help / need to coordinate or would otherwise take a look at what other types of projects has to offer, here's a link: https://codeberg.org/Codeberg/Contributing/wiki/Projects#codeberg-projects

(We're pretty busy folk; although we try to be responsive, we may still miss your message.) ~n

Hi all, Codeberg currently needs help with the following: We wish to deploy the latest version of our registration form for new members (with lots of new information) under: https://join.codeberg.org

Before we do so, we need some more translations by the community. You can view a more recent version and compare here: https://join-test.codeberg.org

If there's still work left to do for your language and you have a few spare minutes, it'd help: https://translate.codeberg.org/projects/codeberg/ev-registration-server/

Source code: https://codeberg.org/Codeberg-e.V./registration-server

Newsflash: We're NOT updating how Codeberg uses data to improve "AI-powered coding assistants". (We don't.)

The first thing that people see when visiting https://codeberg.org is the following: "Software development, but free!"

However, projects hosted on Codeberg are not necessarily by developers of software—on the other hand, deciding on a new slogan can be difficult and contentious, as first impressions really matter (and there's not a lot of space there).

So, one of the people controlling the social media account decided to ask the fediverse: Any good ideas?

Following a decision by the Codeberg e. V.'s Presidium, Codeberg e. V. has joined the ranks of many organizations as a co-signatory of the draft letter of the "Keep Android Open" initiative: https://keepandroidopen.org/draft-letter/

Apart from the impact of the many independent developers hosting their source code on https://codeberg.org, we are concerned by the greater societal implications the Android ecosystem's current trajectory will cause. For more information, see: https://keepandroidopen.org

We have slightly tuned our rate-limiting after not touching it in a while. It should be "better" for most users now, but we value feedback in any case.

Check the full announcement and don't forget to subscribe to the changelog if you don't want to miss any news around Codeberg's services: https://codeberg.org/Codeberg/changelog/issues/2#issuecomment-10671812

#FOSDEM is going strong.

And cut! 🎬

This was an absolutely wonderful event—we were exhilarated by all the conversations and new people that we met, and even saw people forming queues to say hi this year! Thank you to @fosdem for the organization and all the assistance, as well as all the people that visited us!

Codeberg and Forgejo will have a stand (K5) at FOSDEM 2026 in Brussels. Come by and chat with Codeberg and Forgejo contributors.

There'll also be Codeberg and Forgejo stickers. If your Codeberg or Forgejo hosted project has stickers and you're looking for a way to distribute them: Get in touch and we can organise it!

@gsuberland

#39c3

Hey everyone, you can now follow @codebergstatus to get more granular notifications about our current system. We decided to keep the main account clear from the noise of smaller issues and allow you to explicitly opt-in to such notifications.

Important and positive news will continue to be shared on this account 😉

Once again, we are fighting with an ongoing DoS attack. We are very sorry for the disruption of the service and hope to bring the service back online soon.

We are currently fighting against a DDoS attack against our service and our status page. We are analyzing network traffic with the help of our ISP at the moment and let you know once we have updates to share.

Every couple of months, a couple of us come together to write down what we've been working on behind the scenes. The last time we did that was June. There are many exciting things (for us, at least!) that have happened since; you can read all about them in the update that we are sharing with you today:

https://blog.codeberg.org/letter-from-codeberg-onwards-and-upwards.html

And since we're sharing background: Codeberg has a working group for matters involving Public Relations—some of us are deeply involved with Codeberg's day-to-day operations, others of us have experience in putting words together for projects and group efforts like ours. (Teamwork makes the dream work!)

We did spend a lot of time on this update (and went over many details, which is why we're posting on here so late 🌃).

Hey everyone! Codeberg will go down for about 10 minutes starting 19.00 UTC (20.00 CET) to create database indices which are expected to improve performance. This requires a short interruption of service.

We apologize for the inconvenience and short notice.

There will be several short interruptions in service during the next 24 hours. Each should not last more than a few minutes.

We are performing scheduled hardware maintenance, replacing 1 of 3 physical servers. You can find the current status at https://status.codeberg.eu/status/codeberg

Great news: Today, we have managed to distribute our Forgejo instance across two servers. A main instance still handles most traffic, but requests from #CodebergPages are now handled by another server. Going forward, we'll try to route more read-only traffic there to distribute the load.

This is an important milestone, because such a setup was never tested with #Forgejo at this scale.

This should improve availability of both Codeberg.org and Codeberg Pages.

Details: https://codeberg.org/forgejo/discussions/issues/259

We apologize for the long performance degradation today.
Finally, we identified all of the 'tricks' that AI crawlers found today. They no longer bypass the anubis proof of work challenges.

A novelty for us was that AI crawlers seem to not only crawl URLs that are actually presented to them by our frontend, but they converted the URLs into a format that bypassed our filter rules.

By the way, you can track the changes we have been doing via

https://codeberg.org/Codeberg-Infrastructure/scripted-configuration/compare/51618~1..e4aac

We have upgraded to Forgejo v13. You can read the official announcement for the release here: https://forgejo.org/2025-10-release-v13-0/

If you have unexpected issues, please don't hesitate to let us know. https://codeberg.org/Codeberg/Community/issues/