John Davis

@wegylexy does anything prevent us from simply forking the repo?

@nibanks if we forked .net http/3 stack to make the webtransport changes, what are the downsides?

FYI https://kotlinlang.org/docs/reference/native/c_interop.html

Eventually, it should also be possible to route packets over the QUIC RTCDataChannel getting added to Chrome.

This would also create the need for a webassembly implementation of the HTTP2, HTTP3(QUIC), and websocket protocols. Initially, I think websocket protocol (over wireguard) should be pretty quick/simple. The others...

Yes! Let's do it! Does this need to be approved as a feature or something? Once we have a webassembly build, I'm thinking another repo could be dedicated to the...

If we get this thing working, and it catches on, it will beg a very large question. Browsers might be forced to introduce a vpn_wireguard_url w/ a vpn client embedded...

Wow, the future is starting to look a LOT simpler from a security perspective.

I wonder if we could get Mozilla to jump on board early.

Lol, to quote someone, "You wanna make a dent in the planet?"