Primal displays nostr content, but isn't a nostr protocol client
Discussion
Yeah nostr frontend? I dunno what you would call it. If people want to use a frontend then fine.
clients themselves have variations within them: relay pool client, outbox client. Different ways to pull notes. I think this would be good to distinguish as well, then users could make an informed decision about that. fiatjaf is more interested in the latter for instance, which damus iOS currently doesn’t satisfy.
"Viewer"? "Proxy"? "Client-as-a-service"? 😂
maybe nostr gateway would be good. If the gateway goes down then you know you would have to switch to a client to get the raw data directly.
This is still probably going to be over the heads of normies unfortunately. but having words for it will be helpful at least.
I see .
I think gateway is probably a fair term. Then the caching service is acting as the gatekeeper for what is viewable via the gateway, which is an accurate assessment of how it works. You can, theoretically, use a different gatekeeper... if one existed.
Opera calls their analogous browser "Mini", and the backend a "compression proxy server"