Failed to change nick: err_banonchan - Better UX

[anoadragon453]

Seems like there's already some history to this #475 #45

But essentially when you receive a err_banonchan, it apparently gives you the room that you've been banned/quieted in on IRC, but this is not given to the matrix user, leaving them lost and confused as to why they can't change their nick.

[ara4n]

It has it in the logs, but this is useless to the user:

2019-07-10 08:24:39 ERROR:client-connection Server: chat.freenode.net (Matthew[m]) Error: {"prefix":"wolfe.freenode.net","server":"wolfe.freenode.net","comm
and":"err_banonchan","rawCommand":"435","commandType":"error","args":["Matthew[m]","Arathorn","#guardianproject","Cannot change nickname while banned/quiete
d on channel"]}
2019-07-10 08:24:39 ERROR:BridgedClient <Matthew[m]@chat.freenode.net#cu40i3xvjww00> (@matthew:matrix.org) Nick change error : err_banonchan

[ndarilek]

How do you figure this is useless to the user? If I knew which room(s) threw this error, couldn't I leave the individual rooms when changing nicks vs. having to leave and rejoin a dozen or so channels just to find which is causing the issue?

I'm hitting this now and don't know what to do. Somehow my nick became unregistered. I'm now registering a new one, but I can't !nick to it because some channel is blocking me. If the answer is that I have to leave all of my channels to fix this, I'll probably just stop using Matrix as an IRC bouncer since that feels a bit user-hostile.

Thanks.

[emorrp1]

It's useless to the user, because that's the bridge server's logs, but yes would be good if the bridgebot included which room was affected. I only had a dozen freenode rooms, so just !quit and started again, but for anyone else coming across this, the linked issue says to re-login manually with NickServ first:

the instructions to login with NickServ before trying to change the visible nick, that did the trick.