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

Codeberg's performance is currently degraded. We are working on a fix.

We performed an experiment with our storage settings (testing Ceph's resiliency) and did not expect that undoing the action takes x100 the time to do the change.

There is one thing that annoys me about #Codeberg, but I was too lazy to tell …

… until today! Please let us know in the comments.

Do you thank everyone who makes your software project a success?

Take the time today and explicitly send appreciations to those who don't send you code patches, but help with #design, #localization, user support, defining priorities, community management and so much more!

#NonCodeContributions #FreeSoftware

@niku Well, seriously, please consider if there is really a need to mirror #yuzu several times on Codeberg. At a certain point, this is just a waste of storage.

Whatever happens, there are probably enough copies in the world and nothing will be lost. No need to +1 to that, better check if there are already mirrors , first.

Is the recent #Fediverse #spam wave over? We hope so. Thanks to all #instanceAdmins for cleaning this up.

What can we learn from this? Some thoughts regarding #ForgeFederation: https://blog.codeberg.org/what-we-can-learn-from-the-fediverse-spam-for-codeberg.html

#ForgeFed #Forgejo

What do we say to users who upload gigabytes of apparently random data, naming the files "500M.bin, 1000M.bin ..., 8000M.bin"

"Thank you for being an awesome member of our community"? Better proposals welcome.

We are excited about @forgejo becoming a hard fork, and trust the maintainers to double down on their commitment to a secure and reliable software forge. It was a pleasure to work with #Forgejo in the past year, and we thank everyone involved for turning the fork into a successful project.

Help us fund human resources!

#Codeberg would not be here without all the free time volunteers donate to our platform and to upstream projects. However, we can give our project a rocket boost with your help. We have compensated a small share of time for their work in #Forgejo, and we have seen immense progress we would waited long for.

With your help, we can continue going.

Donate to Codeberg: https://docs.codeberg.org/improving-codeberg/#donate-to-codeberg

Learn about our effort to sustain human workforce: https://blog.codeberg.org/letter-from-codeberg-looking-into-the-new-year.html

Can you help #translate #Codeberg's user interface into more languages? Consider joining the #localization team of #Forgejo and review or provide translations for your native language.

Learn more: https://forgejo.org/docs/latest/developer/localization/#joining-the-localization-team

@suruatoel We know of many users who migrated from #Gitea to #Forgejo. We never heard of anyone switching back (correct us if you know someone, would be interesting to learn why).

I think this is a sign, and we believe there is all reason to switch and not look back.

@excds Year of the Linux train, maybe? We've recently seen some kernel boot messages on regional train screens :)

GNU/Linux Debian 10 actually.

We are sitting in the #train to #FOSDEM. Wow, so many #Linux desktops in a public space!

#FreeSoftware #GNU #FOSDEM24

Looking into the new Year: Our latest newsletter was sent to members of our non-profit association and published on our blog:
https://blog.codeberg.org/letter-from-codeberg-looking-into-the-new-year.html

Learn about our efforts to sustain human workforce in our Free Software project, and consider helping achieve this goal with your donation!

From our latest #CommunitySpotlight:

Check out faircamp by @freebliss
https://codeberg.org/simonrepp/faircamp a static site generator for music producers that allows them to get independent of proprietary distributor networks.

Packed with a nice design and all features you'd expect, #faircamp is already trusted by numerous music producers and artists.

Read more about this and other projects on our blog: https://blog.codeberg.org/letter-from-codeberg-looking-into-the-new-year.html

#CommunitySpotlight from our recent blog post https://blog.codeberg.org/letter-from-codeberg-looking-into-the-new-year.html:

What to do with things you do no longer need? Do you want to avoid using #eBay?

Check out the self-hosted flohmarkt (German for flea market) for the job, an ActivityPub-based federated small trade platform. With the active development being less than a year old, you should expect some unfinished touches, though, but it's ready to give it a try!

All the best to the contributors!

Are you an #admin of a #Forgejo instance? What challenges do you deal in terms of #moderation or #spam?

We are caring about your experiences and looking forward to your input in https://codeberg.org/forgejo/discussions/issues/107 to decide how Forgejo can be improved to make life easier for you (and us).

Thank you for spreading the word!

Friendly Reminder to #2FA users: Imagine your primary machine fails today. How will you restore your access to your online accounts?

Please ensure you saved your scratch token somewhere and have working backups of your TOTP app or a backup hardware key.

Thank you!
#Backup

SSH is also back. We expect overall performance to be rather low, though.

Looks like some of you are already back. (At least the regular spam is, too)

Just for clarification: Due to our current networking constraints, there are no webhooks and email notifications at this time.

We are optimistic to have a plan to restore services early afternoon (European time).

We are also looking forward to restoring the Codeberg logo (it is currently missing in some places 😂)

For your convenience, we have temporarily established a way to access Codeberg. This is heavily constrained and might go back offline at any time.

mostly working:
codeberg.org HTTPS (Read/Write)

not working:
SSH, CI, Weblate, Pages and all the rest.