localhost_frssoft
/
ocappub
mirror of https://gitlab.com/spritely/ocappub.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Be clear why breaking the actor model breaks our solution

This commit is contained in:
Christopher Lemmer Webber 2019-07-19 13:31:43 -04:00
parent 029898482f
commit dcbb838429
No known key found for this signature in database
GPG Key ID: 4BC025925FF8F4D3
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.org
View File

@ -119,6 +119,9 @@ so the receiving server can decide whom to send the message to.
Unfortunately this decision breaks the actor model and also our suggested Unfortunately this decision breaks the actor model and also our suggested
solution to authorization; see [[https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/topics-and-advance-readings/ap-unwanted-messages.md#org7937fed][MultiBox]] for a suggestion on how we solution to authorization; see [[https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/topics-and-advance-readings/ap-unwanted-messages.md#org7937fed][MultiBox]] for a suggestion on how we
can solve this. can solve this.
This is more serious than it seems; we cannot proceed to make the system
much safer to use without throwing out =sharedInbox= since we will
lose our ability to make intentional, directed messages.
# - What to do about the holes in the spec? Many community members have # - What to do about the holes in the spec? Many community members have
# asked that we codify current behavior. However, as this document lays # asked that we codify current behavior. However, as this document lays