4 ms·
There is WebRTC code in the javascript source. It looks like some kind of POST/PUT code is used to exchange metadata about the files, but the files themselves d
by jeroenhd 5y ago
There is WebRTC code in the javascript source. It looks like some kind of POST/PUT code is used to exchange metadata about the files, but the files themselves don't seem to get transferred to the server.
Or maybe you're seeing different behaviour from everyone else because WebRTC is not behaving right and you're getting the fallback behaviour?
The "with no server involvement" part of the title is definitely wrong, this needs some kind of server to orchestrate the transfer itself. The server doesn't seem to receive the file contents, though.
- remram 5y agoThat sounds like a lot of "server involvement" to me.
- capableweb 5y ago> Or maybe you're seeing different behaviour from everyone else because WebRTC is not behaving right and you're getting the fallback behaviour? Could be. I've tried it in both Firefox (94.0.1) and Chrome (93.0.4577.63) on Linux (5.15.2), maybe they fallback based on OS if so? Weird, as other websites have no trouble using WebRTC with either Firefox or Chrome for me.
- Kiro 5y agoYou can't see WebRTC in the normal Network tab. Go to chrome://webrtc-internals/ and you will see the WebRTC action.