GitHub/matterbridge
3
0
Fork 0
mirror of https://github.com/42wim/matterbridge.git synced 2024-11-15 00:19:24 +01:00
Code Issues Projects Releases Wiki Activity

Updated Slack bot setup (markdown)

Wim 2020-04-03 21:43:18 +02:00
parent 7a215cf7c3
commit f2d291e7fc
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Slack-bot-setup.md

@ -3,7 +3,7 @@
### Contents ### Contents
[Bot-based Setup](#bot-based-setup)<br/> [Bot-based Setup](#bot-based-setup)<br/>
[Legacy Setup](#legacy-setup)<br/> <strike>[Legacy Setup](#legacy-setup)</strike><br/>
[Issues](#issues) [Issues](#issues)
--- ---
@ -67,6 +67,8 @@ Now you are all set to go. Just configure and start your Matterbridge instance a
# Legacy setup # Legacy setup
Update: 2020-04-03 - this setup is not working anymore. (See https://github.com/42wim/matterbridge/issues/964#issuecomment-607629250)
🛑 This setup is not recommended and will disappear in future versions of Matterbridge. Please use it only if you are absolutely sure that you can not use the normal setup. Legacy tokens are, as their name indicates, a legacy feature and Slack can in the future **deprecate them at short notice** as they have a weak security model and **give access to a wide-range of privileged actions**. Always store your token securely! 🛑 This setup is not recommended and will disappear in future versions of Matterbridge. Please use it only if you are absolutely sure that you can not use the normal setup. Legacy tokens are, as their name indicates, a legacy feature and Slack can in the future **deprecate them at short notice** as they have a weak security model and **give access to a wide-range of privileged actions**. Always store your token securely!
Slack Docs: [Legacy tokens](https://api.slack.com/docs/token-types#legacy) Slack Docs: [Legacy tokens](https://api.slack.com/docs/token-types#legacy)