Kaladaran/briar
0
0
Fork 0
mirror of https://code.briarproject.org/briar/briar.git synced 2026-02-25 00:59:54 +01:00
Code Issues Projects Releases Wiki Activity

akwizgran created page: ForumApp

akwizgran
2015-04-17 14:06:38 +00:00
parent 3e4863767a
commit 7801dd372c
1 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
BlogApp.markdown

@@ -1,4 +1,4 @@
BlogApp is a [BSP application](BSP) that synchronises blog posts among groups of devices. Any subscriber to a blog can invite their contacts to subscribe, but only the creator can write posts.
BlogApp is a [BSP application](BSP) that synchronises blog posts among groups of devices. Any subscriber to a blog can invite non-subscribers to subscribe, but only the creator can write posts.
### Channel identifiers
@@ -14,9 +14,9 @@ The application identifer is random:
**0: INVITATION** - The content is a BDF list with three elements: `blog` (list) and `note` (string, may be null). `blog` is a list with two elements, `name` and `public_key`, as described above. `note` is an optional note from the inviter to the invitee.
**1: RESPONSE** - The content is a BDF list with three elements: `invitation_id` (raw), `decision` (boolean), and `note` (string, may be null). `invitation_id` is the identifier of an invitation created by the opposite device. `decision` indicates whether the invitee wishes to subscribe. `note` is an optional note from the invitee to the inviter.
**1: RESPONSE** - The content is a BDF list with three elements: `invitation_id` (raw), `decision` (boolean), and `note` (string, may be null). `invitation_id` is the identifier of an invitation created by the opposite peer. `decision` indicates whether the invitee wishes to subscribe. `note` is an optional note from the invitee to the inviter.
**2: DEPARTURE** - The content is a BDF list with one element: `invitation_id` (raw), which is the identifier of an invitation created by either device.
**2: DEPARTURE** - The content is a BDF list with one element: `invitation_id` (raw), which is the identifier of an invitation created by either peer.
**3: POST** - The content is a BDF list with two elements: `signature` (raw) and `content` (list). `signature` is calculated over `content`.
@@ -29,8 +29,8 @@ The application identifer is random:
* An invitation or response must belong to the invitation channel.
* A post or attachment must belong to a blog channel.
* An invitation is valid if it is well-formed.
* A response is valid if it is well-formed and it references a valid invitation created by the opposite device.
* A departure is valid if it is well-formed and it references a valid invitation created by either device.
* A response is valid if it is well-formed and it references a valid invitation created by the opposite peer.
* A departure is valid if it is well-formed and it references a valid invitation created by either peer.
* A post is valid if it is well-formed, its parent (if any) is a valid post, and it carries a valid signature over its content.
* An attachment is always valid.
@@ -43,15 +43,15 @@ For the invitation channel:
* All remote messages are stored.
For forum channels:
* Local messages are stored while the local device subscribes to the blog.
* Remote messages are stored while the local device subscribes to the blog.
* Local messages are stored while the local per subscribes to the blog.
* Remote messages are stored while the local peer subscribes to the blog.
### Sharing policy
For the invitation channel:
* Each local message is shared with one remote device.
* Remote messages are not shared with other remote devices.
* Each local message is shared with one remote peer.
* Each remote message is shared with the remote peer that created it.
For forum channels:
* Local messages are shared with all remote devices that subscribe to the blog.
* Remote messages are shared with all remote devices that subscribe to the blog.
* Local messages are shared with all remote peers that subscribe to the blog.
* Remote messages are shared with all remote peers that subscribe to the blog.