WASM and WebRTC: Building for Browsers, Mobile and Servers with one codebase

Поделиться
HTML-код
  • Опубликовано: 7 окт 2024
  • НаукаНаука

Комментарии • 6

  • @mattanimation
    @mattanimation 4 года назад

    love it, I had seen Pion but didn't think about the WASM aspect

  • @jeffg4686
    @jeffg4686 2 года назад

    Have been looking into WebRTC for P2P connections, which is sweet. BUT, my only snag with P2P is exposing the IP Addresses to each other (network sniffer). It just seems like a security risk to me ... Why don't the ISPs have a service to allow NAT to occur at the ISP level (as well). A separate NAT of sorts that simply doesn't expose your public IP. Instead, it serves as the public IP, and respond back to your computer via your IP infrastructure that it knows about (since you sent the request). Seems like a no brainer to me. They could even charge money for this. Get the P2P and the security to boot! ISP even takes a profit. It's a three for. Call it "Secure Peer"

    • @maratmkhitaryan9723
      @maratmkhitaryan9723 Год назад +1

      Webrtc is not always p2p. When ip privacy is your concern use relays. Discord uses them.

    • @jeffg4686
      @jeffg4686 Год назад

      @@maratmkhitaryan9723 - Thanks

    • @jeffg4686
      @jeffg4686 Год назад

      @@maratmkhitaryan9723 - are you talking about TURN and/or ICE? If so, isn't that still p2p?

    • @maratmkhitaryan9723
      @maratmkhitaryan9723 Год назад

      @@jeffg4686 There are server forwarding units, which work as p2p party. When you use pion it may run behind nat on iot device, or on a server with a public ip. You can make all kinds of connections, you want. When sfu has a public ip you don't even need turn server. Ice will connect you directly to the server, without any stun or nat servers.