Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

public vs private "groups" (channels) #217

Open
qriff opened this issue Nov 2, 2017 · 1 comment
Open

public vs private "groups" (channels) #217

qriff opened this issue Nov 2, 2017 · 1 comment

Comments

@qriff
Copy link

qriff commented Nov 2, 2017

As a realization from copy/pasting channel mappings:

There would appear to be a bug when mapping (in config.json file) a public slack channel (vs private) without the hash prefix (to a irc channel), the relay becomes one way (irc to slack, not slack to irc, so basically part of it still works).

Bug (messages relayed only from irc-channel-second to slack-public):

    "channelMapping": {
      "slack-private": "#irc-channel-first",
      "slack-public": "#irc-channel-second"
    }

Working (messages relayed both ways between slack-public and #irc-channel-second):

    "channelMapping": {
      "slack-private": "#irc-channel-first",
      "#slack-public": "#irc-channel-second"
    }
@ekmartin
Copy link
Owner

ekmartin commented Nov 2, 2017

The second example is correct - look at the example configuration here: https://github.com/ekmartin/slack-irc#example-configuration

Channel/group names are unique in Slack though, so I'd definitely be open to change it so that it works both with and without #. It would need to be done in a backwards compatible manner though.

One way it could be done would be to remove # from all Slack channel names on startup, which could be done here. Then this variable could be removed altogether, in favor of just using channel.name.

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

No branches or pull requests

2 participants