libp2p QUIC is what I was alluding to here:
nostr:note1y25xxtm6mg42c9q0ard8tscljc6gqw3cwwmn0tpg6sxpm9c4elxszd887t
Yup, like libp2p QUIC.
You can see here how much faster QUIC is at establishing a connection than HTTPS. It’s because QUIC bundles the TLS into the first outward requests, reducing the number of round trips.
This QUIC model will already be built into GitNestr by default. Although, hornet storage will support the legacy wss:// method to ensure backwards-compatibility with clients who don’t upgrade.
This is what I’ll be tinkering with when trying the new outbox model later on, since it’ll already be built into the Hornet storage relay. Laying my cards on the table. nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c 
Discussion
By the way, we’re already running libp2p QUIC like this as we speak. This isn’t theoretical. We’ve already done it.
Wiring libp2p QUIC up to the outbox model with negentropy in the client will be an experiment we run, later on, soon after GitNestr is released… 🚀