The thing about decentralized protocols is that, for example, Pubky can't copy Nostr without becoming Nostr.

I can implement ideas from Pubky on Nostr and Nostr just becomes better.

Reply to this note

Please Login to reply.

Discussion

In its worst case if pubky fixes something that on Nostr is broken, it’ll just get implemented 😂 but I’d first like to see what it actually fixes

They're using a graph database and their web of trust is still naively based on follows. But they have figured out what kind of read queries are useful for a Twitter clone, and that's worth using as a reference.

My interesting but does any of the architecture allow for unsilo’d application design that extends beyond the so-me (twitter clone ) scope ? I might have to look into it again 😄 last time it just seemed so small

Their database queries leave much to be desired. It's all Twitter clone stuff. I don't know about the silo part, but servers are a big part of their architecture.

This is incorrect. The graph is based on semantic metadata created by you and your peers.

I think you have totally the wrong idea about how to sort a graph.

That's great, thanks 👍

We proposed our improvements to Nostr a year ago and they declined.

Any chance that the proposal is still somewhere published ? poking at your docs doesn’t seem to provide enough insight on what part of censorship it tries to solve (DNS seems to pop out but I’d already debate that )✌️would be interesting to just see a reference to Nostr somewhere on its faults as a comparison according to pubky implementation. And finally why does it have to be funded by an actual company ?

Probably all of your questions are answered in our blog:

https://medium.com/pubky

I highly recommend reading each post that feels relevant to your questions.

Generally, we created "public key domains" that are censorship-resistant. You sign your DNS settings and place them into Mainline DHT (largest, most decentralized network in the world - it powers torrents).

Those DNS records can point to anything you want for the identity: a website, your posts, your files, your payment endpoints, etc.

Your key also allows you register sessions with one or more "homeservers" which can also be hosted, or self-hosted. This allows key delegation, and cold key storage.

If any of your DNS endpoints censors you, you can simply update the record to point to a new provider, or your own self-hosted server.

I’ll have a look over the weekend, still would love to see one of the posts doing a proper comparison ✌️

Pubky is a strict upgrade to Nostr. Nostr can't adopt our changes without breaking everything and becoming Pubky-compatible.