who needs signal
Discussion
๐๐ผ
Wow now that is very impressive.
I didnโt get the reply ๐ did you get the new msg?
idk whatโs going on but it broke my 0xChat lmao
yeah looks like an incompatibility nostr:npub1fgz3pungsr2quse0fpjuk4c5m8fuyqx2d6a3ddqc4ek92h6hf9ns0mjeck nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl
hmmm really nostr:npub1fgz3pungsr2quse0fpjuk4c5m8fuyqx2d6a3ddqc4ek92h6hf9ns0mjeck
Looks sweet
How does this work?
nip17 dm client. no metadata is revealed on relays.
Brilliant fuck yah!!
Thank you for working on this!
but you can't trust group messages, so ...
giftwraps are mainly 1 on 1
giftwraps are cool. I use them for secure backend channel communication for my app.
I'd say they are *only* 1 on 1, really. Unless among close friends.
nostr:naddr1qvzqqqr4gupzpg78lsd0mrjnpljpa54n6u36dkxg03yh8hp4zhaesz2cwetgyahqqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyehxjup3xukkwun0w4c8xttrdah8getcwskkjmn2v43hg6t0dckkzar5v93kktgp2jr7v
I need a desktop DM client so badly.
What's wrong with https://reya.su/coop ?
I lost a signal once when driving through a national forest. I indeed needed signal
Signal has perfect forward secrecy, nip17 does not. White Noise and 0xchatโs โsecret chatsโ have better mechanisms for forward secrecy.
That being said I still do not use Signal, because requiring a phone number is now a no-go for me. I donโt use any apps that donโt have public key identity now. For messaging I use Session, a signal fork that does not require a phone number.
yeah definitely, but you do get inbox relays so there is not a pile of encrypted messages in one place
we plan on adding forward secrecy in the future, but there hasn't been an established standard yet adopted by many clients. baby steps
Yeah. DMs on Nostr are an atrocious situation, thereโs like a dozen different ways to send a DM. Honestly the fragmentation makes mass adoption impossible. My client doesnโt support NIP-17 and I recently noticed Iโd missed a handful of DMs from friends when I opened a NIP-17 supporting client to receive my emails via nostr:npub1p5m98p05wn2tqffh0d9du6kjg8uy04g5485mgagxna56yrugd35qzvjnut
Imagine a normal person finding out that they didnโt receive messages addressed for them because there are multiple DM specs. They are going to come to the conclusion that Nostr is trash.
things just move slowly, once the tech gets built out it will all smooth over. it took awhile before I was able to get to even nip17 since I decided I needed to build a custom database first to ensure there were no performance issues ๐
Signal had a protocol spec from day 1 with nearly all basic requirements of a messaging service. Nostr has 2 NIPs, neither of which have been well thought out by someone who understands cryptography. NIP-17โs spec mentions โoptional forward secrecyโ but the author doesnโt seem to understand that forward secrecy means something in a cryptographic context or how it might be achieved. And if you have forward secrecy, why would you make it optional? Most messengers people actually use have forward secrecy as part of the protocol, with no way to opt-out. Signal, WhatsApp, FaceTime, and Facebook messenger. The only messengers that arguably do not have it are Viber and Telegram, the latter having it optional for its โsecret chatsโ.
โThings just move slowlyโ is a poisonous phrase in terms of making a widely adopted technology product. And it is less about moving slowly and more about people just going in completely different directions. Right now if things were moving faster, the ecosystem would just fragment faster. Thereโs not even an attempt to put developers on the same page or curate NostNostrents towards a reasonable standard. Itโs a clusterfuck.
Ideally, people would be seeking to copy White Noise, as it properly uses Double Ratchet (much like Signal and WhatsApp) instead of NIP-17. But even everyone agreeing to use NIP-17 would be better than the current situation, which is a multitude of incompatible methods that vary by the whim of each clientโs developer.
unfortunately integrating white noise is a lot more complex, giftwraps are more general for more use cases beyond dms, and are simpler to implement.
devs are time constrained, the slowness is more an economic reality even if its โpoisonousโ. Centralized dev can move faster of course and doesnโt have these issues of working with third parties and slower schedules.
The benefit is that each implementation keeps other implementations in line. Itโs harder to sneak through security vulnerabilities without being noticed by other clients.
Well, anything can be fixed as long as it is a open source protocol.
me, I like mobilecoin
Gibs please now
Weโve been waiting for this at nostr:npub1hxfkcs9gvtm49702rmwn2aeuvhkd2w6f0svm4sl84g8glhzx5u9srk5p6t for almost 3 years!