awesome questions! There will be tech blog deep dive that goes into more detail, but just to clarify things a bit we are using h264 as the underlying codec but the protocol is a combination things -- h264 packets over websockets is where we started too!
Usually you want a "reliable" transport (tcp) for handshake, some transfer, etc and then you can get away with a more fire-and-forget (udp) stream for everything else. We broker different connections for different scenarios. The web version is naturally limited to either webrtc or websockets but for the paperweight it didn't make sense to force a web paradigm (or full webbrowser just to access limited socket types) so we interface directly with the hardware.
Haven't encountered big problems with firefox, but browser inconsistencies are definitely something we spend a lot of time working through
Because Paperweight is the black circle hardware device they made to stream from Paperspace. There's no point to using a browser on it, just stream directly through the wifi/ethernet port using TCP/IP.
Usually you want a "reliable" transport (tcp) for handshake, some transfer, etc and then you can get away with a more fire-and-forget (udp) stream for everything else. We broker different connections for different scenarios. The web version is naturally limited to either webrtc or websockets but for the paperweight it didn't make sense to force a web paradigm (or full webbrowser just to access limited socket types) so we interface directly with the hardware.
Haven't encountered big problems with firefox, but browser inconsistencies are definitely something we spend a lot of time working through