Keybase Exploding Messages
151–155 of 155 posts
Re: Keybase Exploding Messages
#152Re: Keybase Exploding Messages
#153Re: Keybase Exploding Messages
#154Earlier quoted context omitted.
From the FAQ: Does the timer begin when the message is sent or received? Sent. This seems like the only sensible answer for group chats. And we can't have a different answer for 1-on-1 chats and group chats. That would confuse people. Not the kind of person who reads an FAQ such as yourself, of course. So our answer is simple: you set a timer and the message is gone after that time.
>And we can't have a different answer for 1-on-1 chats and group chats. What might be the reasoning here that Keybase won't do it yet Signal messenger does start the timer on the "receive" end?
- Signal never deletes keys until after a message is read, because the key schedule and the message history are closely integrated. So if I send a "30 seconds" disappearing message, but you read it a month later, that will work. Keybase doesn't work that way; we delete keys on a fixed schedule, generally about a week. The "start the clock after sending" rule fits our key schedule better, without creating confusing cases at the one week boundary.
- Keybase is designed to support "very large" groups, like thousands of people. In that setting, a "start the clock after reading" rule would be a problem. It's unrealistic that all N thousand members will ever read a given message, and that would make deletion less reliable.
Re: Keybase Exploding Messages
#155Seriously, do we need a stupid animation and a silly-looking "ka-boom" image? It just comes across as trying too hard to be cute and ends up looking childish and stupid.
Metaphors like this help people understand what's happening. If the message just vanishes that could be for any number of reasons. But with this animation it's clear that the message is being erased. Keep in kind not everyone is a hackernews-reading computer expert.