It seems you never tested your stuff. The console is full of errors:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194. (Reason: CORS request did not succeed). Status code: (null).
None of the “sha512” hashes in the integrity attribute match the content of the subresource. -oXZ36ekQX2btnYIZSdj2g
WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. chunk-vendors.9d9d262d.js:6:31482
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194. (Reason: CORS request did not succeed). Status code: (null).
None of the “sha512” hashes in the integrity attribute match the content of the subresource. -oXZ36ekQX2btnYIZSdj2g
Some cookies are misusing the recommended “SameSite“ attribute 4
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://416c35e0.hyperbeam.com/ok?vm=0. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.
Object { type: "New", payload: {…} }
app.fc7f578d.js:1:42733
Object { type: "Create", payload: {…} }
app.fc7f578d.js:1:42733
WebRTC: Using more than two STUN/TURN servers slows down discovery 2 vendorlate.27cb1e73.js:14
WebRTC: Using five or more STUN/TURN servers causes problems 2 vendorlate.27cb1e73.js:14
Object { type: "Consume", payload: {…} }
app.fc7f578d.js:1:42733
Consume error: cannot consume1
The "cannot consume1" is the error that shows also on the three.js demo.
still_grokking|3 years ago
First of all some spyware stuff from cloudflare gets blocked by the ad-blocker.
But this is not the root of the problem as it doesn't work either without the ad-blocker active.
Minified JS Script dies with some cryptic backtrace.
I've tried on the hyperbeam.com website and it does not work either.
It lies straight in my face about a missing H.264 codec. (Which works fine according to https://test-videos.co.uk/bigbuckbunny/mp4-h264).
It seems you never tested your stuff. The console is full of errors:
The "cannot consume1" is the error that shows also on the three.js demo.ambyjkl|3 years ago
Seems like in Firefox, H.264 in WebRTC is supported in an entirely different fashion than other kinds of H.264, like in an MP4 file.