This looks kind of interesting, can't dig too much into right now on my phone, but is the idea just for signalling while the "rooms/channels" are empty?
I'm not sure what the point might be in that case.
Or is it a cloudflare service based websocket service?
I'll check it out when I have a chance at Which point I'll probably have some more dumb questions!
It's a HTTP polling based Cloudflare worker that can be used to establish WebRTC connections. A signaling service of some kind is always necessary to use WebRTC. The OP uses WebTorrent trackers which can work but have some limitations and ultimately have their own risk profiles.
The Cloudflare worker approach offers some unique tradeoffs that make it compelling relative to other options:
- Outage risk is reduced down to Cloudflare workers platform. (vs volunteer-run services like WebTorrent trackers)
- The costs are zero for a moderate level of traffic. (I intentionally designed the protocol for this project to take advantage of the cheapest available approach on Cloudflare, which is free in the best case.)
I'm not sure what the point might be in that case.
Or is it a cloudflare service based websocket service?
I'll check it out when I have a chance at Which point I'll probably have some more dumb questions!