I need to verify that myself though. I will try to find the code where this happens in some clients.

> They won’t show zap receipts from a custom domain, because they can be faked.

Very interesting 

kepford

> Even the prettiest girls or handsomest dude has a mole/freckle/birthmark/phobia/whatever

But they don’t have it in the center of their face

You're so bearish on nostr! 

Even the prettiest girls or handsomest dude has a mole/freckle/birthmark/phobia/whatever. Sometimes, it's not even a bad thing in context, is humanizing, and adds to the attractiveness.

k00b

Zap receipts are anyway dumb. The zap is between zapper and zappee - no one needs to know.

optimism

The primal wallet works just fine, I've tried it out

Educational_Stacker

aPolitical

As Kafka warned: *“The messiah will come only when he is no longer necessary.”*
I believe Nostr, LN, the whole web3 world, will end up building their own RBLs too. You just might call them “reputation graphs” or “verified relays.”
Clients will claim "you can use any relay!", but behind the scenes, 95% of content comes from a few blessed ones

Hence - A trusted node is a trusted god.

noknees

In 1997, Dave Rand and Paul Vixie, well-known Internet software engineers, started keeping a list of IP addresses that had sent them spam or engaged in other behavior that they found objectionable.

Word of the list quickly spread, and they started distributing it as a BGP feed for people who wanted to block all traffic from listed IP addresses at their routers.  The list became known as the Real-time Blackhole List (RBL).

Many network managers wanted to use the RBL to block unwanted e-mail, but weren't prepared to use a BGP feed.  Rand and Vixie created a DNS-based distribution scheme that quickly became more popular than the original BGP distribution.  Other people created other DNS-based blacklists either to compete with the RBL or to complement it by listing different categories of IP addresses.  Although some people refer to all DNS-based blacklists as "RBLs", the term properly is used for the Mail Abuse Prevention System (MAPS) RBL, the descendant of the original list.

I suspect nostr will have something similar for relays or npubs.

Good luck getting anyone to connect to your own relay when they are using clients that have a whitelist or connect to a trusted, centralized server to read events like Primal.

Afaik, this is already the case for LNURL providers. Some clients only show zaps if the zap receipt is from a trusted LNURL provider like strike.me or stacker.news. They won’t show zap receipts from a custom domain, because they can be faked.

security

> In 1997, Dave Rand and Paul Vixie, well-known Internet software engineers, started keeping a list of IP addresses that had sent them spam or engaged in other behavior that they found objectionable.
>
> Word of the list quickly spread, and they started distributing it as a BGP feed for people who wanted to block all traffic from listed IP addresses at their routers.  The list became known as the Real-time Blackhole List (RBL).
>
> Many network managers wanted to use the RBL to block unwanted e-mail, but weren't prepared to use a BGP feed.  Rand and Vixie created a DNS-based distribution scheme that quickly became more popular than the original BGP distribution.  Other people created other DNS-based blacklists either to compete with the RBL or to complement it by listing different categories of IP addresses.  Although some people refer to all DNS-based blacklists as "RBLs", the term properly is used for the Mail Abuse Prevention System (MAPS) RBL, the descendant of the original list.

I suspect nostr will have something similar for relays or npubs.

Good luck getting anyone to connect to your own relay when they are using clients that have a whitelist or connect to a trusted, centralized server to read events like Primal.

Afaik, this is already the case for LNURL providers. Some clients only show zaps if the zap receipt is from a trusted LNURL provider like strike.me or stacker.news. They won’t show zap receipts from a custom domain, because they can be faked.