diff options
| author | Trygve Aaberge <trygveaa@gmail.com> | 2020-05-05 22:23:46 +0200 |
|---|---|---|
| committer | Trygve Aaberge <trygveaa@gmail.com> | 2020-05-05 23:55:15 +0200 |
| commit | 8379f8a5ee270625afd3ac427ed8ee7f03ac2501 (patch) | |
| tree | 66276d7914f3a68eed90f8dda92c56dc4e921667 /README.md | |
| parent | 5d27e9066bff8083326fe84877b50f2940d051de (diff) | |
| download | wee-slack-8379f8a5ee270625afd3ac427ed8ee7f03ac2501.tar.gz | |
Fix /slack register not working after API change
Slack now disallows # in OAuth redirect uris, so we can't use it to
prevent GitHub Pages from seeing the OAuth code anymore.
Since the OAuth code is only valid once and expire after 10 minutes, I
don't think it's a problem that they are exposed to GitHub Pages, so
this is the new default so the same registration process can be kept.
However, for people worried about this, there's a new -nothirdparty
option to /slack register which can be used which doesn't expose the
code.
Fixes #766
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -124,6 +124,10 @@ wee-slack script. /python reload slack ``` +Note that by default GitHub Pages will see a temporary code used to create your +token (but not the token itself). If you're worried about this, you can use the +`-nothirdparty` option, though the process will be a bit less user friendly. + The tokens you add will be stored in the option `plugins.var.python.slack.slack_api_token`. If you don't want to store your API token in plaintext you can use the secure features of WeeChat: |