ircv3-ideas
ircv3-ideas copied to clipboard
ircv3
A numeric, error string, or other normalization to indicate that the user is no longer welcome on a network.
There should be something normalized for providers (irccloud, bouncer providers, etc.) to determine an user is no longer welcome on the network (gline, kline, whatever) so that it can be gracefully handled and the administrators can log or deny access to reconnection to that network of sorts.
At the moment we (irccloud) already prevent auto reconnect when certain strings are matched (kline, banned, etc) and it's an unexpected disconnect. But, these often get triggered by networks by mistake with an overly broad ban mask, so we might stop doing this in future to prevent people being disconnected for longer than is needed after the mistake is reversed. At the moment we have to manually go in and reconnect them en masse. The same would hold if there was a numeric, so I'm not sure it would be that helpful in practice.
Just to document for the future;
A numeric (465) already seems to exist, but this idea is more to indicate to the client a "Please don't try to reconnect" without introducing the "we are bad opers and kline large ranges for no reason". A way to stop the ipv4 reconnecting to accidentally evade an ipv6 ban or vice versa.
Currently this is not happening, nor do we have a good means of preventing this,
Different admins on all different networks expect all different types of bans to mean "please don't come back", adding another one to the mix would complicated things further imo. Akills, klines, glines, and so on. Some even go as far as having their own specialised bots killing users on sight as a form of akill to mean the same thing.
just a random two cents, might it not be feasible to just immediately drop the connection with an ERROR instead of implementing a numeric?
The ERROR already does this, but ERRORs are very generic and nobody should really be parsing ERROR messages from the sixty different ircds we have laying around.
FYI: this is what RPL_YOUREBANNEDCREEP (465) is for.
now ircv3 reinvents rfc1459 from first principles. amazing!
Sending a 465 message does not properly relay the intent that they are banned from the remote side. Sure, it works if you're not using an intermediate server, but you could possibly get a client saying something similar to "Your network Bouncer has specified that you are currently banned", if implemented in a bouncer, which is not the intent desired here.
