-
-
Notifications
You must be signed in to change notification settings - Fork 606
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
71 changed files
with
5,047 additions
and
5,182 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,6 +8,7 @@ out | |
reports | ||
/dist | ||
/lib | ||
/specbuild | ||
|
||
# version file and tarball created by 'npm pack' | ||
/git-revision.txt | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,6 @@ | ||
language: node_js | ||
node_js: | ||
- node # Latest stable version of nodejs. | ||
script: | ||
- npm run lint | ||
- npm run test |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -65,6 +65,7 @@ Later versions of the SDK will: | |
Usage | ||
===== | ||
|
||
|
||
Conventions | ||
----------- | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
Random notes from Matthew on the two possible approaches for warning users about unexpected | ||
unverified devices popping up in their rooms.... | ||
|
||
Original idea... | ||
================ | ||
|
||
Warn when an existing user adds an unknown device to a room. | ||
|
||
Warn when a user joins the room with unverified or unknown devices. | ||
|
||
Warn when you initial sync if the room has any unverified devices in it. | ||
^ this is good enough if we're doing local storage. | ||
OR, better: | ||
Warn when you initial sync if the room has any new undefined devices since you were last there. | ||
=> This means persisting the rooms that devices are in, across initial syncs. | ||
|
||
|
||
Updated idea... | ||
=============== | ||
|
||
Warn when the user tries to send a message: | ||
- If the room has unverified devices which the user has not yet been told about in the context of this room | ||
...or in the context of this user? currently all verification is per-user, not per-room. | ||
...this should be good enough. | ||
|
||
- so track whether we have warned the user or not about unverified devices - blocked, unverified, verified, unverified_warned. | ||
throw an error when trying to encrypt if there are pure unverified devices there | ||
app will have to search for the devices which are pure unverified to warn about them - have to do this from MembersList anyway? | ||
- or megolm could warn which devices are causing the problems. | ||
|
||
Why do we wait to establish outbound sessions? It just makes a horrible pause when we first try to send a message... but could otherwise unnecessarily consume resources? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.