Mine is this: note1lclyv0qwplty97fn4u0k5ns7w0uw8u7tswsa42lrsa2hajqdwmzskm690v

Let's try: ❓ How do these Zaps go through and being displayed beside posts? Does the sending or/and receiving ln wallet have to support Zaps? If yes, how does one know to which relay(s) the sending/ receiving wallet post corresponding notes? (As soon as I know how these Zaps work, I will Zap you sats for the explaining answer(s). 🧡

I remind people that Everyone's a Scammer, is this enough of a shill to you?

For example here: note17ksuq0zq2vptkp0eewnnenjr0rd5k9zn5q37scnanvhfhw803nssxhdkwn

I only found this and it doesn't look like the discussion has advanced over the point "interesting but not necessary": https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/1446

Thank you for the initial work! 🧡

I'd love to add:

"The message receiver can be specified by npub and the sending nsec will be generated by random every time.

Furthermore a small (between 0-30 seconds) random time delay between taking the offer and sending the nostr note should be added to avoid doxing because of timing analyses."

❓ Im not totaly sure about how the npub and nsec thing should be handled. Do you have another privacy friendly approach or thoughts about this? For example i could think of forced random nsec AND random npub receiver (for which robosata displays the nsec). Then nobody would come to the idea to use their main nostr identity but have to use one client with these burner nsec's to receive notifications. However this approach gets complicated if an user wants to have multiple offers open as a maker at the same time.

This statement doesn't age well under relay anarchy. 😆

the final push I needed to clear my Amethyst ( #[8] ) app storage and start fresh. Because my relay view shows a blank void for some time:

U r ✅

Yes I got 20k in total from you. Thank you. Do you want 10k back or can I send them all to the feature request creator?

She's scamming again. To bad she doesn't provide valuable work with her time. 🙈

lnbc100u1p37047fpp57ve5k2u4gq5d4qgeyzgvtjzx7fm229kacckp48jvptdntem38xfqdqu2askcmr9wssx7e3q2dshgmmndp5scqzpgxqyz5vqsp5lwgc3edtan2vg9xcxg2rmvefu8pp2t8cuynj2f204xusrtskvxrq9qyyssqzd8sctfakr2mzu5fhj6pntsyxqjvswezyw3nsyznqtj043q85cgkkxu8gl8gtz3k9rnpdgz0dtfjhlthec95hcyw4ktpfqe03avvtfgqc2nv8w

Yea, let's do this. Will be the easiest for all involved. You can use my profile lightning addres for this. I will keep you updated on the forwarding of the sats by tagging you in a nostr note when appropriate.

👀 WOW! Thank you! 🧡 Just to make things clear: Do you offer this bounty for the github user which opens the feature request or the user which implements this feature into the code base of robosats?

I hope for the same and at the same time I fear that we (the current nostr entities) don't separate our bitcoin maximalism from welcoming any kind of nostr entity, no matter what they like to produce as notes content.

May it be shitcoininers, spammers, fraudsters, criminals, corrupt politicians, anti-nostrs or even your neighbor your interacting just by lawyers for over 21 years. Everyone should be welcomed to use this open protocols because I believe that every entity should be allowed to communicate freely and I believe as well that every entity can change to the better over the course of their life.

Thank you for referencing the originsl post of #[5] . This was very helpful for me.

Thabk you for asking about the context.

#[2] did you know there is a chat room here on nostr as a meeting place for Samourai coinjoins?

Feel free to join us.

🔄 Join our channel *Make Every Spend A Coinjoin* #MakeEverySpendACoinjoin

ℹ️ Meeting place for #Cahoots spenders and collaborators to hook up and coordinate for transacting over Soroban.

➕ To join, just copy & paste this note id into the Amethyst search field and the first result is the mentioned chat room:

note13jks22x993fc6dz2rdzf25tfuqyf2mvtfcay55wkwz25l8qzdewqvzh43s

#[1]

sent. 🧡

"Keep up the good posts at nostr." #[0]  #[1] #[2] #[3] #[4] #[5] #[6] #[7] #[8] #[9] #[10] #[11] #[12] #[13] #[14] #[15] #[16] #[17] #[18] #[19] #[20] #[21] #[22] #[23] #[24] #[25]