You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 23, 2024. It is now read-only.
In case of high activity, a user could be subjected to a temporary ban. This makes sense in an open puzzle but could be a nuisance in a private instance.
My proposal is to allow for a setting to disable such check, either for the puzzle owner or for any and all potential contributors (in case of an unlisted instance, people entering through the direct link).
Ideally the implementation could either be in the form of a setting when creating the instance, or, probably safer, something that can be switched off also at runtime.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In case of high activity, a user could be subjected to a temporary ban. This makes sense in an open puzzle but could be a nuisance in a private instance.
My proposal is to allow for a setting to disable such check, either for the puzzle owner or for any and all potential contributors (in case of an unlisted instance, people entering through the direct link).
Ideally the implementation could either be in the form of a setting when creating the instance, or, probably safer, something that can be switched off also at runtime.
The text was updated successfully, but these errors were encountered: