-
Notifications
You must be signed in to change notification settings - Fork 80
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add implementation consideration about custom unprefixed modes
- Loading branch information
Showing
1 changed file
with
12 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,7 +13,7 @@ copyrights: | |
email: "[email protected]" | ||
- | ||
name: "Val Lorentz" | ||
period: "2021" | ||
period: "2021-2022" | ||
email: "[email protected]" | ||
|
||
--- | ||
|
@@ -365,3 +365,14 @@ This token MUST have an integer value greater than 0. | |
Servers should use this token to communicate to clients the maximum numbers of modes changes in a single PROP request. In the absence of this token or its value, they should assume it is 1. | ||
|
||
Clients MUST support receiving PROP updates with more changes than the value of `MAXMODES`. | ||
|
||
|
||
## Implementation considerations | ||
|
||
*This section is not normative* | ||
|
||
Servers implementing non-standard modes may allow clients to send them both with | ||
and without their vendor prefix. | ||
To avoid clashes with other implementations and future IRCv3 extensions, they | ||
should however avoid advertising (via `RPL_CHMODELIST`/`RPL_UMODELIST`) or | ||
sending them without the vendor prefix. |