From cc3b01f97523ba458bdafe60157ffadaffe6023b Mon Sep 17 00:00:00 2001
From: "Tristan B. Kildaire" <deavmi@disroot.org>
Date: Mon, 28 Sep 2020 13:58:29 +0200
Subject: [PATCH] Updated protocol

---
 protocol.md | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/protocol.md b/protocol.md
index 8e6edaf..6c21fed 100644
--- a/protocol.md
+++ b/protocol.md
@@ -81,7 +81,7 @@ Reply format:
 Request format:
 
 ```
-|-- 5 --|-- type (1 byte) --|
+|-- 5 --|-- type (1 byte) --|-- locationSize (1 byte) --|-- location (n-bytes) --|-- message (n-bytes) --|
 ```
 
 * The `type` field specifies whether the message is to be sent to a user or channel
@@ -133,8 +133,19 @@ it depends, and `0` means error - also more data may follow.
 
 We know as tristanable tag 1, but then _types_ of notifications is the important factor described here.
 
-### TODO: message receive format
-
 ```
 |-- notifyTYpe (1 byte) --|-- ..
-```
\ No newline at end of file
+```
+
+### TODO: message receive format (`notifyType=0`)
+
+For a normal channel message or direct message
+
+TODO
+
+### TODO: channel status message (`notifyType=1`)
+
+types within:
+
+1. `0` - 1 byte: Member leave
+2. `1` - 1 byte: Member join
\ No newline at end of file