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!
@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*.
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).
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.
To avoid disrupting your valuable work, we will be careful and start with very generous limits. Over time, we'll tune the configuration based on your feedback.
We also plan on helping you find and lower resource consumption, should you be shocked with the amount of storage you currently consume.
(By the way, we are aware of a bug that makes repo size count twice. It will get fixed soon)
Due to an increased inrush of spam, registrations are temporarily unavailable at Codeberg until the situation calms down. We apologize for the inconvenience.
We are going to update to Forgejo v11 tonight. We expect a brief interruption during the migration process. Our tests showed that everything should be back within a few minutes, though.
@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.
@mokazemi Redict is probably more "traditional", less features but it does the job we need it for (being a key-value-cache). Valkey is probably more modern and has more active development, but nothing that seems to matter to us. Redict is developed at Codeberg, where Valkey has been created on GitHub, that is part of the motivation for us. It allows contributions by people who use free software, whereas valkey contributors are required to use proprietary software.
@art_codesmith 1. It is not free software and breaks the mission of Codeberg. We promise to only run free/libre software and not business code crippleware. 2. It is unlikely that newer versions of Redis will be available in Debian GNU/Linux due to the changed software license, so we might need to migrate anyway sooner or later.
@art_codesmith There are no open source devs at the table when they choose to no longer publish under an open source software license. They are free to do that and we respect their decision. Please also respect our decision not to use that software any longer, if it is no longer free software.
There are many ways to monetize software. Turning free software into proprietary one is one such thing. But after that switch it is no longer free software. That's it, no need for euphemism. @phf
We are a non-profit, community-led organization that wants to help free and open source projects prosper. We provide Git hosting (using @forgejo) and other services, such as Weblate, Woodpecker CI and Pages.This account is managed by two volunteers that dedicate a few hours per week to social media. If we miss your message, please patiently try again (or take a look at https://docs.codeberg.org/contact instead).