Even if I had documentation to point the primal cache to a relay I host, it would just duplicate a ton of the data.. so inefficient. The goal is to have many relay operators to choose from. Otherwise, we’re all just playing pretend here. LARPing…
Hmm nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s said the primal server was proprietary but after looking further I found it here: https://github.com/PrimalHQ/primal-server
I don’t see anyone else running one, but technically relay operators could run this alongside their relay to service Primal users.
Although, it feels like a fork of nostr. Users can’t connect to normal nostr relays — therefore it isn’t backwards-compatible. The way we built Nestr was:
1) You can pull notes from normal relays
2) You can only pull the Merkle trees and blossom blobs from blossom servers and HORNET Storage servers
We preserved backwards-compatibility. Primal compromised on backwards-compatibility.
And there’s literally no documentation on how to change which relays the cache pulls from. 🤦♂️ It wasn’t built with other people easily running it in mind.
Discussion
No replies yet.