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 @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.
Replies
0Fetching replies…