Congratulations to the keybase team. Most people here seem to be making a self fulfilling prophecy of keybase's death. But I like to think that Zoom intends t

Congratulations to the keybase team. Most people here seem to be making a self fulfilling prophecy of keybase's death. But I like to think that Zoom intends to reuse large parts of keybase codebase: > Logged-in users will generate public cryptographic identities that are stored in a repository on Zoom’s network and can be used to establish trust relationships between meeting attendees. An ephemeral per-meeting symmetric key will be generated by the meeting host. This key will be distributed between clients, enveloped with the asymmetric keypairs and rotated when there are significant changes to the list of attendees. The cryptographic secrets will be under the control of the host, and the host’s client software will decide what devices are allowed to receive meeting keys, and thereby join the meeting. We are also investigating mechanisms that would allow enterprise users to provide additional levels of authentication. Will the founders be interested in releasing parts if not all of the server code to the public? I believe the founders' mission is still achievable and can be carried out, should they be willing to release the code in public.