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

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.

Are you an #admin of a #Forgejo instance? What challenges do you face 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!

We are currently having network issues. We are able to connect to our server's onboard recovery system, but the access is slow and unreliable.

We'll keep you updated.

A quick glimpse at the monitoring (until network access went away) indicated that it's either a grave network misconfiguration or an active DDoS going on. It looked like an inrush of junk data at the maximum link speed of our server.

We are waiting for our provider to help us out with our current situation.

Our provider confirmed an incoming DDoS. We have got access to our systems and currently considering next steps.

Hi all, our server is currently unreachable, not even via VPN and the network of our provider does not respond to pings, too.

Drink something, test your work again, and push it once we're back online 🧉

#Codeberg suffers from high load, and #Forgejo / #Gitea does not scale very well. We identify bottlenecks from time to time, but it's hard to stay ahead.

If your project does not need to be on Codeberg, consider using https://next.forgejo.org instead.

- it runs on the same hardware and stack managed by Codeberg
- it has better performance
- dogfooding this instance helps the Forgejo developers (please report problems as you encounter them)
- it reduces the load on Codeberg

Read on …

A small but notable change on Codeberg? References to #Twitter are now gone.

We believe in independent networks. Drop #GitHub, drop #Twitter, drop all the #proprietary clouds and embrace true freedom.

Codeberg is currently being hit by increased spam, we removed hundreds of spam users and thousands of spam repositories in the past day.

If your issue tracker receives spam issues, please

- create a comment mentioning @moderation and the spammer username in the issue
- or email us to abuse@codeberg.org if you prefer
- you can optionally delete the issue, but please ensure we have the username of the spammer available (e.g. via the mention above)

Thank you.

Hi folks, we are sorry, but this downtime could last a moment. It looks like one of our root SSDs failed. While the RAID seems to work, the performance has dropped to a level where the whole service is impacted, and even our shell on that server is near to unresponsive.

We're back for now. We'll try to keep everything running until we are able to install the spare hardware.

We'll have another downtime. We want to fix some things before the CEST-evening with the highest traffic amount starts.

Our root SSDs are dying, probably because of a firmware bug. We'll try to update the firmware now.

Firmware update succeeded, everything looks OK for now. We'll monitor, but expect Codeberg to stay online for the time being.

We'll have another scheduled downtime once the replacement SSDs arrive.

Because recently some folks at Codeberg mistake their "Freedom of Speech" for the opportunity to insult other users on our platform:

Codeberg is a place to create content, not to disturb each other. We do not want to see discrimination of any kind.

Please report these cases to abuse@codeberg.org via email, or (new!) mention "@moderation" in the Codeberg Issue to quickly notify us of a conversation we should look for.

Contributing to Codeberg: If you can't continuously contribute to Codeberg, but have a lot of experience, e.g. with #Ceph, #Haproxy, #LXC, #Linux and #Networking etc, please bookmark and occasionally check https://codeberg.org/Codeberg-Infrastructure/techstack-support for open issues and questions.

This way, you can share your knowledge without committing sustained energy to the project.

PS: We are also looking for people to manage discussions and ensure the results are summarized and communicated back.

We're having immediate hardware maintenance, should be back online shortly.

@fariszr Not anti-cloud maybe, but anti-monopoly. And it's difficult to find cloud hosting without.

Also, a while back, money was among our worst fears, so we calculated that self-hosting is more economic for large storage scale than using the cloud (we had netcup and Hetzner where we have been before). We expected volunteer contributions to grow accordingly.

Last but not least, OVH might be low-cost, but is of rather low quality in certain domains.

The hardest #scaling issue: https://blog.codeberg.org/the-hardest-scaling-issue.html

Some thoughts about how non-profit web services can have healthy growth and keeping up with proprietary competitors.

s/Gitea/Forgejo: Although we need to get used to it, we’re happy that we can support the #Gitea soft-fork #Forgejo by our means.
It will remain independent of for-profit companies and is guaranteed to remain 100% free/libre forever.

Read more on our blog: https://blog.codeberg.org/codeberg-launches-forgejo.html

Or Visit https://forgejo.org