Are you going on @rabble pod?

revolution.social - A Podcast About the Social Media Revolution

Join us as we explore the social media revolution and how we can build an open world for all.

Would you say the main disadvantage of signing everything is that you need a private key available in every interaction? If that issue didn’t exist, what do you think would be the main advantages?

It is a complex topic, but I think any advantage of signing everything is overstated, while the downsides are understated. It is true that signing can prevent data mutation, but it does not bring any other certainty with it, and there is little evidence of data mutation being an issue in the wild. The topic should be framed by problems that need solving, and best ways to do so. If you want more data integrity, you first need to establish authority of that data, like we do with PKARR. Then, you can do things like use versioned cryptographic data structures, or even more simply, data watchtowers. Then you have all the issues that come when you lose your key. How do people know when that key stopped being you? Now you have data signed by a real you and a fake you. Not very portable.

Thank you for the detailed reply! Any recommendation on where to read more about PKARR?

There are some great posts about public key domains, mainline dht, and Pubky in the blog here: https://medium.com/pubky/ Some docs about the system here:

Pubky Knowledge Base

Welcome to the Pubky Knowledge Base This is a knowledge base for the Pubky platform, which includes Pubky Core, PKARR and Pubky App. These document...

Code:

GitHub

GitHub - pubky/pkarr: Public Key Addressable Resource Records (sovereign TLDs)

Public Key Addressable Resource Records (sovereign TLDs) - pubky/pkarr

GitHub

GitHub - pubky/mainline: Simple, robust, BitTorrent's Mainline DHT implementation

Simple, robust, BitTorrent's Mainline DHT implementation - pubky/mainline

GitHub

GitHub - pubky/pkdns: DNS server resolving pkarr self-sovereign domains

DNS server resolving pkarr self-sovereign domains. Contribute to pubky/pkdns development by creating an account on GitHub.

Yeah, why do i keep hearing about it from podcasters but it's not even usable yet?

All of the code is open source. We have an app we are making with it, in invite-only beta. For now, basically anyone that asks can get an invite code.

Can I get an invite code?

Same, as someone building for nostr, id like to know what all the hype is about

You keep asking me questions but not learning anything. Also, stop quoting people, especially if they weren't even talking about Nostr; speak for yourself. Watch this if you want your answer. View quoted note →

Thanks for the video. Pubky exit: "all you need to do is update that DNS record, and the mainline DHT, and change your provider." (What does "change your provider involve? Copying data?) Nostr exit: "replace the relay in your relay list with a different one." Nostr exit can be accomplished in a web client without asking any trusted server to do anything. Relays don't have to be trusted *because* the exit costs are zero. You're right about relay centralisation concerns. Using the mainline DHT is a good solution. Seems like a useful thing to add to Nostr one day. I don't understand the value of putting pubkeys in the DNS. Is the problem there that you're worried about authorities censoring/stealing homeserver domain names? I notice that you can now get an SSL certificate for an IP address through Let's Encrypt. What about using the standard BitTorrent DHT mechanism to link to IPs instead of domain names? That's the whole purpose of non-mutable "announce" calls. Thank you for taking the time to answer my questions, I appreciate it.