jb55 on Nostr: you would do it like lightning: ws://pubkey@45.123.123.8:4444 maybe you would first ...

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.

quoting note1f84…u8ra

Cool! This would grab a big part of infrastructure. How would you assign IPs to pubkeys?