Minutes interim-2024-mimi-06: Wed 16:00
minutes-interim-2024-mimi-06-202406191600-00
| Meeting Minutes | More Instant Messaging Interoperability (mimi) WG | |
|---|---|---|
| Date and time | 2024-06-19 16:00 | |
| Title | Minutes interim-2024-mimi-06: Wed 16:00 | |
| State | Active | |
| Other versions | markdown | |
| Last updated | 2024-06-19 |
minutes-interim-2024-mimi-06-202406191600-00
MIMI interim, June 19 2024
Content Draft
-
Raphael: Do you have implementation to share?
- Rohan: Will by next IETF. Anyone else?
- Show of hands: 4
-
Rohan: Travis, ok with closing ticket on Matrix extensible events?
- Travis: yes
-
Rohan: Thoughts on leaving implicit id, given potential value for
sharing message history?- Raphael: Maybe premature to make that decision
Metadata Privacy
-
Konrad: #3 is still the pseudonym approach, but with handshake
messages encrypted to the hub?- Rohan: Yes
-
Brendan: What is the value of having pseudonyms, if they can't be
tracked to prevent abuse?- Rohan: There are other approaches to solve abuse, for example,
privacy pass
- Rohan: There are other approaches to solve abuse, for example,
-
Konrad: I think we agree we want a non-protected mode, and a
metadata protected mode. Question is just which mode for protection.
Proposal to wait for Brendan's I-D then decide.- Rohan: If we go with #4, we will have to come up with a new
mechanism for how we do almost everything in mimi. Deployment
will be unlikely because of legal requirements. - Brendan: What mechanisms / what legal requirements?
- Rohan: KYC. Supporting banishing someone from group.
- Alissa: Regardless of where we land, need to enumerate how we
envision all the typical admin actions working
- Rohan: If we go with #4, we will have to come up with a new