1 line
43 KiB
JSON
1 line
43 KiB
JSON
|
{"doc_urls":["chapter_1.html#chapter-1","Message-flow.html#message-flow","Protocol.html#hole-protocol","Protocol.html#process-of-messaging","Protocol.html#user-ids","Protocol.html#message-request","Protocol.html#message-sending","Protocol.html#adding-friend","API.html#hole-frontend-api","API.html#loginning-and-registration","API.html#registration-request","API.html#login-request","API.html#adding-friends"],"index":{"documentStore":{"docInfo":{"0":{"body":0,"breadcrumbs":3,"title":2},"1":{"body":110,"breadcrumbs":5,"title":2},"10":{"body":13,"breadcrumbs":4,"title":2},"11":{"body":8,"breadcrumbs":4,"title":2},"12":{"body":3,"breadcrumbs":4,"title":2},"2":{"body":0,"breadcrumbs":4,"title":2},"3":{"body":29,"breadcrumbs":4,"title":2},"4":{"body":34,"breadcrumbs":4,"title":2},"5":{"body":26,"breadcrumbs":4,"title":2},"6":{"body":24,"breadcrumbs":4,"title":2},"7":{"body":15,"breadcrumbs":4,"title":2},"8":{"body":0,"breadcrumbs":5,"title":3},"9":{"body":0,"breadcrumbs":4,"title":2}},"docs":{"0":{"body":"","breadcrumbs":"How it works » Chapter 1","id":"0","title":"Chapter 1"},"1":{"body":"(pseudocode in Bash style) Hole receiving messages by looking for new items in \"user's bin\" (place where new messages arrives). Because of how freenet works, we can't just say \"Hey! Do I have new messages?\", we can specify messages index like: \"Hey! Gimme 15th message\". Thus we must remember previous message index and to receive the new message we're requesting for 16th message, if we was able to get 15th message. That's mean, what interlocutor also have to know the last message index in our bin. But how he can know it, if there's a lot of other users who also sending messages to our bin? Of course, you can try to receive all messages from the index, you had last remembered, and next index, next, next... until you find the index which does not exist. But it's a freenet, it's take too much time; The solution is unique Id. User creating and giving his/her unique id to each new interlocutor. And when, if interlocutor sending the message he knows, that last message to us had index $N and sends message with index $N+1, if be more verbose, the new message index he send to us will look like \"$(ID)_($N+1)\"","breadcrumbs":"How it works » Message flow » Message flow","id":"1","title":"Message flow"},"10":{"body":"On base of password will be generted keypair for signing and keypair for encoding. { request_type: \"registration\", username: \"user\", password: \"passwd123\", }","breadcrumbs":"Frontend API » Registration request","id":"10","title":"Registration request"},"11":{"body":"{ request_type: login, username: \"name\", decode_key: \"key\", sign_key: \"key\", }","breadcrumbs":"Frontend API » Login request","id":"11","title":"Login request"},"12":{"body":"Each user have :w","breadcrumbs":"Frontend API » Adding friends","id":"12","title":"Adding friends"},"2":{"body":"","breadcrumbs":"Protocol description » Hole Protocol","id":"2","title":"Hole Protocol"},"3":{"body":"Each user have kind of a bin among freenet network,in which anyone can put message. And for each user this bin is his USK insert key. Each message signed by sender. And user can answer to sender, buy putting message at sender insert key if he know it.","breadcrumbs":"Protocol description » Process of messaging","id":"3","title":"Process of messaging"},"4":{"body":"Each user have unique pseudonym for each user whom he communicates. Thos pseudonyms uses by user to identify who is sender end establish message flow. The \"message flow\" is important here. Probably, for each pair of each people we will not only one unique identifier but... I'm not going to do it in further releases. TODO","breadcrumbs":"Protocol description » user IDs","id":"4","title":"user IDs"},"5":{"body":"To receive a new message we have to send ClientGet to our USK request key with URI like /user_id-message_version. As well, the identifier is consists of user_id-message_number For example: ClientGet\nURI=USK@myMessageBinKey/messages/user5678-3 Identifier=request-user5678-3\nVerbosity=0\nReturnType=direc
|