Interesting little fact about Nostr (we have a similar side issue on Hive).
If you log in with someone else's pub key you can't read their DMs but you can see who they've had conversations with.
Keep that in mind when using DMs on Nostr.
This is the problem with #nostr and anything else which doesn't have a viable business model baked into the core protocol.
https://podverse.fm/episode/EQra_C2y3
#VC capture. Today it's gifts from sugar daddy #[0] ... what next? All the VC's from failed "crypto" pile in because #Bitcoin?
Bitcoin is clearly the worst tech blockchain for storing NFTs or trying to do rollups of other chains.
But because sound money bitcoin maxis are so adamant that Bitcoin is the ONLY use of blockchain as a permissionless decentralised database which can succeed, their precious chain will be mutilated by use cases which should live elsewhere.
It's almost too delicious to believe my friends.
Here's why I won't be implementing NIP-57 and zaps on my LNURLp system.
I'm advising all my users to use a custodial lightning wallet like #[0] or hello@getalby.com because of the inefficiency of using my service for Zaps.
Hive users on #Nostr:
I've had a good look at the Zap system and it's not fully appropriate for me to add it to the Hive Lightning Bridge.
I suggest you get a Wallet of Satoshi account and use their Lightning Address system.
Still use v4v.app for NIP-05
Reasons: Zaps are often too small, I won't deal with zaps below 1000. It would also force me to join two systems which I don't want to join.
It also puts a big load on the receiving system, Let #[0] handle that.
Anyone needs more explanation let me know.