qq99 / echoplexus

Socket.io powered chat, JavaScript REPL, whiteboard, and WebRTC calls
Other
393 stars 54 forks source link

Allow identified user to store metadata with his nick #109

Open qq99 opened 11 years ago

qq99 commented 11 years ago

If email exists, we can use gravatar for the user list

qq99 commented 10 years ago

It might be worth looking into OAuth accounts and/or enterprise mode at the same time

heyakyra commented 10 years ago

is a password for nicks supported already so that it is reserved from use by others?

qq99 commented 10 years ago

Not yet, there's no formal notion of accounts at all The closest you can get is using a PGP keypair

heyakyra commented 10 years ago

Ah, cool! Why PGP instead of OTR or WhisperSystems TextSecure protocol?

qq99 commented 10 years ago

I don't know about WhisperSystems TextSecure protocol, but as for OTR:

I did a bit of research into multi-party OTR. It seemed like it's pretty difficult to get a negotiation for potentially many connected clients, and it seems to need to re-negotiate for every join/leave (so this could become quite expensive). Also, I couldn't really understand it nor how too make it work :P OTR is nice, but what I wanted to support was linkable anonymity.

With PGP, the only thing that ever changes is the number of signed&encrypted messages you send out. There's no re-negotiation if you assume your friend is always using the same keypair. It has the nice property that if you're only signing, you only need to send out 1 message. If you're signing and encrypting to every single chat participant, that's N messages, each person receiving their own copy (but echoplexus hides all that from you).

qq99 commented 10 years ago

One of my goals would be to create a dedicated system of accounts, sort of like an enterprise mode, where you cannot participate unless you create an account. Seems like it'd be useful on small personal / company deployments