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 congrats, you missed a point big time
@phnt @codebergstatus also, this solution sucks
Replies
2
@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.