Dunno... I'm not convinced of that.
- In real life, it seems easier to use QR scan to add a new contact.
- In virtual space, it looks similar to copy-paste a npub than a domain name, imo.
Hey Lightning Wallets, you have done an amazing job integrating zaps!! 👏 Wonderful job!
What about stepping up your nostr integration?
What about allowing the user to opt-in to this integration defining his npub?
With that npub the wallet could get from nostr relays information about the user's sent and received zaps, and fetching info of the sender or receiver.
That information could be used to enrich the corresponding Lightning transactions history with the name and pfp of the sender/receiver.
What do you think?
Does it make sense?
cc: #[0] , Alby, #[1] , Stacker News , #[2] , #[3] , #[4] , #[5] , Strike(army), #[6] , etc.
So, a first step would be to educate the crawlers to get and use the relays metadata.
And later we can define allowed limits over there.
Do you know which crawler is misbehaving like that in order to ask it to properly use the metadata to identify uniquely your relays?
Out of curiosity, do every https://filter.nostr.wine/npub relay publish the same metadata (NIP-11)?
Or are some crawlers not making use of the relays metadata?
Exactly, but those checkmarks on pfp's in some nostr clients are confusing users to think there's some kind of verification involved.
Well, 10002 events are not for storing configuration settings:
"The primary purpose of this relay list is to advertise to others, not for configuring one's client."
https://github.com/nostr-protocol/nips/blob/master/65.md
I reckon storing client settings should be done in a specific "list" (maybe a private list) as defined in NIP-51 (still a PR).
Well, actually NIP-65 is not for storing client settings.
#[1]
I think NIP-05 aliases are far from being a must have!
Some people with personal registered domains may find it useful to add a domain alias to their pubkey.
Or maybe in a Company it could be useful as a way to announce their official pubkey.
But I don't see any value on it for the normal user.
I even think assigning a checkmark in the UI to every user with a defined NIP-05 alias is misleading and helping the spammers and scammers.
Stop giving a checkmark to every NIP-05 user. It's helping spammers.
NIP-05 doesn't equal verification.
#[0]
Is it published somewhere what nostr.wine considers "crawling responsible"?
What are the allowed limits?
Maybe this could be something to be announced in the relay metadata (NIP-11)??
Maybe people will then hide behind masks?
This reminds me to The Private Eye comic:
https://en.wikipedia.org/wiki/The_Private_Eye
Recommended! 👍
Yes, but the nice part of decentralised protocols is that there's no need to build all those features in a single app.
Imo, different functions should be distributed in several apps, all of them working together through decentralised protocols (nostr, Lightning Network, etc).
And each user choosing the preferred apps or services.
Microapps ftw!
It's very useful and explains already very well the idea behind the "gossip relay model", though.
Looking forward to the 'final' version!!
đź«‚
What's wrong with the self- prefix, may I ask?
Does the "$" really makes sense in a LN Address context?
I kinda understand it in a "$username" as a brand signal. But in a LN Address that brand is on the @cash.app.
It looks confusing, imho.
TIL about filter.nostr.wine .
Thanks! đź«‚
Nostr social clients are integrating the Lightning Network via zaps.
I'm looking forward to existing Lightning Wallets integrating nostr too!
Not as another micro social apps, but populating a Wallet Friend List with nostr Contact List (s) makes so much sense, imo.
Is self-custodial a word?
It could be much more than cosmetic.
Some badges could be used to tune spam detection algorithms (as the proposed Verified Human, for example).
Some badges could be used as passes to some exclusive features or services, etc.
Really a new world to explore.