Closed slingamn closed 5 years ago
This was deployed.
Strict nickname reservation sends 433 ERR_NICKNAMEINUSE
, which typically has the effect of causing the client to affix an underscore to the end of the nick. So this is actually less disruptive to clients than timeouts, but it illustrates the cultural challenges around making nicknames trustworthy (people will generally just assume that nickname_
is the same person as nickname
).
All current users with registered nicks, except for one, have SASL set up. Timeout-based reservation is an awkward stopgap. Let's make strict the default.
Tasks: