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.
for publishing, how are relays selected by Primal, since atm a user can’t select which relays to use for publishing?
Please Login to reply.
We simply respect the relay list you configured in another client.
What about new user who have never used another client?
