Skip to content

Commit

Permalink
Add documentation for expermental NewJoinerProtection. (#26)
Browse files Browse the repository at this point in the history
  • Loading branch information
Gnuxie authored Jul 27, 2024
1 parent 01bedf4 commit 03e9d3e
Showing 1 changed file with 53 additions and 0 deletions.
53 changes: 53 additions & 0 deletions docs/protections/new-joiner-protection.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
sidebar_label: New Joiner Protection
---

<!--
SPDX-FileCopyrightText: 2024 Gnuxie <[email protected]>
SPDX-License-Identifier: CC-BY-SA-4.0
-->

# New Joiner Protection

:::danger

This is an experimental protection that should only be used as a last
resort when your community is under persistent attack.

This protection is unavailable in Draupnir version `2.0.0-beta.4` and
below.

This protection may be removed or changed entirely.

:::

This is a protection that can help when one of your rooms is coming
under a persistent attack from new joiners. Whether that be wave spam
or targeted attacked.

The protection works by banning new users from a set of configured
servers, leaving existing community members from the target servers
unaffected. The protection serves as an alternative to banning
the server outright.

## Configuration

To configure the protection, append the following under the
`protections:` header in your config file:

```yaml
newJoinerProtection:
serverNames:
- "example.com"
```
You will need to restart the bot to make this effective. We recommend
that you leave servers where abuse typically originates in the
configuration file. Then the protection can be enabled and disabled at
will without restarting the bot.
The ban message can also be changed with the option `banMessage:`.

By default this reads "Unfortunately we cannot accept new users from
your homeserver at this time.".

0 comments on commit 03e9d3e

Please sign in to comment.