This differential implements notification encryption with olm session on web.
Details
Details
- Reviewers
tomek inka kamil - Commits
- rCOMM9df96ca6c7f8: Implement notification encryption on web
Tested in D12673
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
web/push-notif/notif-crypto-utils.js | ||
---|---|---|
318 ↗ | (On Diff #42041) | Why are we using the content key instead of notif? |
web/push-notif/notif-crypto-utils.js | ||
---|---|---|
318 ↗ | (On Diff #42041) | We are using key for notif session here. Content in this variable refers to "the content of notif olm session" |
web/push-notif/notif-crypto-utils.js | ||
---|---|---|
318 ↗ | (On Diff #42041) | Can you rename? This seems like very confusing naming |
Comment Actions
Rename ...DataContent... -> ...Data... to remove confusion around Conent keyword when dealing with notifs sessions
Comment Actions
Make encryptNotification a part of olmAPI. This change is ESSENTIAL on web since it makes encryptNotification run on shared worker. This enables us to deterministically handle race conditions.