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

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.

#Codeberg needs you: Your trust, your donation and your time (you decide how much love you can give, though 💙)

Check out our teams on the Contributing Page: https://codeberg.org/Codeberg/Contributing

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.

Forgejo v7.0 was released (see post above!).

It will take a while until the new features reach Codeberg, but we're in the preparations.

Also join the release party this Saturday, 27 April 12.00 UTC, and get to know the team: https://codeberg.codeberg.page/Events/events/2024/04-27-forgejo-event/

#CommunitySpotlight are you an #XMPP user?

Make sure to check out #Conversations https://codeberg.org/iNPUTmice/Conversations on #Codeberg!

Hi everyone, we are doing user research for #Forgejo, the software that powers #Codeberg.

If you have 30 minutes in the next week, consider participating in the interviews to help us get insights in how you interact with Codeberg and how we can improve the experience for you.

https://cloud.splvs.net/apps/calendar/appointment/MiRtBJ5rYdT4

If you think of your abandoned hobby projects, what was your best idea? Do you wish to see something similar created by someone else?

If there was malicious code in a legitimate project hosted on #codeberg, would we remove access to it, including for security researchers?

Short: No!

We are considering how to prevent fetching malicious code by accident, though.

In any case, we are open to collaborating with security researchers. Interested? Help us build a malware hunting team: https://codeberg.org/Codeberg/Contributing/issues/44

Background: #GitHub locked access to source code of xz, which was background of active investigation from the community.

To people looking for an archive of the XZ code, you might want to check out https://tukaani.org/xz-backdoor/ which links to https://git.tukaani.org/. GitHub is not the only source of truth, although meta information about the Pull Requests is locked in to this silo.

The maintenance succeeded. We are all back for now.

Making use of the faster storage will require Ceph maintenance / balancing, which we will do later tonight when traffic is lower.

Thank you for your patience, and good luck with your current work!

We are entering phase 2: We are shutting down the machine for hardware maintenance.

We apologize for the inconvenience. Next time we boot up, you'll see more RAM and faster storage!

We have introduced phase 1b: We are shutting down some services, because root filesystem maintenance is too slow while Codeberg is still under heavy use. We want to finish maintenance today, so we decided to stop Forgejo.

Maintenance phase 1 is starting: Expect degraded performance (databases, Weblate, ...)

We will be having scheduled downtime today around 18.00 CET (17.00 UTC).

Read all about it: https://status.codeberg.eu/status/codeberg