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

All done, apologies for the inconvenience.

We apologize for the interruptions we had today.

We are currently approaching a project to improve our overall infrastructure redundancy. Although we hit some major stopgaps today (including a bricked power supply), we are overall making progress and we have a good idea of what we can do within the next months.

Thanks to your financial support and our new employee, we will rework and improve our setup in the remaining months of 2024.

We accept donated hardware, including old servers.

Currently, we are in need of Dell R730 power supply units - in case someone has one to spare.

#ServiceToot: Codeberg's uptime is about 99.92% (two weeks average). Not perfect, but surely good enough for a donation-driven non-profit.

What do you think? ~f

#Forgejo 🧡 #UserResearch:

Especially if you are not yet using Forgejo or Codeberg, especially if you are not developing software at all (= everyone is much appreciated!):

We invite you to participate in interviews the next two days (Sun + Mon, August 25 + 26) to help the Forgejo developers learn about and improve the product to your needs.

Visit https://cloud.splvs.net/apps/calendar/appointment/cHr5MB2PoZDp to pick a time and date.

@s_levi_s Our original argument was that we should improve society somewhat. Yet we participate in it, however, that does not contradict what we say, even if we were not doing all of these things.

The problem with what you mentioned is that it is completely hypothetical (the article explains it), similarly to cryptocurrencies! And that even if it wasn't: Wasting hardware and AI scraping the entire Internet (not all of which is powered by renewable energy) 100 times is much less sustainable. ^n

@s_levi_s
- we do not live in a careless "enterprice" environment: We reuse failing server SSDs for our private use, we know that others regularly replace just as a precaution
- we do not spend excess resources on high availability, due to a simple 80/20 rule: 80% gain with 20% effort. We know we could add more spare servers, more sophisticated backups, replace hardware more often to avoid potential failures ... but we don't. It's a waste of resources (incl. our donations).

~f

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

@melroy They do, but the official instance is running the nonfree enterprise edition.

What's your favourite #FreeSoftware that is #NotOnGitHub (or on other proprietary code forges like #GitLab.com)?

Let us know in the comments! Feel free to also share code from other #Forgejo instances, #Sourcehut or other platforms.

#FreeLibreSoftware #LibreSoftware #Opensource #FLOSS #FOSS #GiveUpGithub #GitHub

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

@rimu Codeberg is overall stable because #Forgejo makes hosting quite easy. We are discovering some scaling issues (and fixed many in the past), but you probably don't have to worry about it if you don't plan to go beyond 10k users.

Running a public service means you have to deal with all kinds of abuse and growth pain over and over again. 2024 was not exactly a lucky year in this regard.

~f

@rimu For the record, the first years, Codeberg was pretty much hosted reliably on a single VPS for up to 10k users and it didn't require much attention.

The storage at scale and the Git operations performance (high random IOPS and managing all these small Git files, for example) and database performance are the main challenges infrastructure-wise at the moment.

@tisba Maybe check out https://docs.codeberg.org/getting-started/what-is-codeberg/#alternatives-to-codeberg

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

We're still waiting for a response from the abuse department about a potential unlock. We apologize for the inconvenience caused.

We have blogged about the problem when providers like @netcup (in our case) rely on blocklists as the single source of truth, without second thought or verification.

This caused much trouble and headache for us, but the person who put us on the list due to a config error will likely never know it happened, after all.

https://blog.codeberg.org/how-blocklists-prevent-the-internet-to-be-decentralized-and-safe.html

@netcup The issue is resolved with the help of our provider. Thanks for this and all your patience.

Most of the email was successfully delivered, only few remains in the queue.

In the responses to this thread, many users started to blame the IT admin who automatically put our IP address to the blocklist.

Please note that we don't want to blame a single party. Reporting spam and reacting to abuse reports is a good thing.

However, we are concerned about the fact that automation based on accusations from single parties escalates to regular headache for network operators.

This is also far from the utopy of an Internet, where everyone can easily host their own services.

Blocklists are not only community-maintained resources, but often charge for monitoring and removal services.

There is an imbalance between small and large operators, and the fact that many people suggested us to just use service from $$company$$ instead of self-hosting emails indicates the terrible situation.

We have written about our position in detail previously: https://blog.codeberg.org/how-blocklists-prevent-the-internet-to-be-decentralized-and-safe.html