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

@lynn We managed to break two of these server power supplies with a firmware update. And while searching for a fix, we have found videos demonstrating these very PSUs taking fire.

So ... you never know! ~f

@fossdd But they do not serve as a mobile heating at the same time. ~f

@programmerpony Thank you for your interest! You can request them for free with a Codeberg account by filing an issue here (we have a template for that): https://codeberg.org/Codeberg-e.V./requests ~n

@eliasp Actually, the same staff member checked our tickets about an hour later on the way back (without recognizing us), and asked me to "scroll" in the app to show it's actually "an app" and not just a screenshot.

Checking the connections in a café, thanks to Öffi!

#OeffiApp #de_schildbach_oeffi

To answer the initial question: This is what makes us nerds happy (in case you didn't expect an answer like this). An interesting experiment for us, too.

What this means in the long run for Codeberg? We're finally - thanks to the expertise and help of some volunteers - ready to expand our hardware infrastructure, making Codeberg more resilient to certain kinds of issues and improving availability in the long run.

@RedTechEngineer
It was mostly considered an experiment for us, but it worked better than expected. We'll probably improve protection of the machine, though, just in case. ~f
@sun

For those wondering why Codeberg is slow right now:

„GitHub took down the XX repository due to "Excessive Bandwidth Usage“.

Welcome to Codeberg. Feel free to move on.

But thank you for the stresstest.

@SM0RVV It's actually empty, but we might offer pickup service for large free software projects :)

What are we up to for today? What makes nerds get up early? Some journey ahead ...

#trainstory

Changing trains in Madeburg, having a snack, enjoying the sun.

Train staff didn't accept us presenting our digital ticket on ebook reader 🙄 - they are not allowed to scan arbitrary QR codes without "verifying where they are coming from".

Luckily enough, #PassAndroid was fine for them, because "some app" is apparently okay..

WiFi is working - and so are we.

A new piece of baggage has joined us. Makes for happy sysadmins - which you can see in the image when you look close enough.

Waiting for the train ... we have all we need for "holidays" 😉

(posted a little late, because the train had bad WiFi)

@iagondiscord The problem is that it's not targeting Codeberg. It's the #AIgoldrush. The web was completely crawled, just not by everyone yet. So startups start their #crawlers, carelessly and explicitly ignoring robots.txt to get the #biggestdata.

It does not matter if the web can no longer serve humanity due to this. Training the #AI is the only thing that matters.

Maybe a bit like a sacrifice for faith.

~f #goldrush

You might have guessed it already: We are struggling with excessive crawling today. We have - again - blocked several large IP ranges, but were not yet able to identify the new actor.

We are working on restoring service availability and fine-tuning our rate-limiting.

If someone is interested in implementing an improved native rate-limiting in #Forgejo that also protects other instances from abusive crawlers, please reach out 😉

One of your favorite alternatives to one of Microsoft's most popular products will probably change its name over the next 24 hours. We're super excited about it.

Stay tuned!

Do you enjoy making music and sounds, but you just don't feel like relying on Bandcamp anymore?

In that case, @freebliss's Faircamp is an excellent static site generator made just for you!

Free software, translatable, written in Rust. Perfectly suitable for your experimental noise rock album, your videogame's original soundtrack or your fire mixtape. 💥 (It is also very customizable!)

Codeberg: https://codeberg.org/simonrepp/faircamp
Web: https://simonrepp.com/faircamp

#CommunitySpotlight #FOSS #musicproduction

In a few minutes, Codeberg will suffer from several minutes of downtime due to necessary updates on our physical machine, affecting the reverse proxy.