3 ms·
>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 sta
by 24gttghh 8y ago
>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?
- wazanator 8y agoIt narrows the attack window. It's not hard to imagine a scenario where something happens to the receiver and as the sender you didn't realize this until you sent a few messages but the third party who got the receiver won't be able to access the device for some time. Hopefully by the time they get in they have self destroyed.
- 24gttghh 8y agoA valid point! Thanks for postulating!
- oconnor663 8y agoThere are a couple of important differences, though someone from Signal might need to correct me if I get this wrong: - 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.