Uncle Bob needs to check if his Lightning wallet is working: #[0]
It would need to keep an open connection to all nodes from all registered people and would turn into a very bloated thing and error-prone thing.
It's a great feeling when you spin up CLN and LND on regtest after 6 months using 5 different shells and your channels are still there online and working.
Let the user know what relays are being used and for what, let the user decide, make it not a hassle.
He does like Nostr, though, he states that clearly in https://www.youtube.com/watch?v=tg9S5KMQqBY
I don't understand how can I still see so many "@note1..." and "@npub1..." text in notes.
Clients could really just do a find-and-replace for mentions and references before publishing the events.
NIP-57 is simple, but satdress cannot support it currently since it doesn't know when the invoice was paid, and you can't have a separate address for zaps and lnurl because of the bad choices NIP57 made.
You may be interested in this: https://fiatjaf.com/3f106d31.html
I do think there should be porn relays, but we can't have these unless clients start to give users the option to treat relays differently, browse relays, allow users to pick and group and switch between relays, and expose a nice UX for users to publish different things to different relays.
The Nostros, Nozzle and Monstr clients have started playing with these things, I hope they get somewhere.
Today I learned from #[0] that https://codeberg.org/fediverse/fep exists. Which means even the ActivityPub propaganda boys are not very keen on going through the w3c standardization processes.
I don't know, I don't think there is a consensus. If you think that you can publish the zaps to the relays that have the note.
I think that will work in some cases, but not in others. For example, where do you read replies from? You can be following some profile on an open relay full of spam, but you don't care since you're only fetching notes from that person you're following -- but you don't want to fetch replies to that note from that same relay, since they will be all spam replies, you want to fetch replies only from safer relays, paid or with other antispam techniques built in.
Same could apply to zaps -- although zaps already have an antispam mechanism. If zaps had an indexed "m" tag (for "msatoshi") that could allow clients to filter out very small zaps and that would be better.
By the way, I don't think NIP-65 is a solution to anything or even required to solve anything. It is just one nice addition to the model. It worked already before without that, relying on NIP-05 relay hints, nprofile codes, relay hints in events and keeping track of things.
Watch this relatively old video, it is very enlightening: https://mikedilger.com/gossip-relay-model.mp4
Gossip model in action: 
Well, when you're sending a zap you want it to be seen, so your client must choose wisely where to publish that. I think you'll likely want to publish to places the readers of the note you're zapping are likely to read zaps from.
I also think big zap providers should want to host their own zaps (in addition to whatever they were told to publish to) and clients will know that and fetch zaps directly from them.
The provider, yes, it needs its own pubkey.
If zaps worked we could just zap your first note and that would count as crowdfunding actually.
No, not that!
I mean just put up a lightning address here so I can donate very little without being ashamed of donating very little.
Can you open up a crowdfunding place where a bunch of people can send small amounts and see if we can reach another $200?