We are struggling to keep Codebreg.org available for unauthenticated users due to massive abuse of expensive endpoints.
Our current priority is keeping Codeberg.org responsive for authenticated users.
Timeline
Post
Remote status
Context
3
@codebergstatus Shouldn't have drama forked Gitea, otherwise you would already have some of the tools for that.
image.png
image.png
@phnt @codebergstatus I have that setting on my ForgeJo instance, pretty sure Codeberg has it in their toolbox, but the goal of Codeberg is to be a public forge, where stuff can be published !
@Sobex @phnt @codebergstatus
> but the goal of Codeberg is to be a public forge, where stuff can be published !
Then they need to put on their big boy pants and buy some more compute and bandwidth and also build a CDN. They're trying to be something on the public internet that they clearly cannot afford to be and they don't have the skills and money to build the infra they need.
(I'm still laughing about their Postgres corruption fiasco)
> but the goal of Codeberg is to be a public forge, where stuff can be published !
Then they need to put on their big boy pants and buy some more compute and bandwidth and also build a CDN. They're trying to be something on the public internet that they clearly cannot afford to be and they don't have the skills and money to build the infra they need.
(I'm still laughing about their Postgres corruption fiasco)
Replies
2
@feld @codebergstatus @Sobex I mean it's a nonprofit ran almost exclusively by volunteers. Can't really blame them at that point. The community around them is the bigger issue I think. Building a foss equivalent of GitHub simply isn't possible now, so instead of most foss people saying "migrate to Codeberg from Git{lab,hub}", it should be "run your own if you can" instead.