SASETNAME command

[prdes]

The ability to change an undesirable nick exists, this would essentially expand that to also allow OPERs to change realname i.e. setname but for OPERs suggested by @pilzgift ..

[slingamn]

It's an interesting suggestion but I don't anticipate doing this anytime soon. SANICK is useful in part because nicknames are a shared namespace, whereas realnames are not.

I don't see a clear use case for this in between "just ignore it" and "KILL/UBAN the user"?

[Mikaela]

I think KILL/UBAN can be a bit extreme especially if the user happens to be AFK and a potential scenario is clients like IRCCloud showing the real name next to every message or clients that support extended-join

[prdes]

It's an interesting suggestion but I don't anticipate doing this anytime soon. SANICK is useful in part because nicknames are a shared namespace, whereas realnames are not.

I don't see a clear use case for this in between "just ignore it" and "KILL/UBAN the user"?

There is a clearish soln to change realname it can even match if nick == realname use sanick for both but if you don't want it ill close this. I was planning to work on it

[slingamn]

I would accept a patch for this. It should be modeled after SETNAME but with a new command SASETNAME that takes the nickname as its first argument.