Yeah that’s what nostr:npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqz pkarr does as I understand it.

Is it your contention that basically the DHT is incapable of supporting that? So either the public keys will not show up or it’ll clog up and grind the DHT to a halt? That would be funny tbh

Reply to this note

Please Login to reply.

Discussion

Yes.

This is a good piece to read into, hopefully it will answer some of your questions - https://medium.com/pubky/public-key-domains-censorship-resistance-explained-33d0333e6123

The article doesn't address the scaling issue.

Pkarr does not require the DHT to change topology, neither do bittorrent peers need to change the topology of anything.

I think you are thinking about Pkarr as if it is a holepunching/NAT traversal thing. It is NOT, but neither is Mainline.

Mainline is literally a sharded routing table, just like DNS, but instead of a hierarchy, a flat distribution of routing servers (all of which have port forwarding no need for NAT) .

so now the question is, could one million small nodes cope with the 8 billion people updating their homeserver/hosting provider once a year each? because that is the only Publishing we need.

As for Reads, well just like DNS, we have to cache the shit of it, but that is ok, we only need the DHT to work well enough and caches be refreshed frequently enough just so your followers to detect your super rare event of change your hosting SERVER

Seriously, if the DHT can't scale for this, then nothing can and the alternative is just ICANN, if you think a 100 Nostr relays can scale better than a million nodes AND stay open and censorship resistant, I need you to explain that to me and walk me through what is the innovation in relays that we didn't have before ... because DHTs literally exists because Bittorrent trackers (exactly same as nostr relays) couldn't both scale AND stay permissionless.

I hope that makes sense.

And fuck IPFS and protocol labs, bunch of retards who spent millions of dollars just to destroy the reputation of good designs by horrendous implementations

Ah, that makes sense. So I take it that Pubky works differently from Holepunch’s HyperDHT? Or I probably misunderstood both actually lol

Yes, Pubky doesn't try to replace the cloud, just make domain names sovereign, because it is our position that the cloud most harmful aspect is your inability to leave without losing your identity, data and connections. but with sovereign domains, you have a credible exit that you can exercise when you need.