aaron on Nostr: I've been thinking about implementing "virtual relays" in untethr.me code. They would ...

I've been thinking about implementing "virtual relays" in untethr.me code.

They would go like this. In your client, you would configure your relay to: `wss://nostr-relay.untethr.me/virtual/<any-string-you-make-up>`.

Then this becomes a silo, its own relay: only clients configured with this relay will see data from clients configured on this relay. (Unless of course someone consumes a message and publishes it again at the root relay or anywhere else.)

This will be really easy to implement efficiently (w/ no extra overhead) within the current relay code.

I'm not sure what clients do if someone were to configure multiple ones of these -- i.e., if a relay URL resolves to the same IP address. (Hopefully they just respect them.)

There are other variations of using URL paths to change behavior. For example:

`wss://nostr-relay.untethr.me/read-only`
`wss://nostr-relay.untethr.me/write-only`
`wss://nostr-relay.untethr.me/reactions-only`

...etc...

You get the idea.

Thoughts?