The list of group members, and admins, is part of the consensus state. Any member in a group knows exactly who's part of that group, and that only admins can make valid commits.
Servers are only trusted for message delivery. Given that every group member somehow gets every commit message, they will converge on a shared state of the group. For now marmot uses nostr relays for message delivery, we're already thinking how to do this with fips, it should work.
Replies (4)
The reliability of message delivery of commit messages is the main difficulty, even in the case of a single admin?
A structured network strategy to sync Nostr relays I think can greatly help the persistance and reliability of messages. Negentropy is a huge help. For example, if all admins independently run relays and have write policies exclusive to members/admins, the relays can sync and secure only those messages between each other. Strfry has some support here with a router. However, last I remember, the features were new and could be optimized. I would need to look again.
Yes, and now do this with relays on the phone and fips connection between them, cypherpunk future is now.
Sure, in some cases! Though, the notorious flakey internet connection of phones adds complexity and difficulty. Local messaging use cases could also benefit from wireless connections (e.g., LoRa/Bluetooth/Wi-Fi). In other cases, relays with low latency and high availability would be useful to bolster reliability. For example, with redundant-powered SBC or VPS relay servers with multiple internet connections/transports.
