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

Migrate to using Web API instead of webhooks #10

Open
patcon opened this issue Jul 13, 2017 · 2 comments
Open

Migrate to using Web API instead of webhooks #10

patcon opened this issue Jul 13, 2017 · 2 comments

Comments

@patcon
Copy link
Contributor

patcon commented Jul 13, 2017

The Slack Web API does allow apps to write messages as_user, but it's a little tricky:
https://codexample.org/questions/417349/is-it-possible-to-post-to-chat-postmessage-as-any-user-in-a-slack-team.c#answer-880240

Using Web API would allow:

  • Sending reactions across bridge (would require asking each "reacting" user to auth with app, which is no small feat)
  • Sending edits across bridge
  • Sending "user is typing" messages (using typing in RTM api)

I agree that this is probably not priority, and so would require someone else to do the work. I would also remove the simplicity of the current approach... I would understand if you think this should be tackled by a separate project :)

@wdoekes
Copy link
Member

wdoekes commented Jul 24, 2017

Yes, I did another bot for a different purpose and did see the possibility to do the above, but getting it all right is rather cumbersome. For now, I'd rather keep things simple. My first priority would be to make the setup (configuration and token generation) simpler.

@patcon
Copy link
Contributor Author

patcon commented Aug 1, 2017

Cool! I'll leave this open for posterity, but feel free to close if that's your triage pref

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