get rid of human-readable personna name

pull/4/head
Zlatin Balevsky 2018-07-10 19:29:56 +01:00
parent 083114ce10
commit 6781944bdf
2 changed files with 2 additions and 2 deletions

View File

@ -35,4 +35,4 @@ Nodes will periodically ping a pre-defined Destination for a JSON document conta
### Web Of Trust
Users may choose to "Trust" or "Blacklist" Destinations that return search results. This trust is local to the user, but it can be shared with others. Upon installation the user picks a username which does not need to be unique, but from which a globally unique "persona" is created by concatenating the human-readable username with @ and the b32 hash of the destination of their node. This persona is returned together with search results and when displayed in the UI the user is given the choice to trust or distrust them.
Users may choose to "Trust" or "Blacklist" Destinations that return search results. This trust is local to the user, but it can be shared with others. Each user is assigned a "personna" which is the first 32 bytes of the b32 hash of their node Destination. This persona is returned together with search results and when displayed in the UI other users are given the choice to trust or distrust it.

View File

@ -124,7 +124,7 @@ This message starts with two unsigned bytes indicating the number of patches inc
### Search results - any node to any node
Search results are sent in "results" type connection from the responder to the originator of the query. This connection is uncompressed and only Alice sends any data on it, i.e. there is no handshake. The first thing that Alice sends is the UUID of the search that generated the results. This allows Bob to drop the connection if he does not recognize that UUID. After that Alice sends her human-readable username so that Bob can choose whether to trust or distrust her. After that, Alice sends a stream containing JSON messages prefixed by two unsigned bytes indicating the length of each message. The format is the following:
Search results are sent in "results" type connection from the responder to the originator of the query. This connection is uncompressed and only Alice sends any data on it, i.e. there is no handshake. The first thing that Alice sends is the UUID of the search that generated the results. This allows Bob to drop the connection if he does not recognize that UUID. After that, Alice sends a stream containing JSON messages prefixed by two unsigned bytes indicating the length of each message. The format is the following:
```
{