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

Dear #GitHub users, if you prefer the orange-themed heatmap for #halloween and would like to see it all year long: feel invited to move to #Forgejo or #Codeberg (and choosing a forgejo theme in the appearance settings). It's the default colour here.

Hi! We "upgraded" our primary @matrix chat, (#codeberg.org:matrix.org) to room version 10. Upgrades are a part of the Matrix protocol: They create a new room in the place of the old one, and send invites to everyone in the old room. If you were in the old room, you should have received an invite.

We had 1588 members, but it seems like we only sent ~1180 invites. If you were a member of the chat, please accept the invite! If you haven't received one, please let us know!

https://matrix.to/#/#codeberg-space:matrix.org

In the meantime, you could join our Matrix space and our Matrix room (#codeberg-space:matrix.org and #Codeberg.org:matrix.org respectively) again for real-time discussions with others in the same boat.

Completely optional, of course. ~n

Hi. Yes, we have a full outage right now (https://status.codeberg.eu).

This acknowledgment comes from the social media manager that _isn't_ a system administrator. I can't share more details right now, so all I have to say is the following for now: It has been a weird and challenging week, sorry for the inconvenience. ~n

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

#trainstory

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

@s_levi_s Codeberg is running a single server (~130W) on renewable energy. We know that we can reach more efficiency, mostly because we don't benefit from scaling effects yet.

The difference is more like this:
- we do not encourage users to use more resources, because it would cost us more. Most competitors do the opposite (e.g. recommending the use of heavy CI pipelines), simply because it makes more revenue
- we do not spend any computing power on tracking and unnecessary data collection

If Codeberg is trying to "compete" against GitHub and GitLab, why does it refuse to take a look at AI assistants? Apart from infringing on authors' rights and questionable output quality, we think that the current hype wave led by major companies will leave a climate disaster in its wake: https://disconnect.blog/generative-ai-is-a-climate-disaster/

Other _sustainable_ (and cheaper!) ways for increasing efficiency in software development exist: In-project communication, powerful automation pipelines and reducing boilerplate.

The #Forgejo maintainers are preparing for the next release - v8.0. Thank you so much for the effort you spend, we are excited to deploy the improvements for the benefit of our users.

Part of the work in Forgejo is paid for by Codeberg, thanks to the financial support of our non-profit members and voluntary donations.

Learn how you can chip in your money to liberate code hosting: https://docs.codeberg.org/improving-codeberg/donate/

#GiveUpGithub #BreakMonopoly

@aral Pretty recent, but #codey is starting something like this: https://codey.ch/

Hi guys, our email server was locked by the provider due to "abuse" it seems. We're working on it, please be patient.

Email delivery is currently unavailable.

Okay, the whole story, according to our research:
In Dec 2023, an " IT professional" joined Codeberg with a valid email address. In the meantime, they apparently changed something with their server, because the email address is no longer available.
They are also a very active contributor to abuseipdb.com, reporting every server which sends mail to nonexistent email addresses on their personal server to.
This report triggered the abuse department of our ISP to take down our server.
Thank you!

Hi everyone! New person managing the social media account here – many of us were at the #GPN22 in Karlsruhe and, this time around, there were many that were interested (or even involved in!) alternative forges for themselves or their hackspaces and, well, Codeberg?!

I even talked to a person in a train that later turned out to be a Forgejo contributor (the person next to them was a Codeberg e.V. member). We all met up!

So long Karlsruhe, and thanks for all the fish! 💙

📸 (credit in alt text)

We investigated performance degradation due to excessive crawling of Codeberg.

We often trace back such things to company websites that proudly list their key investors - but don't actually explain what they are doing (or why they need to crawl Codeberg more excessively than the crawlers of the major search engines combined).

It's probably not a use case we believe in anyway, so we blocked several large IP ranges today.

Introducing some of the new #Forgejo features now available on Codeberg (the thread will be extended over the next days):

You can now set your pronouns in your user settings, and they will display on your profile.

If you link to code in an issue, these will now show up as a preview, see https://codeberg.org/forgejo/forgejo/issues/3525 for example.

With #Forgejo v7, there is now experimental code search support. It is currently only available to logged-in users and up to a certain repo size for performance reasons.

Results are generated with git-grep on the fly. We are working on integration with an external search index and also making progress there, but it will take some more time until this is ready.

If you visit the activity pages of your repository, you can now find much more information an graphs, like a list of contributors and code frequency.

If you prefer to use the #Sourcehut #CI, you can now select the dedicated sourcehut integration in your repo webhooks settings (see https://forgejo.org/docs/v7.0/user/webhooks/).

One of the oldest feature requests of Codeberg is finally addressed: You can allow any user on the instance to edit the wiki, not only collaborators. See https://forgejo.org/docs/v7.0/user/wiki/#activation-and-permissions for details.

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.