you would do it like lightning:
ws://pubkey@45.123.123.8:4444
maybe you would first fetch this pubkey from the relay metadata and use it as an optional faster and more secure mode of connection for future sessions (no tls overhead). wouldn’t work on the web but native apps would see a latency reduction on reconnections which happens a lot on mobile. nostr:note1f84rezwtnax5ctpvnrm30rc37gep5gassssv4yzelzvpfv2w9m6shju8ra
Thinking about bridging the web with the nostr-web:
Can you go forward using this as a URI and address resources on a relay? Or is this a step back because you would name the relay? Hm… definitely a step back.
And more importantly, the internet is permissioned because IP addresses have to be assigned. Nostr is permissionless because nsecs don't need to be assigned. We need to get away from IP addresses.
It's the original sin of TCP/IP.
Bring me my spear! O clouds, unfold!
Bring me reticulum relay addresses and client I2P integration XD
