Primal clients connect directly to your list of relays for all publishing actions. We haven't yet implemented the relay settings UI; that's coming very soon.

When it comes to reading, Primal clients connect to our caching service. Our plan is to enable users to connect to any caching instance, as well as offer the ability to disable caching altogether, in which case all reading would be done directly from the relays. We view the ability to work with a caching service to be an optional competency that some clients can choose to implement, *not* as a replacement for connecting directly to relays.

Note that the entire Primal software stack has been open sourced under the MIT license, so everyone is free to modify it and further experiment with these techniques.

Reply to this note

Please Login to reply.

Discussion

Primal is my default now. Thank you for your service!

for publishing, how are relays selected by Primal, since atm a user can’t select which relays to use for publishing?

I used the "Save Relays Publicly" button in the Iris web app (https://iris.to/settings/network) to publish a list of relays to my public profile. Not all nostr clients appear to do that. I think many of them just maintain a private list of relays. I had previously only used Damus, Snort, and Coracle, and none of them had published relays to my public profile.

Primal seems to delete old notes? How long does the cache keep the notes? When it is reading does it fetch from cache + relays or only cache?

nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr Who can I talk to about the spam filtering in primal? ... I think you have false positives.