This is how we win.

nostr:nevent1qqst8v7whsm84hg5rd5lut8s5x6qu2t2an3pfxr3a6mkjd5ttxlxtugpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqzyrq7n2e62632km9yh6l5f6nykt76gzkxxy0gs6agddr9y95uk445xqcyqqqqqqgafdhsn

Nostr be-like:

forget what you know, open your mind to what's next

nostr:nevent1qqst8v7whsm84hg5rd5lut8s5x6qu2t2an3pfxr3a6mkjd5ttxlxtugpzpmhxue69uhkummnw3ezumt0d5hsygxpax4n544z4dk2f04lgn4xfvha5s9vvvg73p46s66x2gtfedttgvpsgqqqqqqsqkly4n

The idea here is to identify the relay with a uri something like thus:

wsn://npub1234....7890@[1001:1003:1003:1004::abcd]:8443

wsn://npub1234....7890@22.33.44.55:8443

wsn://npub1234....7890@centralizeddomainname.com:8443

wsn://npub1234...7890@torelayabcd...efg.onion:8443

Where the format is

wsn://@:

wsn: Web Sockets Nostr

The @ symbol could be changed to something that doesen't have an alternative meaning. Maybe #, %, &, ~ or whatnot

The only downside is it wouldn't play nice with reverse websocket proxies

This is how nostr:npub1exv22uulqnmlluszc4yk92jhs2e5ajcs6mu3t00a6avzjcalj9csm7d828 works basically.