Merge pull request #5 from clokep/mx-diffs

Encryption & notary differences from Matrix.

mx-differences.md

@@ -216,6 +216,26 @@ The only change is made to Step 1 of the content hashing algorithm. The full alg
 3. Hash the resulting bytes with SHA-256.
 4. Encode the hash using unpadded base64.
 
+### Encryption
+
+Encryption is enabled via an `encryption` property in the `m.room.create` event, not via a separate
+`m.room.encryption` event:
+
+
+```json
+{
+   "encryption": {
+      "algorithm": "m.mls.v1.dhkemx25519-aes128gcm-sha256-ed25519"
+   }
+}
+```
+
+Thus encryption must be enabled at room creation time.
+
+`m.mls.commit` events can be viewed by any user in the room, regardless of
+history visibility. The draft doesn't currently cover how exactly this works,
+but should be treated as `shared` history for ease of use for now.
+
 ## Request Authentication
 
 There are largely clarifications to how request authentication works. Namely:
@@ -230,6 +250,9 @@ There are largely clarifications to how request authentication works. Namely:
 This is meant to be compatible with [MSC4029](https://github.com/matrix-org/matrix-spec-proposals/pull/4029), when
 MSC4029 has real content in it.
 
+Linearized Matrix requires attempting the server *first* before falling back to
+a notary server.
+
 ## Linearization Algorithm
 
 The specific mechanics of this algorithm are undefined. The rough idea is that when a DAG-capable server becomes