Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Add `account-required` cap value to `draft/account-registration` as per
discussion here:

ircv3/ircv3-ideas#73
  • Loading branch information
slingamn committed Mar 15, 2022
1 parent 53ec0cd commit dca0007
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions extensions/account-registration.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,9 @@ The only defined capability keys so far are:
to process
* `custom-account-name` - if present, the account name can be different
from the user's current nickname
* `account-required` - if present, indicates that the connection to the
server cannot be completed unless the client logs into an account with
SASL.

### Commands

Expand Down Expand Up @@ -261,6 +264,13 @@ like a `PRIVMSG` to NickServ), which are limited in length, clients may want to
prevent or discourage users from setting passwords so long they may not fit
in these messages. 300 bytes should be a safe reasonable limit.

The capability value `account-required` indicates that all connections require
SASL to proceed. The absence of this value does not indicate that connection
registration can necessarily proceed in the absence of SASL; it may be
disallowed due to specific properties of the connection (e.g. an untrustworthy
IP address), which will be indicated instead by `FAIL * ACCOUNT_REQUIRED`.
If the capability value `before-connect` is advertised, clients should respond
to both of these conditions by suggesting that the user register an account.

# Server considerations

Expand Down

0 comments on commit dca0007

Please sign in to comment.