From f2d291e7fca99affdc52b33e0dff4291fff481be Mon Sep 17 00:00:00 2001
From: Wim <wim@42.be>
Date: Fri, 3 Apr 2020 21:43:18 +0200
Subject: [PATCH] Updated Slack bot setup (markdown)

---
 Slack-bot-setup.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Slack-bot-setup.md b/Slack-bot-setup.md
index 34dc705..f717028 100644
--- a/Slack-bot-setup.md
+++ b/Slack-bot-setup.md
@@ -3,7 +3,7 @@
 ### Contents
 
 [Bot-based Setup](#bot-based-setup)<br/>
-[Legacy Setup](#legacy-setup)<br/>
+<strike>[Legacy Setup](#legacy-setup)</strike><br/>
 [Issues](#issues)
 
 ---
@@ -67,6 +67,8 @@ Now you are all set to go. Just configure and start your Matterbridge instance a
 
 # 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!
 
 Slack Docs: [Legacy tokens](https://api.slack.com/docs/token-types#legacy)