nip11: "virtual_paths" #1201
nip11: "virtual_paths" #1201
Conversation
|
I like it, do we have numbers on how many paths are spurious vs legitimately virtual? Mike was saying there were lots of paths pointing to the same relay, but I can't think of why. Examples would be useful. |
|
As far as I know filter.nostr.wine has paths for each pubkey and relay.nostr.band has paths for nip32-labeled content. I'm working on a relay with the sole purpose of having virtual relays of multiple types with a shared database. I was thinking of putting these in subdomains, but maybe paths are better. |
I know about those, I'm more wondering what an example of a path/qp that doesn't indicate a virtual relay would be. |
|
lgtm |
|
nice, this is useful |
| ``` | ||
|
|
||
| - `is`: this is `true` when the current path queried is a virtual path. | ||
| - `canonical`: this is the path that should be used when the client doesn't care about the virtual. |
There was a problem hiding this comment.
can we make this for moving domains also
| {"path": "/jp", "description": "only stuff in Japanese"}, | ||
| {"path": "/it", "description": "only stuff in Italian"}, | ||
| {"path": "/fr", "description": "whatever"}, | ||
| {"path": "/pt", "description": "blergh"} |
There was a problem hiding this comment.
what if I want to connect to multiple virtual relays at once? I feel like we need a way to handle multiplexing on relays eventually...
#1198 (comment)
This is just a stupid starting point just to get something concrete, please change it before merging @mikedilger @v0l @staab @nostrband