how to download & verify nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 on nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpzemhxue69uhhyetvv9ujuerfw36x7tnsw43z786xdyf.
https://blossom.primal.net/e686ce772c4130489a69a5dbf78b28f176a38c1e9e83794df9405ca5e663f7f1.mp4
Login to reply
Replies (12)
No need to use Obtainium, easier to tap on the download link! Good video tho
we did some zap tests on this note… we made one attempts to⚡zap this note, at zap@btcpay.ripsline.com, over a period of about 60 seconds. zero of the zaps were successfully paid... your server did produce invoices, however, we were unable to successfully pay the invoices. it may be that your node or wallet service was offline at the time we attempted the zaps. the actual error we got was 'route not found'... which is an unfortunately vague error that lightning payments sometimes produce. this means our payment node could not find a path to your node. (it could also be that your node was online at the time of payment, but did not have sufficient inbound capacity to receive payments.) 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.
hey! I doing maintence and changing my lightning address yesterday to zap@ripsline.com. it looks cleaner than the btcpay prefix. that's why it didn't work. can you test now?
did y'all actually want to help or just shill your custodial lightning service?
just tried it now, seems your lightning address is still invalid -- likely your server did not respond correctly
everything has been tested and is working as expected.
are you getting zaps from other users and are those zaps showing on your profile? we'll stop testing now as it seems you don't want us to continue
yes, receiving zaps from other users. happy to have you continue testing but hard to debug with the limited information. I tried to DM.
getting failures from jumble.social and yakihonne web, but from a command line tool no failure, my guess is a CORS issue 

thank you! I think you're right about CORS. I just implemented a fix, can you test it out? i'll zap you back.
just failed again from jumble.social... I actually recommend you set up a separate nostr profile and test from that.... zapping is a CORS minefield...
it's fixed. can u zap one more time please? thanks for all the help!