Stacker News and vida.page also offer Lightning Addresses with zap support right now.
Both services are custodial, though.
Agree.
And some lists being private and some being public.
Yes, I know that Lightning Addresses from several providers work as recipient for sats.
👍
Showing these payment proofs on nostr is what this "zaps" (NIP-57) is about.
Thanks for your work, btw!!
🫂
Afaict, right now the following Lightning Addresses services support NIP-57:
- strike.army
- Vida.page
- Stacker News
I guess they are working on supporting it (or at least studying about it):
- wallet of Satoshi
- getAlby
- Cash App
Agree.
I'm thinking lately how Zebedee could be improved very much integrating with #nostr for the identity and social part.
I don't know if #[2] could share with us any integration plan??
🫂🤞
#[6] has been giving some hints lately, and #[7] 's developer has been studying NIP-57 last days too, so I suppose both services could be working on it, yes.
🤞🫂
vida.page and Stacker News Lightning Addresses also support NIP-57 right now.
Just found out: Stacker News Lightning Addresses also support NIP-57.
vida.page by #[6] also supports it.
nostr.mom is a public relay that does some spam filtering.
You can try it in Global, if you want to.
That's how Amethyst works, afaik.
NIP-65 allows to report a user with kind1984:
https://github.com/nostr-protocol/nips/blob/master/56.md
I reckon some clients use these reports to hide/mute/block some pubkeys reported by some your follows.
No.
The zapper (zap provider) signs the events kind9735 with its own privkey, not the user's.
As far as I understand, the zapper sign the events kind9735 with its own privkey, not the user's.
What about integrating the Wallet with #nostr Contact/follows List??
Let the user set his npub in Settings, connect to some nostr relay and get his follows list. Voilà!
You have an updated Contact List ready to allow the user to send some sats to any of his contacts' Lightning Addresses.
Have a look to this tool to backup your follows list:
Just wanted to clarify some confusion I often see when users ask "how to verify yourself with NIP-05" kind of questions, because they used to think a checkmark means a user is verified.
As you correctly stated, NIP-05 just allows to add an alias to a pubkey.
Thanks a lot for your work and products, btw!
🫂
PS: when Alby NIP-57 support? 😉
NIP-05 doesn't "give you a checkmark".
That's just a #nostr client decision.
While some clients add a checkmark to users with NIP-05 defined (i.e. Damus), some others don't do that (i.e. Amethyst).
NIP-65 relays lists (our list and the user list) should be used when sending a DM (kind4) to a certain user, imo.