diff options
| author | dec05eba <dec05eba@protonmail.com> | 2018-05-16 10:24:22 +0200 |
|---|---|---|
| committer | dec05eba <dec05eba@protonmail.com> | 2018-05-16 10:25:06 +0200 |
| commit | e6331c04af99d7deeb9b15be02dd30665c3c41ce (patch) | |
| tree | 7d8c1dadcdefe4579fbcc750a352f3b80879b347 /README.md | |
| parent | 777d8053540cf94f5b2156c8e2b242efb4d07007 (diff) | |
Rewrite code to work with new backend
Redesigned join channel system, read README.md for more information
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 8 |
1 files changed, 7 insertions, 1 deletions
@@ -7,6 +7,12 @@ opendht, boost, libnsgif, mpv, sfml xsel, curl # TODO Use http(s) library to download content (curl?) and stream gif. If content is html, then stop downloading after we have retrieved title, header image and paragraph - +# Channel invite +Inviting users to channel is done by generating an invite key which is a combination of the node hash and an encryption key (a new encryption key, not the same as the one that is used for the channel nodes themselves). +After generating the invite key, the user that generated it will listen to requests to join the channel using InfoHash generated by the node hash and encryption key. +The user that wants to join the channel using the invite key has to sign a message using their public key and encrypt it using the invite encryption key and send it to the same InfoHash the creator of the invite key is using. +If the creator of the invite key can verify that the message they received was signed with the public key that exists in the message and the message can be decrypted using the invite encryption key, then they will respond with the channel node encryption key. +The user that created the invite key will then add the user to the channel and the user that wants to join will wait until they receive 'ADD DATA' node that with the public key that they requested to be added with, +by receiving and decrypting node data with the key the got from the creator of the invite key. # Screenshot  |