Newsflash: We're NOT updating how Codeberg uses data to improve "AI-powered coding assistants". (We don't.)
Remote
Codeberg
@Codeberg@social.anoxinon.de
mastodon 4.7.2We are a non-profit, community-led organization that helps free and open source projects prosper. Our services include Git hosting (https://codeberg.org, using @forgejo@floss.social), Weblate, Woodpecker CI and Pages.
To receive assistance (faster), request features or report problems, see: https://docs.codeberg.org/contact
This account is volunteer-run; we are only active for a few hours per week, so we may not be able to respond to your inquiry.
Status: @codebergstatus@social.anoxinon.de · https://status.codeberg.eu
27602 Followers
425 Following
50 Posts
Joined October 20, 2022
Hosted at:
Documentation:
Frequently Asked Questions:
Have you ever wanted a Codeberg t-shirt? Maybe a polo shirt? What about a towel or a mug? A barrel bag?! If that's the case, we put together a list of places where you can get them from: https://merch.codeberg.org
To be clear, we don't produce, sell or earn a commission from any sales made. Our logos can be used to print garments at no cost. (If you're interested in doing it yourself, you can get them here: https://codeberg.org/Codeberg/Design)
Replying to on social.anoxinon.de
Fun fact: Codeberg was born as a direct consequence of a false DMCA takedown (those were very popular a decade ago) against the @gadgetbridge@social.anoxinon.de repository—an indie Android app that helps users control their own gadgets (smart wearables). If that didn't happen, we most likely wouldn't exist today.
Gadgetbridge is still hosted on Codeberg to this day and available on alternative app stores such as @fdroidorg@floss.social and @IzzyOnDroidOrg@floss.social.
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
Psst... we've been silently attending events every now and then, but a bunch of people within the Codeberg team are attending the #gpn24 in Karlsruhe, Germany. We may have restocked our sticker stash – if you're there, keep your eyes peeled. 👀
We deployed Forgejo v15 and started to restrict the granted storage from "unlimited" to very generous quota.
Please read the full announcement in our changelog: https://codeberg.org/Codeberg/changelog/issues/2#issuecomment-13512086
(Don't forget to subscribe the relevant feeds if you haven't already!)
#FOSDEM is going strong.
Over the past year, our best minds were tasked with developing new Codeberg features that we planned to launch today... "inject ads to pull requests", "announce NEW ways to opt-out", "charge self-hosters"...!
We believe that an unidentified insider has been leaking all of them, but did not mention the following to the recipients—which we are, as this has gone too far: They were intended to be April Fool's jokes, not part of our business model.
Thank you.
Replying to
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".
We've deployed Forgejo v14 a hour ago.
Forgejo v14 includes user-facing changes and improvements, which can be read at https://forgejo.org/2026-01-release-v14-0/
If you find regressions or bugs, we ask you to report them at https://codeberg.org/Codeberg/Community/
Replying to
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.
If not now, then when?
https://www.theregister.com/2025/09/05/github_copilot_complaints/
Replying to
For the load average auction, we offer these numbers from one of our physical servers. Who can offer more?
(It was not the "wildest" moment, but the only for which we have a screenshot)
Replying to
Keep in mind that this is explicitly not a public vote, but rather a "call for inspiration", if we may. We'd rather avoid a Boaty McBoatface (https://en.wikipedia.org/wiki/Boaty_McBoatface) type of situation, but humorous suggestions remain nevertheless welcome! 😉
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
Replying to
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).
Replying to
Woah, those are nearly 200 (good/humorous/useful) suggestions! Nearly all of them do provide insights on what each of you thinks is the most important thing about Codeberg in a sentence, which is very useful for us to know as well! 😄
(No matter if we came up with a tagline, adjusted one of yours or chose "the best one" as-is, we'd have to discuss amongst ourselves anyway. There won't be any changes on there for a while, but maybe elsewhere!)
Thanks for playing along, "Cody McCodeface" out! ~n
Replying to
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.
Replying to
Tip: A bunch of ideas we have gotten so far involve the themes "mountain"/"summit", "unlike the 'rest of the Internet'", "retreat", "iceberg", "cool"... there miiiight be something behind those, but we also welcome out-of-the-box suggestions. :)
Replying to
We appreciate all the love and support we receive from you, thank you so much.
However, the sad story is, that this day was a massive disruption for most people who develop software on a serious level on Codeberg, from large Free/libre software projects to companies and freelancers, and we are sorry about this.
We acknowledge if this makes you want to move elsewhere, but we're of course happy about everyone who can stay ❤️.
Replying to
We have finally reached a somewhat stable level of operation. In the past hours, we managed to partially restore service, but mostly managed to do so only for a subset of our users (due to DNS propagation delays and IPv6 vs IPv4 connectivity differences).
Currentely, Codeberg is available for all the situations we monitor for, and we expect that most connectivity issues will be resolved soon after all DNS caches clear.
Replying to
Bad news: DDoS has followed to the new location.
Good news: There, we have at least basic DDoS protection.
Bad news: The server is still unreachable.
We have received first numbers. The DDoS is apparently about 11Gbit/s over UDP traffic currently.
Boosted by @fedicat@pc.cafe
As we have gotten a number of inquiries due to confusions about this: Following our annual member assembly, we have indeed sent out emails for voting on its proposals. But only to those who have an active e. V. membership. If you are a ‘supporting’ member of Codeberg e. V., you do not have active voting rights.
If you are looking for a low-traffic way to stay up to date about changes to our services: We created https://codeberg.org/Codeberg/changelog/ to document significant changes to our services in one place. You can "watch" issues that are important to you, to get targeted notifications.
We also use our second account @codebergstatus@social.anoxinon.de to keep you up to date about downtime and incidents.
@alice@lgbtqia.space @jaz@toot.wales It's been forwarded to the moderation team ~g
Replying to
We were still struggling with email delivery from Forgejo. It looks like some queues are corrupted and restoring them is very hard. Most queued messages are spam or registration emails with already expired tokens. Finally, we made the decision to reset the queue and will do that in a few minutes.
We are using the opportunity to switch the queues to #redict / #redis, which was a planned project anyway (a requirement for clustering our Forgejo to multiple instances).
Replying to
@thesamesam@social.treehouse.systems Unfortunately, I'm not sure if encouraging anyone to reinforce the vendor-lock-in of Microsoft GitHub by making maintainers financially dependent on that platform, is in spirit with our mission. ~f
Replying to
🔔 Heads-Up: Notification emails generated today won't be sent. If you require someone's attention, please ping them again. If you tried to register, please sign in and re-send your activation email (or re-register your account in case it was pruned due to the pending activation).
Replying to
@Suiseiseki@freesoftwareextremist.com Anubis is the option that saved us a lot of work over the past months. We are not happy about it being open core or using GitHub sponsors, but we acknowledge the position from the maintainer: https://codeberg.org/forgejo/discussions/issues/319#issuecomment-6382369
Calling our usage of anubis an attack on our users is far-fetched. But feel free to move elsewhere, or host an alternative without resorting to extreme measures. We're happy to see working proof that any other protection can be scaled up to the level of Codeberg. ~f
Replying to
@organicmaps A lot of people seem to suggest you to move to an instance of Forgejo or even Codeberg. We hope you are not overwhelmed or annoyed by this, and wish you all the best for returning back to work with your project ASAP.
If you indeed consider moving to #Forgejo or #Codeberg in the future, feel free to add your project to https://codeberg.org/forgejo-contrib/moving-to-forgejo/ and let us know if we can be of any assistance to you.
Replying to
@cadey@pony.social I'm sorry if this gave you any unwanted or negative attention. I consider crawlers emulating more of real browser features to bypass protections of websites an inevitable future, and today at least one big crawler seems to have started doing so. ~f
Replying to
@silverfish@yourwalls.today Well, using cloudflare would kinda mean giving up on all our ideals:
- no big corporate services, everything under our control
- privacy by default, but Cloudflare likes to decrypt traffic in the middle
- no proprietary dependencies, everything runs using free/libre software
However, we have currently used DDoS mitigation from a smaller provider that does not do man in the middle sniffing, so we only had to sacrifice partially using non-free software for a while. ~f
Replying to
@Suiseiseki@freesoftwareextremist.com BTW, we're also actively following the work around iocaine, e.g. https://come-from.mad-scientist.club/@algernon/statuses/01K2N54XEVTEYYAASHZ0P48FBT
However, as far as we can see, it does not sufficiently protect from crawling. As the bot armies successfully spread over many servers and addresses, damaging one of them doesn't prevent the next one from doing harmful requests, unfortunately. ~f
Replying to
@serebit@floss.social Of course we accept requests for when you are approaching it. But keep in mind that every request will likely be checked by a user, so please avoid creating support burden when you are unlikely to pass the threshold anyway.
Something like 60-80% reached might be sensible. ~f
Replying to
@lindesbs@mastodon.social 160 GB apparently. Looked it up from https://codeberg.org/Codeberg-Infrastructure/meta/src/branch/main/hardware/achtermann.md ~f
Replying to
@littledetritus@geraffel.social Sometimes yes, sometimes no. Our members come from different backgrounds and have different fields of interest/skillsets – we appreciate everyone that has something new to bring to the table. ~n
Replying to
@pierstoval@mastodon.social @codecat@meow.social Some of our volunteers upstream contributions to Forgejo (and we've commissioned others to do the same in the past), but, ultimately, we aren't in charge of choosing what is implemented/merged and what isn't. That's up to the Forgejo community. :)
With that being said, I think that at least some of these features would be desirable by the community and are worth making an issue over. Or, at the very least, an "awesome-forgejo" (the repository) entry. ~n
Replying to
@lenny@freespeech.chat If you read the thread, you'll notice that this is exactly what we did, except that we made a mistake. ~f
Replying to
@littledetritus@geraffel.social Thank you for joining! Now you can participate in all sorts of wonderful discussions, such as whether there should be a gap between the e. and the V. or not! ^^' ~n
Replying to
@bkuhn@fedi.copyleft.org @downey@floss.social Thanks for the testimonial, we really appreciate your support!
It does have an impact – we remember our stand at FOSDEM 2025 being overrun by cool and curious people visiting our stand after the shoutout we got from your colleagues during your talk. We hope to see you next year (nevertheless, I had a very pleasant discussion with Denver :D). ~n
Replying to
@angestoepselt vielleicht! bitte contact@codeberg.org anschreiben, wenn das einfach für euch ist :) ~n
Replying to
We have deployed Forgejo v16, read more about the new features that come with this release in their news article: https://forgejo.org/2026-07-release-v16-0/
Report any new bugs or regressions to https://codeberg.org/Codeberg/Community/
