nielliesmons on Nostr: If MLS can't be :Nostr: LS, I'm not interested. Which means I'm thinking through ...

If MLS can't be LS, I'm not interested.

Which means I'm thinking through solutions on:
1️⃣ How to offer way more content types than just Chat in one group?
- Without specialized applications needing to download the full group state just for you to give access to your private Figmastr files of that group.
- In a way that groups can select the content types they handle
- Where each content type can have different access and persistence conditions. As in: it's ok if Chat messages dissapear after a week, but not ok if the Repos do.

🅰️ I think the answer might lie in having one MLS group per content type and then grouping (pun intended) thes etogether in the main group ID event. And if that group ID is a key pair, we opens even more exciting options.

2️⃣ How to run a mint for the MLS group, zero-knowledge style, where only group members can use the mint, without the mint even knowing who of the group they give access to.

🅰️ Here I just have a strong hunch that this is possible but will need the #ecash crew for guidance.

3️⃣ How to integrate #WebRTC into these groups in a way that scales?

🅰️ Probably worth stealing the video server spec Jitsi uses for this.