Skip to content

Commit bdf2750

Browse files
authored
away-notify: Clarify away notifications should not be echoed (#531)
This matches every known server implementation.
1 parent fd20302 commit bdf2750

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

extensions/away-notify.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,9 @@ state, as well as when a user joins and has an away message set.
3030
(Note that AWAY will not be sent for joining users with no away
3131
message set.)
3232

33+
Clients SHOULD NOT be sent AWAY messages to notify them of their own away
34+
status (as they can rely on `RPL_NOWAWAY` and `RPL_UNAWAY`).
35+
3336
The format of the AWAY message is as follows:
3437

3538
:nick!user@host AWAY [:message]
@@ -46,3 +49,9 @@ To fully track the away state of users, clients should:
4649
state of all users in that channel.
4750

4851
3) Update state appropriately upon receiving an AWAY message.
52+
53+
## Erratum
54+
55+
The previous version of this specification did not explicitly say
56+
users should not get notifications of their own away status with AWAY.
57+
This was clarified in 2023

0 commit comments

Comments
 (0)