Documentation

Cannot fetch prekeys of LH users if requester has not given consent or has old clients.

pops a channel until it finds an event that returns a Just upon running the matcher function

like checkChan but throws away the request and decodes the body

this sets the timeout to a higher number; we need this because the SQS queue on the brig is super slow and that's why client.remove events arrive really late

FUTUREWORK(mangoiv): improve the speed of internal event queuing

If a member of an existing conversation is assigned a LH device, users are removed from the conversation until policy conflicts are resolved.

As to who gets to stay: - admins will stay over members - local members will stay over remote members.

scenario 2.2: charlie is put under legalhold but creates an MLS Group himself since he doesn't need to claim his own keypackage to do so, this would succeed we need to check upon group creation if the user is under legalhold and reject the operation if they are

LH can be configured in a way that does not require users to give preliminary consent to LH when being added to a team. The user still has to approve the LH device before the recording starts. This is called "implicit consent", was introduced to accomodate specific work flows, and there is some hope that it'll be removed in the future.

Explicit consent requires users to consent on entering the team, and then approve the actual being put under recording again if it happens.

This flag allows to make tests run through both configurations with minimal adjustment.

Ensure that the LH config is as expected: Either by expecting it from the current server's config. Or, by creating a new one.