Because you are conflating PKDNS with a DHT-driven protocol. The events published in a homeserver don't populate across DHT at all. I haven't even looked at Pubky's protocol because it doesn't really matter in the context, since it doesn't operate like nostr in that capacity. The protocol is a modular piece of the stack.
You can also just run Pubky without pkdns and then boom you're dht-free and also just operating on clearnet DNS.
98% sure about this.
right, so why bother when there is so much nostr code already written to do this?
Nostr fails me lots but I use both and will continue to use both until I find something or create something that adequately meets my demands. I want to integrate NWC into Pubky if not a whole nostr relay so my homeserver can actually serve me instead of me trying to juggle a bunch of nostr relays.
NWC is a nostr protocol and is built around the use of a nostr relay as a rendezvous point between the wallet service (connected to the LN server), the relay, and the NWC RPC client which talks to the wallet service. your proposed integration won't work with a home service unless you have a VPS tunnel from an internet routable address with the wallet service to your home relay (like cody's pigeon service, or like how i have wireguard and lerproxy to run wss://test.mleku.dev on my dev box
Homeserver is a Pubky term. 😃☁️
