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
@*@example.com: block the entire example.com instance (should it also block all subdomains for safety?)
The blocklist is stored in the database, and is not publicly available to prevent malicious listing on public blocklists (see conversation on https://github.com/sgrigson/oliphant/issues/8).
The text was updated successfully, but these errors were encountered:
Add configuration features to block users.
When a blocked user tries to reach the instance, the request is rejected with a 403 Forbidden response.
Note: users should be able to also block entire servers too with a
*
wildcard.Examples of syntaxes:
@[email protected]
: block that user@*@example.com
: block the entireexample.com
instance (should it also block all subdomains for safety?)The blocklist is stored in the database, and is not publicly available to prevent malicious listing on public blocklists (see conversation on https://github.com/sgrigson/oliphant/issues/8).
The text was updated successfully, but these errors were encountered: