Because of the increased interest in encrypted chat recently, I decided to put together a survey of different proposals with a summary of their common ideas. The goal is to allow us to 1. decouple different use cases from another, but keep a shared core that devs can build on, 2. get us all behind one proposal, and 3. pack everything into that proposal that is needed for good UX and privacy.

Please take a look and leave comments/corrections, and tag anyone else working on an implementation.

https://gist.github.com/staab/f8284af12450dbbdcead6e0c3ed95e2c

nostr:nprofile1qqs9nwtdlrvttent8w268cd6zkt4pfhd66duhwsc27htv549kgyt6kgprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqywhwumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wsq3camnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdswsu8t8 nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz3mhxue69uhkummnw3ezummcw3ezuer9wcq3wamnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5qs6amnwvaz7tmwdaejumr0ds7csnrk nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyv8wumn8ghj7un9d3shjtnwdaehgunpw35jucm0d5q3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnyv0c7x9 nostr:nprofile1qqs84k6jpsav0jmdeqjn2zxlpnsajaw6f8l0m2d4e9t8gjsyn53s4nspz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwxpuxx6rpwshxxmmdqyg8wumn8ghj7mn0wd68ytnhd9hx2u9umav

Reply to this note

Please Login to reply.

Discussion

So , whats the state of DM's , Group Chat , and general purpose nostr w/in nostr stuff ? Lets find out .

very cool ...

#asknostr #nostr

https://gist.github.com/staab/f8284af12450dbbdcead6e0c3ed95e2c

Nostr chat in Amysthest atleast is full of spam. Needs chat owners who can boot others out

Nice summary 🤙

Behind you 💯💯😜 and thank you for your time and efforts 💓🙏

Thanks for the summary

Thanks, great summary, this is very helpful for us in exploring a suitable NIP solution.

In my NIP101 implementation, the aliases between friends are not completely random(derived key). User A's alias private = shared key tweak added by A's private key, and User B's alias private = shared key tweak added by B's private key, so there is no need to change the alias key for friends here?

However, this is not suitable for large group chat scenarios. Group chats still need to change the group shared key to ensure forward/backward secrecy. I have a rough idea and am in the process of drafting it in the NIP :)

Thanks for the clarification, the most active conversation is on nip 24 (by Vitor), we'd appreciate any input you have there

You're missing that NIP that says "just use SimpleX".

🤝

It's on there, nip-lol

We are dedicated to making Nostr not Simple. :)

The thing I don’t like with simpleX is I can’t send a message easily to someone. For example, I can’t send you a message without first notify you I want to send you a message (except if you share your simpleX address to everyone, but you don’t)

With nostr I already have your public key so I can send you a message directly, then you are free to accept or notes sages from non followers

That's why I think we should try to integrate SimpleX with Nostr clients instead of just installing the app that exists. We could use Nostr to coordinate the messaging.

But to fair I don't really see DMs on Nostr either, so that thing about sending a message directly to anyone is not valid for me. Also you never know in which relays people are checking for DMs.

Interesting, SimpleX Chat is written in Haskell. Integration sounds useful.

I like what you said. I agree.

NIP 44 is describing how it works with NIP 65 for relay discovery

I hate auto correction so much sometimes.

*You are free or not to accept a message from non followers

The discusiion of private chat /encrypted group chat is in my timeline since the first day i joined nostr.

and everyone who is interested should check this note!

nostr:nevent1qqs83n0tyd3ugah9u8ekxrsmvaq6geqvjhtns6m2dmf4kvjdx8a8ylsp83mhxue69uhkummnw3ezuerpw3sju6rpw4ejcamnwvaz7tmwdaehgu3wxcurstn0wfnjcamnwvaz7tmjv4kxz7fwvcmh5tnfduuy9w9r

One thing I only talked about in that NIP-44 proposal PR that I think would fix 99% of the problems is allowing people to choose in which relays they want to receive DMs and have other clients publish DMs _only_ to these.

Yeah, maybe a worthwhile addition to nip 65