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 Apr 19, 2022. It is now read-only.
My school decided to standardize on Slack and purchased an Enterprise Grid https://slack.com/resources/why-use-slack/slack-enterprise-grid subscription. Basically it lets you have multiple workspaces under one umbrella. A "benefit" (and I use the term very loosely here) is that your DMs are accessible and shared across every workspace, even if the other person isn't a member of that workspace.
I finally joined a second workspace on our grid and now any time someone DMs me I get two copies of it in Matrix from two different Matrix users (one routed from each workspace). It'd be great if there were some way for the bridge to recognize that the sender from the Slack side was identical and deduplicate it.
The text was updated successfully, but these errors were encountered:
My school decided to standardize on Slack and purchased an Enterprise Grid https://slack.com/resources/why-use-slack/slack-enterprise-grid subscription. Basically it lets you have multiple workspaces under one umbrella. A "benefit" (and I use the term very loosely here) is that your DMs are accessible and shared across every workspace, even if the other person isn't a member of that workspace.
I finally joined a second workspace on our grid and now any time someone DMs me I get two copies of it in Matrix from two different Matrix users (one routed from each workspace). It'd be great if there were some way for the bridge to recognize that the sender from the Slack side was identical and deduplicate it.
The text was updated successfully, but these errors were encountered: