Per-user policies & grace periods #5

New Issue

phryk · 2021-07-29T02:11:02Z

phryk commented

2021-07-29 02:11:02 +00:00

This is a key point in making mod_e2e_policy more practical.

E2EE can be fiddly to get working (Dino setup key troubles for example).
Thus we want to allow new users a grace period in which the policy for them is set to optional before it automatically turns to required.

Also, make this behavior optional, with another option being enabling users to set their policy (and possibly accepted E2EE schemes [see #3] via Ad-Hoc commands) and yet another the old behavior of having just one static policy for direct messages and another for MUCs.

And, of course add module options as needed.

This is a key point in making mod_e2e_policy more practical. E2EE can be fiddly to get working (Dino setup key troubles for example). Thus we want to allow new users a grace period in which the policy for them is set to `optional` before it automatically turns to `required`. Also, make this behavior optional, with another option being enabling users to set their policy (and possibly accepted E2EE schemes [see #3] via Ad-Hoc commands) and yet another the old behavior of having just one static policy for direct messages and another for MUCs. And, of course add module options as needed.

phryk referenced this issue

2021-08-01 23:33:53 +00:00

"required" policy restricts E2EE warnings from arriving #1

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: phryk-evil-mad-sciences-llc/mod_e2e_policy#5