web transport is a w3c web browser api which exposes the lower layer functionality of quic, like datagrams and bi/uni directional streams, to the web browser when it communicates with HTTP/3. i see several benefits for having lokinet's wire protocol use http3 over quic with webtransport capabilities for the datagrams:
passive DPI protocol camouflage, the ISP only sees HTTP/3-quic-tls traffic. ISP throttling will also affect other services like youtube so they (probably) wouldnt dare.
domain fronting. if you want to hide that you are using lokinet, you can set up a domain fronting bridge on a popular CDN.
a lokinet in the browser will become far easier. the wire protocol for lokinet would be native to the browser, if we need to overcome cors, we can have cors permit every single service node and/or we can serve a webpage from lokinet's inbound quic connectivity.
web transport is a w3c web browser api which exposes the lower layer functionality of quic, like datagrams and bi/uni directional streams, to the web browser when it communicates with HTTP/3. i see several benefits for having lokinet's wire protocol use http3 over quic with webtransport capabilities for the datagrams: