4 ms·
https://wicg.github.io/local-peer-to-peer/#security-same-origin https://wicg.github.io/local-peer-to-peer/#security-same-ori... The W3C won't ever adopt a syst
by Rhapso 2y ago
https://wicg.github.io/local-peer-to-peer/#security-same-origin https://wicg.github.io/local-peer-to-peer/#security-same-ori...
The W3C won't ever adopt a system like this. They intentionally nerfed all local-loopback servers to never be able to effectively use websockets or ssl. That seems like a place to start before adopting this.
I honestly don't believe we will be able to meaningfully change or improve browsers without abandoning the w3c and starting standards over almost from scratch. Brave exists, but we would need to do better than that and design more general p2p protocols and systems.
- pthatcherg 2y agoWebRTC (with p2p) was done within the W3C, as was a p2p QuicTransport. And this new API is similar to the open screen APIs that have been done in the W3C. So I'm pretty sure work like this can be done in the W3C.
- Rhapso 2y agoTry making webrtc work without a domain name and ssl cert. It shipped compromised so it couldn't be used without giving the server the potential to mitm all connections. its not p2p in any sense except network efficiency.
- pthatcherg 2y agoI'm not sure what you mean. It does work without a domain name and SSL cert.