mx-puppet-slack icon indicating copy to clipboard operation
mx-puppet-slack copied to clipboard

Slack puppeting bridge for matrix

Results 48 mx-puppet-slack issues
Sort by recently updated
recently updated
newest added

This project doesn't seem to be pure-node, and judging by the dependencies (as well as the Dockerfile) [these](https://github.com/Automattic/node-canvas#compiling) packages at least need to be installed before `npm install`. Shouldn't this...

I run `unlink 1` in the control room and this turns up in the logs: ``` [ERROR] WebClient:2 Failed to fetch members for the channel. Nov-2 09:42:40.423 [MatrixEventHandler] error: Error...

If e.g. slackbot joins it would be nice if it left again after a short period of inactivity.

Slack puppet is exceeding grace period when stopping docker container. Related to https://github.com/Sorunome/mx-puppet-bridge/issues/57

It seems the bridge ignores messages sent by a puppeted user (in my case xoxc) when considering which message should be replied to: ![image](https://user-images.githubusercontent.com/1029578/86532570-6f1c8500-becb-11ea-8404-7fe511e109d0.png) ![image](https://user-images.githubusercontent.com/1029578/86532573-75aafc80-becb-11ea-89a7-f6cd70b51aa2.png)

Can you describe what functionality the relay mode provides over the puppeting functionality?

question

This project is missing the documentation to help users setup the Slack App with the correct permissions to use the puppet.

![image](https://user-images.githubusercontent.com/1048265/80335162-537c6a80-8808-11ea-80bd-d5da3de7f78b.png) getting this message when nothing apparent has happened in the bridged slack room ``` Apr-27 04:51:37.807 [SlackPuppet:slack] info: Received create request for channel update puppetId=1 roomId=T02A11S1M-G0C07RXCG Apr-27 04:51:37.811 [SlackPuppet:slack]...

bug