Blog signature must cover the client ID

akwizgran
2015-04-24 18:17:05 +00:00
parent 47f75b1813
commit 37176db83d

@@ -7,11 +7,11 @@ ForumClient uses the following client identifer:
Each forum has its own channel, and there is a single invitation channel shared by all forums. The [channel descriptor](BSP#channel-identifiers) for the invitation channel is an empty [BDF list](BDF).
The channel descriptor for a forum channel is a list with two elements: `name` (string) and `salt` (raw). The salt is HASH_LEN random bytes. It prevents collisions between forums with the same name.
The channel descriptor for a forum channel is a list with two elements: `name` (string) and `salt` (raw). The salt is HASH_LEN random bytes to prevent collisions between forums with the same name.
### Message types
**0: INVITATION** - The content is a BDF list with three elements: `name` (string), `salt' (raw), and `note` (string or null). The channel identifier can be calculated from `name` and `salt`, as described above. `note` is an optional note from the inviter to the invitee.
**0: INVITATION** - The content is a BDF list with three elements: `name` (string), `salt` (raw), and `note` (string or null). The channel identifier can be calculated from `name` and `salt`, 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 or 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.