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
[BUG] wee-slack loads old threads in buffers #830
Comments
Are you using an OAuth or session token to authenticate with Slack? OAuth tokens can't be used to mark threads as read, so it's possible that those old threads are not marked as read and when wee-slack reconnects they will open again. See https://github.com/wee-slack/wee-slack#4-add-your-slack-api-tokens. You can tell the difference between token types as OAuth tokens start with |
@mhoran , I used session tokens |
@hissssst: Can you enable debug mode and see if you get any errors in the core buffer? |
@trygveaa - I faced the same issue even with session tokens. A few several-months-old threads (but not all) are always opened on startup, and even on network reconnection. I checked in debug mode but did not find any errors or warnings. But, I did find that all the opened threads contain a So, maybe this scenario is not handled correctly somewhere? |
It looks like the issue here may have been that some threads that one isn't subscribed to was opened by Hopefully this was the issue, but feel free to comment or open a new issue if there's still problems. Note that it's still a problem with OAuth tokens as mentioned above, it only works with session tokens. I recommend disabling Thanks to @srijan for helping figuring this out here and on IRC. |
Envitoment:
Options
Current behaviour
wee-slack opens old threads with mentions in separate buffers
Desired behaviour
Only threads with mentions created after starts are opened in separate buffers
The text was updated successfully, but these errors were encountered: