...whenever we encrypt or decrypt a message on them. This adds
another line of logging for every device in the room, so will
be reasonably verbose if you're in large encrypted rooms, but
the information ought to be valuable.
Requires https://gitlab.matrix.org/matrix-org/olm/merge_requests/9
Don't merge before a new version of Olm is released with this merge
request (it won't work).
This removes the IS details (server and access token) from `requestToken` calls
to the HS, as long as the HS supports the new separate add and bind mode. In
this mode, all of the 3PID validation is handled by the HS, so the IS details
are not used.
Fixes https://github.com/vector-im/riot-web/issues/10933
This API has existed for quite a while, but historically we've instead proxied
this request via the homeserver. As part of MSC2290 work, we are changing
approaches such that we will request tokens directly from the IS when binding
for discovery.
Part of https://github.com/vector-im/riot-web/issues/10839
This adds a way to test for MSC2290 support on the homeserver with separate add
and bind functions. It checks the unstable feature flag as well as the upcoming
r0.6.0 spec version.
Part of https://github.com/vector-im/riot-web/issues/10839
Fixes https://github.com/vector-im/riot-web/issues/10898
In some restricted modes of Firefox, the WebRTC classes aren't super available: accessing them can cause SecurityErrors to be raised. In these conditions, we should just disable WebRTC support instead of falling apart.
To avoid the same problem that happened with lazy-loading (see https://github.com/matrix-org/synapse/issues/5528).
Note that as of writing r0.6.0 is not yet released, however it is the next scheduled release of the client-server API.
When the pending event order setting was set to 'chronological'
(the default) `addPendingEvent` would NPE because Room no longer
has a `this._filter` property. It should get the filter from the
event timeline set instead, as it does in the previous line when
checking or the presence of a filter.
We should strongly consider changing the default pending event order
to 'detached' and probably removing 'chronological' or comitting to
support it properly: it's not really tested and is prone to breakage
like this.
Applies flumpt's fix from https://github.com/matrix-org/matrix-js-sdk/issues/599
Fixes https://github.com/matrix-org/matrix-js-sdk/issues/599
For example, if the identity server throws a 401 on `/account`, we end up here with a JSON object. Don't convert the string `object Object` to JSON because it'll fail: just use the object.
This passes along the `id_access_token` to the HS, which it will need when
speaking v2 IS APIs to the IS.
Unfortunately, some HSes seem to explode when given this new parameter, so we
only pass it along for the moment if an unstable feature `m.id_access_token` is
also set.
Part of https://github.com/vector-im/riot-web/issues/10525
Defined in MSC2140
Hubert Chathi