Skip to content
This repository has been archived by the owner on Jun 24, 2021. It is now read-only.

Join forwarding can appear very unfriendly in certain cases #55

Closed
dmlloyd opened this issue Feb 25, 2014 · 2 comments
Closed

Join forwarding can appear very unfriendly in certain cases #55

dmlloyd opened this issue Feb 25, 2014 · 2 comments
Milestone

Comments

@dmlloyd
Copy link

dmlloyd commented Feb 25, 2014

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.

@jillest
Copy link
Contributor

jillest commented Mar 9, 2014

I agree that the current behaviour is suboptimal.

@kaniini
Copy link
Contributor

kaniini commented Dec 11, 2015

i agree with the change but don't really know of a good way to do it cleanly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants