You might have guessed it already: We are struggling with excessive crawling today. We have - again - blocked several large IP ranges, but were not yet able to identify the new actor.
We are working on restoring service availability and fine-tuning our rate-limiting.
If someone is interested in implementing an improved native rate-limiting in #Forgejo that also protects other instances from abusive crawlers, please reach out 😉
@Codeberg
Note that @fdroidorg can't build apps hosted on codeberg anymore due to this. Its buildserver clones the repo for each app and soon gets 429.
@grote
This is interesting feedback. There have been no changes to the rate-limiting, and the last two changes over the past three months were always increases.
We have blocked several offending IP ranges. Is there information about which hosting providers Fdroid uses?
@fdroidorg
@Codeberg @grote @fdroidorg where are production buildservers are located is not public information, and it is not necessarily static. But I imagine it would be easy to figure out which IP address by looking at the logs on the codeberg side. We haven't been blocked before by any other git/scm hoster, to my knowledge.
