3 ms·

After the move to WASM you can no longer use TCP/UDP sockets in your extensions and must rely on WebSockets/WebRTC instead, which is a shame. See https://develo

by mikevm 4y ago

After the move to WASM you can no longer use TCP/UDP sockets in your extensions and must rely on WebSockets/WebRTC instead, which is a shame. See https://developer.chrome.com/docs/native-client/migration/ https://developer.chrome.com/docs/native-client/migration/ (see the "PPB_TCPSocket and PPB_UDPSocket" section).

crummy 4y ago
You sort of can, if you don't mind piping your traffic through wireguard for example: https://www.youtube.com/watch?v=DNS4en4JyGo https://www.youtube.com/watch?v=DNS4en4JyGo
- mikevm 4y ago
  That requires another node... I want a direct connection to the outside.
- paulgb 4y ago
  Is UDP-over-WebSocket built in to WireGuard, or is this really tunneling browser <> WS/UDP proxy <> WireGuard?
exikyut 4y ago
Uhh... um, that's cough looking to change sometime soon. https://chromestatus.com/feature/6398297361088512 https://chromestatus.com/feature/6398297361088512 Part of me completely understands. The other half is looking at this like a deer in⠀𝙎 𝙋 𝙄 𝘾 𝙔 ⠀ 𝙃 𝙀 𝘼 𝘿 𝙇 𝙄 𝙂 𝙃 𝙏 𝙎⠀and absolutely facepalming...