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

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 🚀

We are going to deploy storage limits on Codeberg. Here is what you need to know: https://blog.codeberg.org/new-storage-limits-on-codeberg-what-you-need-to-know.html

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.

You can read more about the release on https://forgejo.org/2025-04-release-v11-0/

@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.

@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 Because Redis it is no longer free/libre software. See https://github.com/redis/redis/blob/unstable/LICENSE.txt

@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

Codeberg is going down for scheduled database maintenance. Please enjoy your break.
We expect to be back in a few minutes.

✅ Done: Migration from #Redis to #Redict for caches
⏳ In Progress: Migration from MariaDB to Galera Cluster

Hi everyone, for several hours we are currently fighting with potentially malicious crawling. We are seeing distributed access on Codeberg that could have been crawling, however it seems to only use the most expensive routes. And each time we block an access pattern, a new one pops up immediately.

We are doing our best to keep the performance up.

We have found a solution together with @as9136 that will likely provide sufficient protection for IPv4 users, and we have a good idea how a long-term setup can look like (but it will take a while to get there). Thanks a lot for all the networking and support!

The switch is awaiting DNS propagation (pending for > 30 minutes already, and might take another hour for some users. And indeed, we are not happy with the service quality of #namesilo).

@zeh
Thank you for the offer, and the service sounds really interesting as an alternative to Cloudflare, especially for smaller-scale websites.
Unfortunately, having a third-party decrypt traffic to Codeberg is currently a no-go and it looks like their service mostly relies on that.

However, we are receiving some help setting up network-level DDoS protection and more is in preparation, so we're confident we'll find an alternative soon.
@silverfish

@silverfish 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