matty/peertube-plugin-livechat
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Slow Mode XEP WIP (XEP-0143 compliance).

Browse Source
This commit is contained in:
John Livingston 2024-02-26 11:04:24 +01:00
parent 7c5b67ef99
commit 6bbea26da0
No known key found for this signature in database
GPG Key ID: B17B5640CE66CDBC
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
support/documentation/content/en/technical/slow_mode.md
View File

@ -161,7 +161,7 @@ If the slow mode duration has changed (either because the room configuration was
## 5. Server-side rate limiting
When the Slow Mode is enabled, server MUST NOT accept two consecutive messages from the same user, to the same room, until the slow mode duration has elapsed.
Only messages containing at least one `body` tag must be taking into account (to avoid counting `chatstate` messages for example).
Only messages containing at least one `<body/>` element must be taking into account (to avoid counting `chatstate` messages for example).
Room administrators and owners MUST NOT be rate limited.
@ -169,7 +169,7 @@ If a user bypass the limit, the server MUST reply an error stanza, that respects
* `error_type` MUST be `wait`, as described in [RFC 6120 - Stanzas error - Syntax](https://xmpp.org/rfcs/rfc6120.html#stanzas-error-syntax),
* `error_condition` MUST be `policy-violation`, as described in [RFC 6120 - Stanzas error - Defined Stream Error Conditions](https://xmpp.org/rfcs/rfc6120.html#stanzas-error-conditions),
* the stanza SHOULD contain a `text` tag explaining why the message was rejected, and this message SHOULD mention the slow mode duration so that user can understand why they can't post their message.
* the stanza SHOULD contain a `<text>` element explaining why the message was rejected, and this message SHOULD mention the slow mode duration so that user can understand why they can't post their message.
Here is an example or error stanza: