-
Notifications
You must be signed in to change notification settings - Fork 73
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
Try RTM API instead of in+outbound webhooks #41
Comments
One tiny thorn appears to be that an "app bot" account is not able to set a room topic, so Matrix->Slack topic bridging wouldn't work in this case. |
I agree we should use RTM API, it's much more powerfull than outgoing webhook. But does an app bot can change it's avatar and username per message? I don't think so. One idea is to use an app bot with RTM API only to get more information from message (mainly attachments), but still keep ingoing webhook to post messages. Add a possibility for user to opt-in and puppet them would be an amazing bonus. |
The way to do this would be to have the bridge act as a “puppeting” bridge - ie logging on with real slack credentials as a real user to mirror that user’s activity in Matrix. I think @leonerd added this to gitterbridge (but not yet deployed) but not slackbridge |
Yes but I like the ability to bridge users who doesn't have a slack account.
And iirc there is already a puppet only slack bridge.
Le 2 oct. 2017 1:31 AM, "Matthew Hodgson" <[email protected]> a
écrit :
… The way to do this would be to have the bridge act as a “puppeting” bridge
- ie logging on with real slack credentials as a real user to mirror that
user’s activity in Matrix. I think @leonerd <https://github.com/leonerd>
added this to gitterbridge (but not yet deployed) but not slackbridge
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAdQ0YL56GYMJhB7y6hcAfx8JcH8ugULks5soCDYgaJpZM4LTM5A>
.
|
@Half-Shot this can be closed by #89 right? |
or at least renamed to "support user puppeting" |
Closing this, and making #104 for puppeting. |
https://api.slack.com/rtm
In summary it seems:
The text was updated successfully, but these errors were encountered: