bitcoinerrorlog on Nostr: I think you are mostly coming from a position of strictly trying to refute Pubky ...
I think you are mostly coming from a position of strictly trying to refute Pubky instead of actually considering it.
1. Impersonation - (I should first note that this is mostly an imaginary issue that isnt occurring in the wild, even on traditional web hosts. When people are censored, they notice, and are often directly informed! ...But your theory is sound, so let's discuss.)
Our Pubky app doesn’t sign everything, so yes, a homeserver could lie about tags or relationships. But you are ignoring a many things:
- You can run your own homeserver.
- You can sync your data locally, or on trusted servers.
- Despite everything in Nostr being signed, it still has some similar issues, because ALL hosts/relays/homeservers can decide which data to serve or not.
- With homeserver and indexer data being public, it is quite easy to detect any sort of inconsistency.
- Signing everything comes with problems of discovery that Pubky solves. How do people know exactly when your key was compromised or what your new key is? This is less likely to even happen to you in Pubky because your keys can be kept cold and separate from apps.
- There is nothing stopping anyone from building a Pubky app that does sign everything! This is not some sort of novel thing, but it does wreck usability and security for people, so we handle it differently in our app. If your way is better, build it and prove it. Nostr would certainly benefit from using pubkies instead!
2. Censorship - ALL HOSTS CAN CENSOR regardless of protocols. Just like Nostr relays can selectively censor or ban users, Pubky homeservers can too. The difference: Pubky gives you an actual credible exit default migration path (DHT), and anyone, including yourself, can easily mirror your data.
3. Ownership - You own your key, and your graph can follow you. But if you’re not self-hosting, you delegate trust—just like Nostr users trusting relays. Pubky users can tailor their redundancy however they like with backups, mirroring, self-hosting, alternate hosts, etc.
4. DHT scale/spam? Mainline DHT is literally the largest, most resilient, most decentralized network on Earth, and we took the time to prove it here: https://medium.com/pubky/mainline-dht-censorship-explained-b62763db39cb
1. Impersonation - (I should first note that this is mostly an imaginary issue that isnt occurring in the wild, even on traditional web hosts. When people are censored, they notice, and are often directly informed! ...But your theory is sound, so let's discuss.)
Our Pubky app doesn’t sign everything, so yes, a homeserver could lie about tags or relationships. But you are ignoring a many things:
- You can run your own homeserver.
- You can sync your data locally, or on trusted servers.
- Despite everything in Nostr being signed, it still has some similar issues, because ALL hosts/relays/homeservers can decide which data to serve or not.
- With homeserver and indexer data being public, it is quite easy to detect any sort of inconsistency.
- Signing everything comes with problems of discovery that Pubky solves. How do people know exactly when your key was compromised or what your new key is? This is less likely to even happen to you in Pubky because your keys can be kept cold and separate from apps.
- There is nothing stopping anyone from building a Pubky app that does sign everything! This is not some sort of novel thing, but it does wreck usability and security for people, so we handle it differently in our app. If your way is better, build it and prove it. Nostr would certainly benefit from using pubkies instead!
2. Censorship - ALL HOSTS CAN CENSOR regardless of protocols. Just like Nostr relays can selectively censor or ban users, Pubky homeservers can too. The difference: Pubky gives you an actual credible exit default migration path (DHT), and anyone, including yourself, can easily mirror your data.
3. Ownership - You own your key, and your graph can follow you. But if you’re not self-hosting, you delegate trust—just like Nostr users trusting relays. Pubky users can tailor their redundancy however they like with backups, mirroring, self-hosting, alternate hosts, etc.
4. DHT scale/spam? Mainline DHT is literally the largest, most resilient, most decentralized network on Earth, and we took the time to prove it here: https://medium.com/pubky/mainline-dht-censorship-explained-b62763db39cb