Avatar
Basanta Goswami
46f6acdf9064234122fa080f5d9ef69573d791048e0b256630f8af296331b6e7
bitcoin maximalist • অসমীয়া ○ working on bitcoin stuff @ bullbitcoin.com ○ building other freedom tech stuff @ unsigned.in ○ teaching bitcoin @ xonghoti.com ○ helping with the tech side @ mim.inc कर्मण्येवाधिकारस्ते मा फलेषु कदाचन | मा कर्मफलहेतुर्भूर्मा ते सङ्गोऽस्त्वकर्मणि ||

Analyzing Chat Encryption in Group Messaging - Real World Crypto (RWC) 2025

https://www.youtube.com/watch?v=ghtMAmQCa5E&ab_channel=IACR

I DMed you using Primal (which still uses NIP-04 I think), not sure if you can see it

Replying to Avatar alp

✋ EU

Hey 👋

Let's have a private chat? I'm about to go to bed so I can talk to you tomorrow, but let me know whatever medium you prefer for DMs, I'll text you there

If you run a web development agency or are a freelancer in the US, EU, or UAE, ping me here or on Signal at basantagoswami.33

I run my own small agency here in India and looking for collabs on projects with other Bitcoiners

Fellow nostriches, any help in getting us connected will be appreciated 💜

What do you have in mind? We can upload any docs to blossom and sign a note with the URL

Replying to Avatar corndalorian

we should rename it to sex

Nostr apps distributed via Zapstore are the real dApps (or nApps?

Replying to Avatar Paul

Wow nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc you've really changed, is this what John Vervaeke would want?

lay off the acid gigi

Relays should have npubs too. Gets rid of reliance on DNS and TLS

when I first read the nostr NIP-01 I remember immediately going - wait, this is it? why didn't we have this already?

Primarily I use these tools for private communication:

1. Mail

For talking about a single topic at a time, threads in Discord server messages also kinda work for this thing. Different messages from the same user are treated as different matters. I need to be able to always have access to old conversations done in this way. NIP-17 seems ideal for this

2. Private DMs

I use WhatsApp and Signal etc for talking to people that I know. WhatsApp "feels" ideal in this case, because your identifier (phone number) is also a private matter. Here, I would like as much privacy as I can get, so NIP-EE (MLS) stuff seems ideal. I don't even necessarily want a single identifier for an app like this. I would much rather have a different identifier (I think SimpleX does that) for each person that I am talking to

3. Public Inbox

My Instagram, Twitter, Telegram and Nostr DMs are open for people to reach out to me, where I don't have to reply if I don't want to. Here my identifier is not a private matter. Most people also maintain two private/public mail IDs for the same reason. I would like to be able to go back and read all old messages here, so I think NIP-17 works better. A mail like UX won't feel right here.

4. Timely groups

I create or join a lot of groups on WhatsApp and Signal, for small timely topics like a discussion about a coming field trip with friends, or negotiation related to a freelancing project with the client. This can be better maintained via mail threads, but the only reason I prefer WhatsApp groups is because my mail accounts are full of spam, and conversations done in this way can be taken to a DM very quickly. Can't easily switch to a messaging mode in Gmail, and might miss something important. These also work as NIP-17 mails

5. Persistent groups

I join groups of Bitcoin communities etc, where I might not know or trust all the other participants. I wouldn't want to be directly reachable by other community members from these groups. I think I would prefer NIP-EE groups for this

The question is, how do you design all the UI/UX around all this stuff

Are their claims regarding their L2 Spark legit at least?

https://docs.spark.money/spark/spark-tldr

These claims seem way too good to be true, but if they managed to build what they claim, that would be at least one good thing coming out of this company