You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I understand the point of having AckRequests and Acks in chat channels, in certain cases it might be nice to have them auto explode. For example, if I need to track which users signed in, the bot's response with the certificate is enough. Once the bot has given this cert, I really don't care about the Ack messages.
It would be nice for these Ack messages to auto explode. The default could, for example, be 5minutes, and of course be configurable
The text was updated successfully, but these errors were encountered:
@krezreb you can set an exploding retention policy on the conversation and the client will respect the policy and apply the default. @mmou we can likely close keybase/go-keybase-chat-bot#68 as a result
Setting the conversation retention policy to is a decent alternative, but perhaps the intention of this request is to be able to retain the Signature_Request and Signature_Response messages, and only explode the AckRequest and Ack messages.
If you set the policy to explode all messages, you can still audit logins by looking at your SSH CA logs at LOG_LOCATION.
While I understand the point of having AckRequests and Acks in chat channels, in certain cases it might be nice to have them auto explode. For example, if I need to track which users signed in, the bot's response with the certificate is enough. Once the bot has given this cert, I really don't care about the Ack messages.
It would be nice for these Ack messages to auto explode. The default could, for example, be 5minutes, and of course be configurable
The text was updated successfully, but these errors were encountered: