Pubkey is dyndns, and you serve content from your "home server". This is laughably censorable by any man-in-the-middle or casual DoS attack
Discussion
So your data only exists on your own server? I can't publish my data elsewhere?
Maybe you can? The main pitch is for "home servers", and the DHT only stores your key's current IP address
We're not going to have 8 billion home servers out there, so hopefully that isn't the case.
Please just read about it instead of associative guessing together.
It is normal dns format, but key-based dns, you can have mirrors, fallbacks, whatever setup you want.
The cool part is you have a definitive place to declare your endpoints, that no one can censor.
We set ours up assuming a primary homeserver, because this obsoletes the need for the relay model entirely.
I want to learn and I will spend some time reading and also we'll have a chat as you suggested.
Bro, nostr uses http and icann dns... just read this
https://medium.com/pubky/mainline-dht-censorship-explained-b62763db39cb
Yeah, and we should do something about it. But without signing events and distributing them you aren't anything approaching censorship resistant
Once you understand the design you will understanding why signing everything is not needed (but you could still do that if you wanted anyway...)
I designed distributed session management for the NYSE. I know *something* about whether signing everything is needed
Then i trust your learning will continue with Pubky.
"Smugky"
Call it what you want as long as you get in here :)
No, nostr is where I am
Let me know when I can post to pubky over Polaroid photo https://github.com/nostr-protocol/nips/pull/1500
Which side of the "Worse is Better" argument are you on, John?
Nobstr (Berkeley) vs Pubeky (MIT)...the right or best thing doesn't always seem to win.
Gimme an invite anyway 😬
