New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit the number of community members #14532
Comments
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Apr 30, 2024
jrainville
added a commit
to status-im/status-go
that referenced
this issue
May 1, 2024
…equests (#5105) * feat(community): limit nb of requests to join and members Needed for status-im/status-desktop#14532 * chore: simplify TestRequestAccessAgain * chore: add a test for the member limit
jrainville
added a commit
to status-im/status-go
that referenced
this issue
May 1, 2024
…equests * feat(community): limit nb of requests to join and members Needed for status-im/status-desktop#14532 * chore: simplify TestRequestAccessAgain * chore: add a test for the member limit
jrainville
added a commit
to status-im/status-go
that referenced
this issue
May 1, 2024
…equests (#5107) * feat(community): limit nb of requests to join and members Needed for status-im/status-desktop#14532 * chore: simplify TestRequestAccessAgain * chore: add a test for the member limit
jrainville
added a commit
that referenced
this issue
May 1, 2024
jrainville
added a commit
that referenced
this issue
May 1, 2024
Fixed in #14566 and status-im/status-go#5105 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
To make sure the app stays performant, we will set a hard cap on the number of community members.
That cap needs to be editable relatively easily so that if everything goes well, we can increase it for example.
There are two possible options, from hardest to easiest:
Do not reject it, just ignore it, that way it stays pending for the user and it will expire and they can send it again later (if the limit is increased)
The text was updated successfully, but these errors were encountered: