Minutes interim-2024-mimi-11: Wed 16:00
minutes-interim-2024-mimi-11-202409181600-00
| Meeting Minutes | More Instant Messaging Interoperability (mimi) WG | |
|---|---|---|
| Date and time | 2024-09-18 16:00 | |
| Title | Minutes interim-2024-mimi-11: Wed 16:00 | |
| State | Active | |
| Other versions | markdown | |
| Last updated | 2024-09-26 |
minutes-interim-2024-mimi-11-202409181600-00
MIMI Interim Meeting - Sept 18, 2024
Basic Recipient Preference Requirement (slide 9)
-
Rohan: If you don't include a tag, what gets returned?
- Femi: Everything gets returned. During discovery, all the
mappings get returned. No need to request an exact tag name. - Rohan: Some concern about the privacy implications of the tags.
- Femi: Everything gets returned. During discovery, all the
-
Rohan: Concerned about sensitive tags (e.g., for personal groups of
a sensitive nature).- Femi: Could give those groups a code name so they are not
exposed. - Rohan: Could enumerate tags.
- Femi: Could give those groups a code name so they are not
Security and abuse preventon (slide 17)
- Alissa: Do we think rate limits can distinguish between legitimate
and illegitimate request volumes?- Femi: Can address this with token buckets assigned to individual
requester accounts.
- Femi: Can address this with token buckets assigned to individual
Additional areas (slide 19)
- Alissa: These are not imposing requirements on the protocol,
correct?- Femi: Correct.
Discussion
-
Rohan: How many DPs will there be? 10s, 100s, 1000s?
- Femi: Could be up to 500 or 1000 over time. Want smaller players
to be able to participate.
- Femi: Could be up to 500 or 1000 over time. Want smaller players
-
Rohan: Re Orie's comment about UTF-8 for tags. Could have a registry
but also with some user-defined portions.
Summary
- Alissa: We will send call for adoption to the list and solicit
reviews.
Future interims
- Rohan: Will have updates on access control, anti-abuse, and content
format coming.