Because it's a protocol, not an app.

It’s got decent branding. Just needs to be polished into beta and beyond and then put into the hands of users. Staying on top of marketing helps - jumping on trending relevant events on X etc…

It is a messaging app and can be used for big groups. So most probably it catches reach with projects or companies announcing stuff to their followers in there. Or people who are already equipped with a nsec and happy to find a more capable DM-Application. You should not expect for any kind of application to get from alphatesting to mass adaption in a blink of an eye ;)

Maybe if it stopped being a honeypot and started being honest about the privacy and security limitations of being an app

So maybe if someone made another app on that protocol without the honeypot branding

Your website is pretty much marketed towards consumers, avoiding these technicalities. Is there an sdk or reference implementation for the message processing?

GitHub

Add NIP-EE: E2EE messaging using MLS by erskingardner · Pull Request #1427 · nostr-protocol/nips

Take 2! This NIP outlines a way to do secure direct and group messaging on Nostr using the MLS protocol. Easy to read

RFC 9420: The Messaging Layer Security (MLS) Protocol

Messaging applications are increasingly making use of end-to-end security mechanisms to ensure that messages are only accessible to the communicati...

Information on RFC 9750 » RFC Editor

GitHub

GitHub - marmot-protocol/whitenoise-rs: The Rust brain for the White Noise app

The Rust brain for the White Noise app. Contribute to marmot-protocol/whitenoise-rs development by creating an account on GitHub.

GitHub

GitHub - marmot-protocol/whitenoise: The White Noise Flutter app

The White Noise Flutter app. Contribute to marmot-protocol/whitenoise development by creating an account on GitHub.

https://github.com/rust-nostr/nostr/tree/master/mls