cryslith / kataomoi Goto Github PK

Instead of just spewing everything into the console (which we should still do), we should figure out what to display to the user when various error/warning conditions happen.

When another user takes too long to reply or gets disconnected during a time-sensitive stage of the SENPAI protocol, we currently flag them as cheating, but this could just be a problem with the server or with their internet connection. We should give users a "recovery phrase" that they can pass on to their partner if they get disconnected, containing either s or x depending on which role the user is playing in the protocol. The client will allow users to complete the answer-sharing and honesty-proving stages out-of-band if necessary, by exchanging these phrases over any medium they choose.

Requiring people to organize and choose a time to use kataomoi together is a serious hindrance to using kataomoi successfully. We should allow users to select Yes/No answers for other users who aren't currently online; the protocol exchange still can't take place until both users are online at the same time, but online status can be detected automatically and acted upon by the client without further user intervention.

In more detail, this would require persistent user accounts instead of ephemeral rooms and usernames. Users would create accounts, and join (or be invited into) "circles" containing other users, who they could then select answers for. Clients would detect when users in the same circle come online, and perform exchanges then if they hadn't recently performed an exchange with the same user. Long-term client state (such as keypair, circle memberships, choices for other users, and past results) would be encrypted client-side with the user's password, and then both stored in browser localStorage (when possible) and sent to the server to be saved.

When dealing with users not in the same physical location, we'll need fancier mechanisms for authenticating mappings between real identity and username/public key. We should give users a way to display their own public key fingerprint for verification, and locally sign other users' public keys (these signatures would become part of the saved client state). Adding ways for users to verify public keys without face-to-face interaction (for example, users can upload a PGP-signed statement for other users to view) could also be useful.

Instead of just having page load stall while keys are generated, we should have a widget that says "Generating cryptographic keys, please wait..." and do the keygen in a way that doesn't hang up the browser. Not sure whether Forge's web worker keygen is useful, but we can always go with createKeyPairGenerationState and stepKeyPairGenerationState as used in their example code in the readme.

I don't think we're doing anything sensible in case of issues with AES decryption or OEAP unpacking. We should make sure that an adversary who sometimes spews random garbage at the client doesn't break anything.

Links on the main page should open in a new tab so client state isn't lost.

What's this all about, how does it work, what's a "room", what does "DTF" mean, how do I use any of this, etc.