matrix-docker-ansible-deploy
matrix-docker-ansible-deploy copied to clipboard
spantaleev
Add matrix-bridge-mautrix-slack role
Also probably the role should be moved to roles/custom where the other roles live now after the last change
Thanks a ton @Zocker1999NET for the checklist, makes the migration a lot easier.
Unrelated to that change, were the slack puppets able to be created properly in your instance? I may have gotten configs messed up, it seems the bridge is only able to puppet my own account.
Unrelated to that change, were the slack puppets able to be created properly in your instance? I may have gotten configs messed up, it seems the bridge is only able to puppet my own account.
@xangelix sadly I have a very inactive Slack, so I couldn't test if messages from the puppets are bridged ... But I have problems with DMs not being bridged.
Do you think this works well enough to be merged now?
As for various problems with bridging.. I wonder if the bridge is fully-featured or stable enough for us to be recommending it over appservice-slack, etc.
As for various problems with bridging.. I wonder if the bridge is fully-featured or stable enough for us to be recommending it over appservice-slack, etc.
For what it's worth, this bridge appears to function without the need for a slack-side app/api. Several of the Slack workspaces I need to bridge with don't allow app/api access. That might make this bridge worth any warts it might have.
(Full disclosure, I'm very new to Matrix, but I've been watching this pull request because of that nuance regarding this Slack bridge vs the others)
I tried this on my personal instance, and so far, so good with the several slacks I bridged.
However, since this project moved to galaxy roles, some works have to be redone (I'd be happy to commit the modifications I did on this branch if you give me the access).
Also, there's a small "bug" of opening plenty of "Slack Bridge Bot" rooms... Not sure what it is about so far (bug or just threads? 🤷🤷🤷)
@RoiArthurB were the above changes mentioned by Zocker after moving to galaxy roles not all of the needed ones? also, did you test this role specifically, or the bridge?
@RoiArthurB were the above changes mentioned by Zocker after moving to galaxy roles not all of the needed ones?
Was enough, moving files and replace galaxy's project new variable (like the link to postgresql).
also, did you test this role specifically, or the bridge?
This role precisely in my matrix-docker-ansible-deploy instance :)
Only seems to bridge the logged-in user both ways, other users not working.
Not sure why getting these errors / what's wrong with the localpart:
Failed to send media message 2023-01-03 01:53:02.000469079 +0000 UTC to matrix: failed to ensure joined: failed to ensure registered: failed to POST /_matrix/client/v3/register: M_EXCLUSIVE (HTTP 400): Invalid user localpart for this application service.
Scratch that, all is now in order--appears to be fully functional except for displaynames.
What's wrong with display names? Is it an upstream problem or some misconfiguration? Do upstream report them as working?
Config properly sets these vars to:
bot_displayname_template: '{{.Name}} (bot)'
channel_name_template: '#{{.Name}}'
displayname_template: '{{.RealName}} (S)'
However all the bridged users have their full Slack ID as the display names.
I posted in the mautrix slack matrix channel for now, but will post an issue upstream if I don't hear back. No one else has reported this problem, so it's quite possible I've misconfigured something.
I believe all the vars here "should" work.
https://github.com/slack-go/slack/blob/master/users.go
Naming issue appears fixed in https://github.com/mautrix/slack/commit/f933a14343ad3bef3059bf64eec02f8a34d81461. This merge request should be ready to go!