#425 Better rate limiting

Open
opened 1 week ago by fnetX · 1 comments
fnetX commented 1 week ago
Collaborator

Currently, there is a very basic rate-limiting that is less ideal (does not prevent abuse, but limits it + normal users run into the limits (Moritz reported this + #241).

Let's track the progress here and give the matter some higher priority. We could also discuss and assign some funds to get this solved ...

Please also see these relevant Gitea feature requests:

Currently, there is a very basic rate-limiting that is less ideal (does not prevent abuse, but limits it + normal users run into the limits (Moritz reported this + #241). Let's track the progress here and give the matter some higher priority. We could also discuss and assign some funds to get this solved ... Please also see these relevant Gitea feature requests: - [#9559 - general rate limiting](https://github.com/go-gitea/gitea/issues/9559) - [#9847 - extended by 6543, user creation date](https://github.com/go-gitea/gitea/issues/9847)
fnetX added the
enhancement
label 1 week ago
fnetX added the
contribution welcome
label 1 week ago
fnetX added the
gitea-related
label 1 week ago
fnetX added the
upstream
label 1 week ago
fnetX commented 6 days ago
Poster
Collaborator

just note: #119 mentions an API protector that we might want to have a look at.

I ran into the rate limiting for the first time today and noticed that issue open / close actions are apparently not restricted at the moment, although they trigger the same amount of email + system notificatons.

just note: #119 mentions an API protector that we might want to have a look at. I ran into the rate limiting for the first time today and noticed that issue open / close actions are apparently not restricted at the moment, although they trigger the same amount of email + system notificatons.
Sign in to join this conversation.
Loading…
There is no content yet.