f1xska

<h1>Messenger</h1>
<div class="level1">

<p>
Frequently there is a need to communicate with People with same interests or located in the same area. Examples:
</p>
<ul>
<li class="level1"> a hotel guest might want to discover groups of the hotel</li>
<li class="level1"> at some event men want to organize Minyan and want a way to agree on time and place</li>
<li class="level1"> a lost child or item was found and want to announce that in "Lost and Found" group of the area</li>
<li class="level1"> a person wants to discuss some public event with like-minders</li>
</ul>

<p>
For matter of the Machon Tal Term Project Success, the POC would allow flow below:
</p>
<ol>
<li class="level1 node"> A person creates "stored query" with properties below:<ul>
<li class="level3"> kind: Messages</li>
<li class="level3"> with date not older than week ago</li>
<li class="level3"> geo: X,Y with radius R</li>
<li class="level3"> query lifetime for the next 2 hours</li>
</ul>
</li>
<li class="level1 node"> He reviews results and sees summary of Messages found, grouped by topic name and number of unique posters (implying activity) and wants to subscribe to certain topic:<ul>
<li class="level3"> he creates folder with "chat view" Memo with the topic id, and exports it</li>
<li class="level3"> the Memo automatically creates "stored query" for Memos of kind:Message, date not older than week ago and that topic id</li>
<li class="level3"> any message Memo he creates will contain same topic id, and get consumed by other subscribers</li>
<li class="level3"> he might want to enable popup notification on every incoming message</li>
</ul>
</li>
</ol>

<p>
What essentially happens here, that each participant <b>maintain his own "view" of chat, based on local and incoming posts</b>. Should he ever decide to leave the chat "e.g. dereference the group", copy of all his messages will remain on all participants "exported storage".
</p>

<p>
The scenario above might be extended to cover more cases like these:
</p>
<ul>
<li class="level1"> ignore someone that posts offensive content</li>
<li class="level1"> send message about group details to someone ("Invite them")</li>
<li class="level1"> propose "group" icon that allows voting. The one with most votes is shown as "group" logo</li>
</ul>

</div>

<h2>Privacy (aka Mail mode aka "shared" folder)</h2>
<div class="level2">

<p>
There might be need to for private Memos exchange between two or more parties. In this flow, the sites are essentially <b>"notifying" others what changes they are suggested to do in their own copy of the folder</b>:
</p>
<ol>
<li class="level1"> An public/private keypair is created <b>by each participant of the folder</b></li>
<li class="level1"> For each recipient, the keypair is encrypted with his public key and Memo of kind "KeyPair" and recipient id is created</li>
<li class="level1"> Recipients has active subscription to all Memos of kind "KeyPair" and recipient equals his id</li>
<li class="level1"> recipient receives the "KeyPair" Memo, decrypts it and stores in his keyring.</li>
<li class="level1"> recipient subscribes to all Memo of kind "Encrypted" and id=hashed keyring, instructs the system to put incoming Memos into speicific folder.</li>
</ol>

<p>
At this point the folder of each participant is empty, all participants have<b> their own empty folder</b>  and they are subscribed to each other on suggested updates to the folder. Thus every change to the folder content has two flows below:
</p>

<p>
For change initiator:
</p>
<ol>
<li class="level1"> Local Memo is "encrypted" and exported as blob</li>
<li class="level1"> Reference to the blob it is added to the local folder. The epoch is bumped, folder is encrypted using the keyring and exported</li>
</ol>

<p>
For change recipients
</p>
<ol>
<li class="level1"> Blob of kind "Encrypted" and id=hashed arrives</li>
<li class="level1"> Assert Epoch is one-next than the currently known one, abort if not</li>
<li class="level1"> unpack the blob, <b>replace </b>content (e.g. references) of the existing folder</li>
</ol>

</div>

Enable Complex Tables Editor Height px Turn supplementary image paste support on

Edit summary: Minor changes