Can the nostr-mls library focus on core MLS functionality only?

[wcat7]

Hi, I’d like to ask if it’s possible for the nostr-mls library to focus on just the core MLS functionality? Specifically, it would be great if the library could avoid handling things like nostr event processing, messages,welcome storage, etc., and leave those responsibilities to the client.

Keeping the library lightweight and focused on MLS core would make it much more flexible and easier to integrate.

[yukibtc]

@erskingardner @delcin-raj

[delcin-raj]

Doing some major changes in the whitenoise crate. This will be addressed once I sort the issue I'm working on.

[erskingardner]

I think we need to think about this more before we make a change. The whole point of building the library in this way was to ensure that it's as easy as possible to integrate mls correctly. If a client integrated this wrong then it breaks the security guarantees for everyone.

[JSKitty]

The library would probably benefit from having less internal abstraction, given that's the job of the Nostr SDK (the high-level framework), right?

That said, I have no issues (personally) with how nostr-mls looks and I'll use it as-is, will be happy to dive in to it in the coming days and drop any feedback I have. Thanks for building this. 🤟