Avatar
Gunnar Stødle
198ae429b4fdfb7ad0d05c6877c3b2c7db5aedfff9794682fc52fd50e8cee27a
Mountain Man, Maker myrabbitholestory.com

Another option if you do not have access to extentions is to make an account at stacker.news you can log in with phoenix wallet. Chnage default user name to xxx and you got xxx@stacker.news as your lightning address.

Alby is a browser extention see getalby.com

You need to use a wallet that give you a lightning address like wallet of satoshi or alby. Phoenix do not work for this.

Haha yes, you wont give up and you will get it.

No thats not a lightning address. It's an lightning invoice. See the fucking lightning address website link above and read it!

Haha you fat finger boosted?

Get set up with a lightning address! https://lightningaddress.com/

Haha i see what you did there, zapping your self up the Amathyst feed.

We need to be able to comment share and zap songs without logging in to your web client. Open it up make wavlake nostre client. For the love of music, please no more walled gardens.

Vote with your money opt out of fiat, join bitcoin. Its the only way to fix this shit.

Tried to zap you back but it looks like you have just put a regular invoice in your profile and that does only work one time an expire. Try to put a lightning adresse there instead. If you don't have a lightning address you can get one in wallet of satoshi or Alby wallet extention.

Rereading A World in Debt Freeman Tilden 1935

I am impressed by the new zap enabled amethyst client! Amethyst has come along way since last time i tried it a couple of weeks ago. Time fly on nostr and the development speed is breathtaking. I have no doubt we will win the internet.

Did some more zap tests from amethyst.

Zapped my own note above using breez no problem.

Zapped a jb55 note using breez no problem.

This is good, i do not have a lightning enabled lightning address but it still worked but zap was not recorded in my zap tab.

jb55 have a zap enabled lightning address and it worked but no zap recorded in my zap tab.

Looks like anon tipping posts in ametyst still work and that is a great relief.

Now onto more zap testing :)

Testing amethyst's latest zap enabled client.

Trying to tip a post from Gigi who do not have a zap enabled lightnging address do not work. Prompted "User do not have a zap enabled lightning address."

Trying to tip a post from Jameson Lopp seemed to work and loaded the invoice into breez wallet but payment failed.

Not happy about the way this is heading. Zaps seems to break non nip-57 anon lnurl ipping on nostr. Not good.

I have been thinking about the complexity, user experience and privacy implications of NIP-57 zaps. Zapping involve having the nostr client doing calls to a users zap enabled lightning address service to make an invoice recording the event and npub of the payer.

Your payment will be linked to the event and your pubkey, not good for privacy.

If NIP-57 zap support become standard in most clients anon lnurl donation support like how it is today in nostr clients may suffer.

I am afraid Nip-57 Zaps will lead to a huge loss of payer privacy and centralisation around Nip-57 enabled clients, wallet and lightning address services that implement it.

Also i am not sure how anon tipping an zaps can interoperate when tipping posts. As i understand clients would have to support both methods, but how can that be done on the same zap button?

Its all very confusing. Especially since both Nip-57 and anon lnurl tipping are referred to as zaps by most users.

@jb55 et all please enlighten me if i am wrong here. Maybe we should pull the breaks on Nip-57 before we break user privacy and anon tipping on nostr?