-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message ID support: The sending side #1946
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1946 +/- ##
==========================================
+ Coverage 75.72% 75.81% +0.08%
==========================================
Files 142 142
Lines 16271 16276 +5
==========================================
+ Hits 12321 12339 +18
+ Misses 3950 3937 -13
☔ View full report in Codecov by Sentry. |
And |
Ah, makes sense; it probably requires a source of randomness or time for the wasm side that it doesn't have otherwise; it could be done via a custom import, or... compiling to the WASI target and include a WASI polyfill in the browser. |
523bf39
to
b7ce432
Compare
b7ce432
to
b6bb0f3
Compare
This closes: #1266
The first patch cleans some logs up, secondly we add optional support to send
message IDs for our
m.room.encrypted
to-device events, and finally we log themessage ID when we encrypt room keys.