Codeberg/Community
54
325
Fork
You've already forked Community
12

Better rate limiting #425

Open
opened 2021年04月07日 13:15:45 +02:00 by fnetX · 4 comments
Owner
Copy link

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)
Author
Owner
Copy link

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.
Author
Owner
Copy link

I just want to transfer some points from other issues / discussions:

Some people told about looking at Discourse and other forum software for slowly increasing limits with user experience / their amount of successful interactions ...

I'm not really a fan of this, since I have been hit by this multiple times: Joining a community, wanted to become active and - oops, you can't use this kind of feature or at least not that often ... please be careful with these kinds of algorithms!

I just want to transfer some points from other issues / discussions: Some people told about looking at Discourse and other forum software for slowly increasing limits with user experience / their amount of successful interactions ... I'm not really a fan of this, since I have been hit by this multiple times: Joining a community, wanted to become active and - oops, you can't use this kind of feature or at least not that often ... please be careful with these kinds of algorithms!

So what are the actual API rate limits right now? The top comment mentions "basic rate-limiting" but I couldn't find anything about that. I'm mostly interested in fetching information such as the release list using the gitea API (which by itself doesn't seem to have any rate limiting capabilities yet).

So what are the actual API rate limits right now? The top comment mentions "basic rate-limiting" but I couldn't find anything about that. I'm mostly interested in fetching information such as the release list using the gitea API (which by itself doesn't seem to have any rate limiting capabilities yet).
Author
Owner
Copy link

Currently: 2000 requests / 300s

https://codeberg.org/Codeberg-Infrastructure/scripted-configuration/src/branch/main/hosts/kampenwand/etc/haproxy/haproxy.cfg#L233-L235

Currently: 2000 requests / 300s https://codeberg.org/Codeberg-Infrastructure/scripted-configuration/src/branch/main/hosts/kampenwand/etc/haproxy/haproxy.cfg#L233-L235
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#425
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?