They share the same leaf node. The cool part is totally opt-in, you can keep using the manual multi-leaf-node approach that the RFC provides, or use this one, which is basically a mesh sync using Blos...
How did you handle the fact that each leaf node has a ratcheting key? If I remember MLS correctly each leaf node has a ratchet but its not strict, the application messages can come out of order. But I remember having an issue with two clients sharing state because they didn't want to send two application messages on the same leaf node ratchet index...
All very confusing stuff, but I'm interested how you guys got multiple clients to share the same state without fighting each other
All very confusing stuff, but I'm interested how you guys got multiple clients to share the same state without fighting each other
2
