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
1
@codebergstatus Shouldn't have drama forked Gitea, otherwise you would already have some of the tools for that.
image.png
image.png
Replies
9
@phnt @codebergstatus congrats, you missed a point big time
@phnt @codebergstatus also, this solution sucks
@tragivictoria @codebergstatus I know the point, I've been trying to keep my forge running on the same box as this instance in a usable state as well for 2 years without being too much intrusive about it. I know the issues and problems associated with it.
My point is that if Codeberg didn't fuel dumb drama and fears years ago, they would be in a better position to fix their current issues than what they currently have.
>also, this solution sucks
I know that it's not the greatest implementation. It's more of a band-aid solution than anything else. Still better than a full on/off switch and a better start than an on/off switch.
My point is that if Codeberg didn't fuel dumb drama and fears years ago, they would be in a better position to fix their current issues than what they currently have.
>also, this solution sucks
I know that it's not the greatest implementation. It's more of a band-aid solution than anything else. Still better than a full on/off switch and a better start than an on/off switch.
@phnt @tragivictoria @codebergstatus i did something similar for git.pleroma.social with caddy setting and checking cookies, works alright. traffic was indeed unusably bad before.
@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 @codebergstatus Gitea has a third option in the same setting that requires authentication only for some of the more expensive routes that usually cause issues. That's the difference between the two.
>but the goal of Codeberg is to be a public forge, where stuff can be published !
If they are getting flooded, which they are for at least two years now, it's better to hide certain things to anonymous users than bring the whole service down altogether with scraping. Things like blame that are expensive and rarely used legitimately.
>but the goal of Codeberg is to be a public forge, where stuff can be published !
If they are getting flooded, which they are for at least two years now, it's better to hide certain things to anonymous users than bring the whole service down altogether with scraping. Things like blame that are expensive and rarely used legitimately.
@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)
@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.