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

Slack display name does not update #1600

Closed
keenan-v1 opened this issue Oct 4, 2021 · 0 comments · Fixed by #1604
Closed

Slack display name does not update #1600

keenan-v1 opened this issue Oct 4, 2021 · 0 comments · Fixed by #1604
Labels

Comments

@keenan-v1
Copy link
Contributor

Describe the bug
Matterbridge does not seem to pick up on Slack display name changes without stopping and restarting.

To Reproduce
Set up a Slack <-> IRC gateway, chat once. Change your display name on Slack. Chat again.

Expected behavior
I expect it to pull the latest display name.

Screenshots/debug logs
If applicable, add screenshots to help explain your problem.
Use logs from running matterbridge -debug if possible.

Environment (please complete the following information):

  • OS: linux
  • Matterbridge version: 1.22.3 e45bbe4

Additional context
Please add your configuration file (be sure to exclude or anonymize private data (tokens/passwords))

[irc]
    [irc.rizon]
    Server="irc.rizon.net:6697"
    Nick="SlackBot"
    NickServNick="SlackBot"
    NickServePassword="MyPass"
    UseTLS=true
    SkipTLSVerify=false
    RunCommands=["PRIVMSG nickserv :IDENTIFY MyPass SlackBot"]
    RemoteNickFormat="<{NICK}> "

[slack]
    [slack.myslack]
    Token="xoxb-secrets"
    RemoteNickFormat="<{NICK}> "
    PrefixMessagesWithNick=true


[[gateway]]
name="mychan"
enable=true
    [[gateway.inout]]
    account="irc.rizon"
    channel="#mychan"
    options = { key="withkey" }

    [[gateway.inout]]
    account="slack.myslack"
    channel="mychan"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant