Me?
Mainly Amethyst, but testing some others.
Was this question really for me? 🤔
It looks like you have set a LNURL but not a Lightning Address, and I think Amethyst just likes LN Addresses:
https://nostr.band/npub1c878wu04lfqcl5avfy3p5x83ndpvedaxv0dg7pxthakq3jqdyzcs2n8avm
😞
Here's his newer pubkey: #[5]
Oh... 😞😞
Gossip model of using relays as explained in NIP-65 (0) or in the following picture:
(0) https://github.com/nostr-protocol/nips/blob/master/65.md
Ok, I think #[3] was simplifying the architecture, yes.
The LN node receiving the payment doesn't have to implement the zapper function by itself. It could ask another zapper to publish and sign the zap event, I guess.
I suppose nostr.band is using the zapper pubkey to identify a zapper, whatever the LN node receiving the Lightning transaction was.
Is it like that, #[3] ?
It could even improve a bit with the transaction list enriched with the zap information (sender/receiver name and pfp), imo:
😉
#[1]
Bueno, espero que los siguientes en transformarse en clientes nostr sean algunas de las existentes Lightning Wallets, que además de publicar los zaps (como ya hacen ahora) sean capaces de recoger info de nostr para enriquecer la lista de transacciones con ella.
Estaría bien poder ver directamente en la lista de transacciones de la wallet a quién enviamos ese zap y de quién recibimos aquel otro, con el nombre y foto de perfil actualizado.
A ver si se animan a implementarlo...
#[1]
Nice!!
Blog nostr 🚀 !!
#[6] would explain better, as those are their graphs from nostr.band , but I suppose he's counting unique zaps signers, as zap events are signed and published by the Lightning Address providers after the payment has been processed properly.
Zap senders and zap providers are interesting metrics to watch too::
And what's your opinion about this model?
Do you think it's better and interesting to go for it sometime in the future?
Yes, it could work in some cases when there's a known DNS domain and they want to announce which pubkey relates to the domain.
Companies could use to set the official pubkey, for example.
What I wanted to explain is that just having a NIP-05 alias set doesn't verify anything per-se.
Ask the author to publish it as long form content on nostr (0), and people will be able to read it and zap it on habla.news .
(0) https://github.com/nostr-protocol/nips/blob/master/23.md
It's just putting together already public information inside the Lightning Wallet's transactions list.
Many nostr clients already show this information. Next step is for the Wallets to show it too, imo.
Setting the npub in the wallet will ease getting the public zap events easily.
Showing the (new) private zaps would require setting the nsec, though. That requires more trust on the Wallet, true.
Lightning Wallets integrating nostr profiles enriching their transaction history page:
#[1]
I haven't tested Keet yet, sorry.
It looks much easier to set, as it's just installing an app, right?
Don't know how fluid it works on mobile, though. Is it a good user experience?
Could try to see if I can add something useful...
A private relay could be used to send private DMs between the family members using nostr, without leaking the metadata publicly.
There are more systems to do that, I know (i.e. private matrix server), but a nostr private relay looks so easy to set and maintain.