# orderedItems[].object.content
An #LMDB storage adapter for #OpenMLS, the #rust implementation of Messaging Layer Security
https://github.com/parres-hq/openmls-l mdb-storage

# orderedItems[].object.ephemeral.metadata[].twitterTitle
GitHub - parres-hq/openmls-lmdb-storage: An LMDB storage adapter implementing the OpenMLS storage traits

# orderedItems[].object.ephemeral.metadata[].description
An LMDB storage adapter implementing the OpenMLS storage traits - parres-hq/openmls-lmdb-storage

# orderedItems[].object.ephemeral.metadata[].ogDescription
An LMDB storage adapter implementing the OpenMLS storage traits - parres-hq/openmls-lmdb-storage

# orderedItems[].object.ephemeral.metadata[].ogTitle
GitHub - parres-hq/openmls-lmdb-storage: An LMDB storage adapter implementing the OpenMLS storage traits

# orderedItems[].object.ephemeral.metadata[].twitterDescription
An LMDB storage adapter implementing the OpenMLS storage traits - parres-hq/openmls-lmdb-storage

# orderedItems[].object.content
Integrating the shared jdt_activity_pub #RustLang crate used by the backend #Enigmatick server into the frontend #Wasm component. Necessarily broke a couple of Vodozemac functions, but those will be replaced by #OpenMLS shortly.

# orderedItems[].object.content
I'm redesigning my #E2EE architecture to use #OpenMLS instead of Vodozemac. Inertia seems to be with the former and I'd like to see #ActivityPub stay at the forefront.

I should have a working proof-of-concept soon. The big challenge seems to be with persistence; with Vodozemac, I could maintain a separate session record for each conversation. With MLS, all of the Groups are maintained in a single storage object for each user. And that storage is not designed with web server persistence in mind, so I've had to get a little creative. I think I can make it work.

You can follow along here.