pluggable (choose your own provider) metrics about pubkeys/events that are difficult or impossible to compute client side.
That I know.
I'm just curious about the actual use cases in products.
Most often that stuff can just be a hidden (interop) HTTP call that serves as a faster, better UX route for something that you have a Nostr basd fallback for.
Example: Whitelisting npubs for WRITE access in your XXXXX
1. Invisible to user: "Hey Vertex, is this npub good?"
If yes, auto-whitelist.
2. If no, visible to user: "Here's our Join form"
Then, if the whitelist is public. That IS the metric now. No need for assertions.
I'm just curious about the actual use cases in products.
Most often that stuff can just be a hidden (interop) HTTP call that serves as a faster, better UX route for something that you have a Nostr basd fallback for.
Example: Whitelisting npubs for WRITE access in your XXXXX
1. Invisible to user: "Hey Vertex, is this npub good?"
If yes, auto-whitelist.
2. If no, visible to user: "Here's our Join form"
Then, if the whitelist is public. That IS the metric now. No need for assertions.
1
