the page isn't loading for me, i get Uncaught SyntaxError: Unexpected token .
on bundle.js:25391
Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
11–20 of 69 posts
Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#12the page isn't loading for me, i get Uncaught SyntaxError: Unexpected token . on bundle.js:25391
Interesting, looking into it. Can you share which browser you are using?
Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#13wow this is incredible! How many concurrent users does it support?
Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#14the page isn't loading for me, i get Uncaught SyntaxError: Unexpected token . on bundle.js:25391
Interesting, looking into it. Can you share which browser you are using?
chromium
Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#15Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#16Nice work. What type of backend do you need in terms of servers/users if this was a real product? Clubhouse has been suffering under heavy load in certain cases. WebRTC is mostly P2P, but there is still a significant server load to handle edge cases and large rooms. You should show this off to Mozilla or some other web company that's backing WebRTC and try to get some funds for scaling up your servers if you need to…
Spot on. For larger rooms we will probably have to add mixing on the server side and that will definitely put more load on the server. We also want to make it super simple to spin up your own Jam for example if you are organizing a micro conference over a weekend and for that we will need to better understand what that means so we can recommend what kind of server/specs to go for. Thanks a lot for bringing this quest…
I highly recommend MediaSoup for this. It’s all node based and is great for creating “rooms” from WebRTC connections.
Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#17Earlier quoted context omitted.
Spot on. For larger rooms we will probably have to add mixing on the server side and that will definitely put more load on the server. We also want to make it super simple to spin up your own Jam for example if you are organizing a micro conference over a weekend and for that we will need to better understand what that means so we can recommend what kind of server/specs to go for. Thanks a lot for bringing this quest…
I highly recommend MediaSoup for this. It’s all node based and is great for creating “rooms” from WebRTC connections.
Thanks for the pointer!
Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#18wow this is incredible! How many concurrent users does it support?
Thank you.
That's a great question. Our current setup is p2p WebRTC and should scale to many small rooms (up to ~12 people) fairly well. That said, there is a TURN server for NAT traversal and a signal server for coordination.
We'll try to get a better picture of where the limits are this week. I don't have a good answer atm to be honest.
Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#19Looks like a just wrtc "helloworld" example from MDN.
Re: Show HN: Jam, an Open Source Clubhouse (w/ WebRTC)
#20Nice work. What type of backend do you need in terms of servers/users if this was a real product? Clubhouse has been suffering under heavy load in certain cases. WebRTC is mostly P2P, but there is still a significant server load to handle edge cases and large rooms. You should show this off to Mozilla or some other web company that's backing WebRTC and try to get some funds for scaling up your servers if you need to…
Spot on. For larger rooms we will probably have to add mixing on the server side and that will definitely put more load on the server. We also want to make it super simple to spin up your own Jam for example if you are organizing a micro conference over a weekend and for that we will need to better understand what that means so we can recommend what kind of server/specs to go for. Thanks a lot for bringing this quest…
Amazing work! The WebRTC community needs something like this so bad. Not only will this push a bunch of users toward self-hosted/free software but will also inspire others to build cool things :)
If/when you hit scaling challenges I would love to help! I maintain github.com/pion/turn and github.com/pion/webrtc. One of the reasons I built it was so that I could put my TURN and Signaling server in the same process. It makes it way easier to tie your auth together for signaling+TURN. Then if you do go down the SFU route lots of interesting things you could do. You can see that with how screego[0] does it.
Happy to help however I can (even if not using Pion!)
[0] https://github.com/screego/server/blob/e845b3d29c4b5794ed10f...