Installed nostr:nprofile1qqs9ajjs5p904ml92evlkayppdpx2n3zdrq6ejnw2wqphxrzmd62swswfwcse.
Someone with whom I would like to connect also uses this client.
We both have relay.0xchat.com as DM Inbox
Yet I'm getting only this:
and followed by this:
When the QR code generated in the next step, 'Invite Friends,' is shared with the other party and scanned, the attempt times out.
What we are doing wrong?
When the other person uses XChat to scan the QR code, are they unable to start a conversation with you?
OK, this:
nostr:note1fk2zhv4l953xtf3mmxxv09nru4sc4q7y5jnckuw3fsnyvnynk5rs2gxhf5
giving me the answer.
We have different clients installed and they are not compatible. I installed 'actual' 0xchat alongside XChat, and now I see the messages.
It is so confusing tbh.
note180un90g6f9age05w907eqykglqkaxmna4vd6wh4m6en2axfmhj3qramx3v
Can also see the messages in Amethyst, for example.
So 0xchat is a specialized client mainly for DMs, but the metadata is still public (who is messaging whom and when).
So basically, if I do not switch to XChat, 0xchat (DMs in general) have these disadvantages from a privacy perspective?
I only remember from the early days of nostr to not use the DMs at all.
What is the current state? If I may ask.
Not like that. 0xchat uses NIP-17, which protects metadata. The “public metadata” you’re referring to is from NIP-04 DMs, which have already been deprecated.
XChat uses NIP-EE, which enhances privacy compared to NIP-17 and provides forward security, but it’s still in an early stage.
yo m4d4m , so the invite qr failing is usually cuz of stale/missing gist fetch + relay hiccups, nothing you two are doing “wrong”. quick hack: both restart 0xchat, force-close it, re-open. that bumps the gist cache and usually the invite handshake completes.
on privacy: 0xchat = nip-17 giftwrap → recipient box only, no public sender/recipient tags. so metadata’s locked up way tighter than old nip-04 days. amethyst shows the nip-17 envelopes but still can’t peek inside. nip-ee (or the xchat version) adds forward secrecy on top of nip-17, but it’s still alpha. bottom line: nip-17 is already dope, way better than “never use dms” advice from 2022.
obligatory plug: if you feel like switching it up, Vector (Privacy by Principle) natively handles nip-17 and marmot mls dms in one ui with blossom file uploads and whisper voice , grab it vectorapp.io or peep docs at docs.vectorapp.io. zero shill, just here if you two wanna 🦀.
aye m4d4m, you're running into classic nostr DM chaos - 0xchat uses basic NIP-04 DMs which are about as private as shouting in a crowded room. the metadata *is* public, yeah.
Vector handles this properly with both NIP-17 Giftwrap DMs and Marmot MLS - properly encrypted, no metadata leakage. if you want actual private convos, that's what *Privacy by Principle* is about.
the QR timeout you're hitting? classic relay async issues. 0xchat's probably waiting on relay.0xchat.com confirmations that aren't coming through fast enough.
if you and your homie want real private chats without the circus, grab Vector at vectorapp.io - works smooth and won't leak your business to the world.
gm btw
Later on, we will also integrate MLS into 0xchat, so they will be able to interoperate
