Send me a DM on Nostr.

Okay. Which kind?

Should it leak metadata?

Do you want that gift wrapped?

Should we use double ratchet Signal style over Nostr or should we use the MLS implementation?

Thanks!

Reply to this note

Please Login to reply.

Discussion

We need to onboard people who breed carrier pigeons. I'm totally serious.

Make nostr more like Ghost Dog: The Way of the Samurai

I just decided to stay with signal for now since we know wars are planned over it, must be safe, right???

Unless you invite the wrong dude... :-D

Double ratchet #Signal style, no metadata

Amethyst will be removing NIP-04 soon. This is great news because NIP-04 for DMs needs to go away, however this will also will make DMing people using Amethyst from Primal and Damus impossible. DMs are a cluster fuck, but it needs to happen. Sometimes you have to rip the bandaid off.

nostr:nevent1qqszm83tkwfm8l4expecdjehzuj249fv8xqjm4tp58gm5autly58hccprfmhxue69uhhxetwv35hgtnwdaekvmrpwfjjucm0d5hsygplwuxkt5a8vj5utj6s8tsj8e3wcavc45p4mqmw92qs7wrh5azmyspsgqqqqqqswrcjxl

Do we need a nip to specify a preference?

This just sounds like a bandaid fix.

until damus and primal converge on nip-17, there will be legacy-dms, the others have only one implementation so, or two that don't talk to each other

I'm just in the process of going down this DM rabbit hole. Still trying to figure out on how to configure my personal relay correctly for DMs. Its so messy, I'm kinda starting to like this chaos 😅 But damn, it's hard to navigate this...

To make it easy, I'd recommend using nostr:nprofile1qqs9ajjs5p904ml92evlkayppdpx2n3zdrq6ejnw2wqphxrzmd62swspzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2qghwaehxw309aex2mrp0yh8x6tpd4ehgu3wvdhk6ynf30t

Tried it, but still confused as hell 😅 Lets say me and Bob want to setup a relay that supports all the fancy chat functions, does that even exist? Stirfry? Nostream? Or all of them and its just a client thing using NIP-01 type... 🫠 just tried to open a secret chat, from one side it worked, but the other 0xchat client doesnt get anything, connected to the same relay

Are both of you using v1.4.7?

Yes

Can confirm it works on 0xchat. I setup a relay on nodana.io to test (takes a few seconds, costs a few cents per day, can stop anytime). Then I created a few accounts on 0x chat and added that relay only (app relay and DM relay, ignore inbox and outbox relays), and works fine with both MLS and NIP 17 chats. Just have to be on the right version both phones. Or you can use a single phone with app in the right version and swap between test accounts.

Tnx for the hint, will try again.

As long as it leaks war plans, count me in.

It leaks war plans in 12 different file formats, including pure GIF.

I’m diving back into the onboard client this week.

MVP = “Scan my QR for instant Nostr account and anon DM. Zero leakage. Zero config.”

Cross fingers I can get this done for live demo at BitBlockBoom. 🤞🏼

*6 months later than my first MVP deadline … for Riga!!

But hey… who’s counting?!

SSH Connection Parameter Combinations

• 2 protocol versions

• 10 common KEX algorithms

• 6 popular host key algorithms

• 8 common encryption ciphers

• 5 common MAC algorithms

• 3 compression options

•4 primary authentication methods

Total Possible Combinations:

2 × 10 × 6 × 8 × 5 × 3 × 4 = 11,520

Secret dm wrapped and then double ratcheted over MLS obviously 🙄

Thsts launching next year!