Kenny Meyer

I would like to bump this as this affects me, too. What can be done to fix this?

I do :)

Same issue here, setting `position='relative'` did the trick for me. Thank you @santhosh-john

> Is it recommended to use `Socket Mode` or event subscriptions via the Request URL (webhook) if we plan on supporting multiple workspaces, or does it not matter @seratch gave...

When are you planning to merge this into master?

Thank you, your answer is very appreciated. > A check to [rotate tokens happens with each request](https://github.com/slackapi/bolt-python/blob/dbe2333046b582c087fd19d6812c8a523835f53c/slack_bolt/authorization/authorize.py#L299-L310) and [rotations are done when needed](https://github.com/slackapi/python-slack-sdk/blob/70cf7baa2238b391accd66f1a32b51418a32c072/slack_sdk/oauth/token_rotation/rotator.py#L19-L56). This should all happen behind the scenes...

> or when the token is already expired when it receives a request from Slack. So, the Token Rotation will still work with the refresh token even after the `bot_token`...

> While I understand the option name "token_rotation_expiration_minutes" is a bit confusing, you can set token_rotation_expiration_minutes=1000000 to let bolt-python do rotation every time you receive a request from Slack. (see...

Is this really a security issue if you're accessing your Umbrel without https via tailscale? Isn't the traffic between you and Umbrel always encrypted as long as connected to Tailscale?

seeing the same issue with the following NVR:  did you already fix this?