You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 24, 2021. It is now read-only.
This problem was observed in ircd-seven on FreeNode but it was recommended to bring it here.
If you (as a user/channel owner, not IRC oper) have a channel forward set up from some channel to another, via a +f in combination with a +i or widely-applying +b or whatever, then in most clients (by now anyway) you are forwarded without a problem. However if you happen to already be in the target channel, you are presented with an often-hostile message corresponding to the +i or +b or whatever mechanism you used to block access to the original channel.
For people who are not really familiar with IRC (and in fact for some who are), this behavior is pretty scary/off-putting. It would be nicer perhaps if the server always responded with the 470 "ERR_LINKCHANNEL" code in this case - or at the least, there should be a way to enable this behavior.
The text was updated successfully, but these errors were encountered:
This problem was observed in ircd-seven on FreeNode but it was recommended to bring it here.
If you (as a user/channel owner, not IRC oper) have a channel forward set up from some channel to another, via a +f in combination with a +i or widely-applying +b or whatever, then in most clients (by now anyway) you are forwarded without a problem. However if you happen to already be in the target channel, you are presented with an often-hostile message corresponding to the +i or +b or whatever mechanism you used to block access to the original channel.
For people who are not really familiar with IRC (and in fact for some who are), this behavior is pretty scary/off-putting. It would be nicer perhaps if the server always responded with the 470 "ERR_LINKCHANNEL" code in this case - or at the least, there should be a way to enable this behavior.
The text was updated successfully, but these errors were encountered: