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

Direct group messages aren't correctly handled #193

Closed
Ppjet6 opened this issue Jun 21, 2018 · 2 comments
Closed

Direct group messages aren't correctly handled #193

Ppjet6 opened this issue Jun 21, 2018 · 2 comments

Comments

@Ppjet6
Copy link

Ppjet6 commented Jun 21, 2018

Running matterircd 9b09123 and mattermost 4.8

There seems to be lots of issues with this kind of direct messages, I wonder if there is support even for them. I'll try to outline a few issues. I can split this if required.

Steps to reproduce

  • Via the webui, Direct Messages (+) > Select at least 2 users > Go
  • Send a message, via the webui
  • Get a participant to send a message to that group
  • Send a message via the bridge to the group

What happens

First issue, when I create the direct message tab, nothing happens on my IRC client.

Second, when I send the message to that tab via the webui, I get two windows created on my IRC client, one channel with all participants, and one private conversation with the channelid. Every subsequent messages sent by participants will appear as private conversations between me and that participant.
EDIT: when I send a message via the webui to that group, on the IRC side it appears in the channel under my nick, which is expected.

Third, from the IRC client, when I send a message in the newly created channel, it appears as:

16:27 < pep:7ntbwhjycjffmypj1jjreidpbe> foo

What I expect

I would expect these "direct group messages" to behave like normal channels, seen from the IRC side. I have no knowledge of the MM protocol and how that's handled though.

@42wim
Copy link
Owner

42wim commented Jun 27, 2018

Please update to the latest matterircd release, I think the issue you mention should be fixed in 0.18.1
See eg #178
If you still have this or other issues on 0.18.1 (or .2 release very soon), please reopen or create another issue

@42wim 42wim closed this as completed Jun 27, 2018
@Ppjet6
Copy link
Author

Ppjet6 commented Jun 28, 2018

I checked and we are running 0.18.2-dev, so I believe this fix is in.

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