Thread

My first thought was like "why would rust-nostr add support for highlights?" nostr:nprofile1qqsznh4gvuh5fmgkf07g8kea5k75wgqp4acrql6zyam8fj7xf5esz0spzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzemhxue69uhhwmm59ejx2un8d9nkjtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09ufrlyjs legit broke my brain 😭😂

testing zaps for this note… we made six attempts to⚡zap this note, at pay@yukikishimoto.com, over a period of about 2 hours. six of the zaps were successfully paid... please check for 6 satoshis received. problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (the zap spec requires that the zap receipts be sent to the relays specified in the zap.) this means a nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.

Is whitenoise/Marmot protocol already available in the bindings of rust-nostr? Tagging nostr:nprofile1qqspwwwexlwgcrrnwz4zwkze8rq3ncjug8mvgsd96dxx6wzs8ccndmcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxrhwden5te0ve5kcar9wghxummnw3ezuamfdejj7ekel7y

Nope - we've moved all the Marmot stuff out into it's own library, MDK. https://github.com/marmot-protocol/mdk

OK. Looking forward to python bindings.