Notices by Codeberg (codeberg@social.anoxinon.de), page 2

We apologize for a period of extreme slowness today. The army of AI crawlers just leveled up and hit us very badly.

The good news: We're keeping up with the additional load of new users moving to Codeberg. Welcome aboard, we're happy to have you here. After adjusting the AI crawler protections, performance significantly improved again.

It seems like the AI crawlers learned how to solve the Anubis challenges. Anubis is a tool hosted on our infrastructure that requires browsers to do some heavy computation before accessing Codeberg again. It really saved us tons of nerves over the past months, because it saved us from manually maintaining blocklists to having a working detection for "real browsers" and "AI crawlers".

However, we can confirm that at least Huawei networks now send the challenge responses and they actually do seem to take a few seconds to actually compute the answers. It looks plausible, so we assume that AI crawlers leveled up their computing power to emulate more of real browser behaviour to bypass the diversity of challenges that platform enabled to avoid the bot army.

We have a list of explicitly blocked IP ranges. However, a configuration oversight on our part only blocked these ranges on the "normal" routes. The "anubis-protected" routes didn't consider the challenge. It was not a problem while Anubis also protected from the crawlers on the other routes.

However, now that they managed to break through Anubis, there was nothing stopping these armies.

It took us a while to identify and fix the config issue, but we're safe again (for now).

We, the operators of this social media account, sometimes face dilemmas about what we want to post. For example: "Are you a Hubber and want to become a Berger? We're looking forward to you!"

Love it or hate it, one thing is certain: It doesn't really matter, because others are doing our marketing today. 🙃

#Codeberg #GiveUpGitHub #GitHub

@namelessvoice To add: There is a proposal on changing our terms on licensing a bit more with the stated intent of making it less "specific" in the way that you mentioned – however, it is far from official. It should be put up to a vote among members of Codeberg e.V. in the coming week. (Disclaimer: I'm one of the proposal's authors, but what I'm trying to say is "we are aware of that criticism and are looking into it".) ~n

P.S. @hannah's link does clarify our stance on private repositories.

Psst... looking for a new club to join? 👀

Great news, ours is looking for new members: https://codeberg.org

If you're out and you'd rather stay out, we would absolutely recommend the easy-to-self-host @forgejo: https://forgejo.org

(We are a bit biased, though. 😄)

Codeberg now has an experimental way to report abuse to admins. It's WIP in #Forgejo and is going to be released in version 13 in some months. However, we deployed it on Codeberg to get some insights on how it works. Looking forward to your feedback!

The work was sponsored by @nlnet. Thank you very much!

It looks like we are under attack, that caused SSH connections to fail. We have deployed mitigations and the situation calmed down. Please let us know if the issue occurs again.

Codeberg is currently unreachable, apparently due to a network outage at our provider. We'll hit you up as soon as we know more.

We're back. It looks like all servers (all datacenter?) lost power, but we have no confirmed information on the background yet.

From a quick ping on various services, it seems the issue is not with our volunteer-driven rackspace provider, but affecting the whole datacenter we're located in.

Which might be good news, because it then doesn't rely on volunteers to fix the issue, but on professional staff 😉.

@evan The decision to block these scrapers actually originates from an Codeberg-e.V. internal discussion. The argument for "visibility" in the AI language models was considered. However, the cost on Codeberg is immense (also see https://drewdevault.com/2025/03/17/2025-03-17-Stop-externalizing-your-costs-on-me.html), and we are also not fans of the Big Tech AI companies.

Codeberg is a development platform. If your content needs to be known to all scrapers, you are free to publish valuable resources to a normal website additionally.

We couldn't believe it at first, but one of the most common numbers guessed about the #IPv6 adoption among logged-in users is 42%. We assume that many users took this number as a joke. But in all seriousness: it is correct! (It is exactly 42.0095476% higher than that of our largest competitor #GitHub 😄)

We boosted the first post with that guess, but feel free to browse all the other awesome project recommendations made in this thread, too!

(Context on the number 42: https://en.wikipedia.org/wiki/Phrases_from_The_Hitchhiker%27s_Guide_to_the_Galaxy#The_Answer_to_the_Ultimate_Question_of_Life,_the_Universe,_and_Everything_is_42 )

How much of Codeberg's logged-in users are connecting via #IPv6, in percent?

Send your guess as a comment and optionally include a link to your favourite project on Codeberg.

First closest guess will get boosted.

@zkat Yeah, I don't have a favourite messaging app either. However, it feels like choosing Discord is similar to choosing GitHub, because *something is not quite right yet*.

~f

We are still struggling with hardware failure on our primary machine. Several services like Forgejo, Weblate and Woodpecker CI are not yet distributed across our servers.

To give us piece of mind when doing further investigation and hardware maintenance on that node, several services will be moved, starting with Forgejo tonight.

This will result in some minutes of downtime while the instance moves from one mountain to another (our servers are named after mountains).

Thanks for understanding.

We have migrated the primary Forgejo instance from "Kampenwand" to "Achtermann" now and everything is expected to run stable. Let us know if you face any issues.

For some minutes, the page showed a banner with " WARNING: THIS IS A TEST INSTANCE. DATA CAN VANISH AT ANY TIME.". No data was at danger, or lust but we simply forgot to remove the warning before doing the actual switch.

For some minutes, SSH host key verification failed. If you accepted the new key, please restore the previous one. The keys are listed in https://codeberg.org/Codeberg/org/src/Imprint.md#ssh-fingerprints.

The migration wasn't as smooth as we hoped but the impact has not exceeded our expectations.

We apologize for the inconvenience, and are now looking forward to see you pushing the code you worked on in the meantime 🚀