david on Nostr: I like that pubky has a semantic social graph and uses neo4j to power it. But my fear ...
I like that pubky has a semantic social graph and uses neo4j to power it. But my fear would be that pubky is falling into the trap of trying to build a cathedral, making the requisite underlying structure like their DHT more rigid than it has to be, which is a major critique in my mind of projects like IPFS and bluesky.
I’m guessing pubky users truly control their private keys and their identities, which is true for IPFS but untrue for bluesky which (I think?) holds users’ private keys.
The biggest strength of nostr (in addition to the fact we hold our private keys) is that nostr is resisting the cathedral trap, better than any other protocol that anyone is actually using.
But the nostr ecosystem lacks a semantic social graph powered by a mature graph database like neo4j. This really needs to happen.
I’m guessing pubky users truly control their private keys and their identities, which is true for IPFS but untrue for bluesky which (I think?) holds users’ private keys.
The biggest strength of nostr (in addition to the fact we hold our private keys) is that nostr is resisting the cathedral trap, better than any other protocol that anyone is actually using.
But the nostr ecosystem lacks a semantic social graph powered by a mature graph database like neo4j. This really needs to happen.