webrtc-nuts-and-bolts VS jam

I recommend WebRTC For The Curious too, as another comment. Personally, I didn't use WebRTC in C#, but the WebRTC concepts are nearly the same in every different language/platform. Also, you can check out my project and documentation on internals of WebRTC, written in Go and JavaScript: https://github.com/adalkiran/webrtc-nuts-and-bolts . It's not related directly, but another example of usage at my other project, written in Go, Python, and JavaScript: https://github.com/adalkiran/distributed-inference .

I am heavily biased toward WebRTC. Here is my take on it though!

> It's incredibly complex as a specification

What is complex about it? I can go and read the IETF drafts, webrtcforthecurious.com, https://github.com/adalkiran/webrtc-nuts-and-bolts and multiple implementations.

QUIC/WebTransport seems simple because it doesn't address all the things WebRTC does.

> has limitations and numerous issues that set limits in how scalable it can be

https://phenixrts.com/en-us/ does 500k viewers. I don't think anything about WebRTC makes it unscalable.

-----

IMO the future is WebRTC.

* Diverse users makes the ecosystem rich. WebRTC supports Conferencing, embedded, P2P/NAT Traversal, remote control... Every group of users has the made the ecosystem a little better.

* Client code is minimal. For most users they just need to exchange Session Descriptions and they are done. You then additional APIs if you need to change behaviors.

* Lots of implementations. C, C++, Python, Go, Typescript

Show HN: WebRTC Nuts and Bolts, A holistic way of understanding how WebRTC runs\ (0 comments)

You can find it at: https://github.com/adalkiran/webrtc-nuts-and-bolts

Jam pro

Jam – Self-Hosted Clubhouse\ (40 comments)

Wow, I just woke up to this. Glad to see Jam here on hn. We've come a long way since the initial release earlier this year (Show HN: https://news.ycombinator.com/item?id=26131123).

Most of our efforts since february went into making the rooms more reliable which sounds simple but there are actually countless of different reasons for why audio might not work or not work as well as it could (switching from wifi to mobile data, microphone permissions, bandwidth problems, OS forces app into background, …) some are solvable others at least need to be documented and tracked.

What else is new other than reliability?:

# Support for large rooms (think: thousands of people in the audience) using an SFU

Initially Jam only had support for p2p rooms which is great for small rooms (up to like ~20 people depending on upstream bandwidth of the speakers) but for online conferences, meetups and so on you often need rooms that support 100s or 1000s of participants so we added an SFU where the speakers still send audio to each other p2p to keep conversations low-latency but we use a server to stream audio to all users that are in the audience.

(That said: you can still run Jam p2p-only if you prefer that)

# Locally recorded multi-track audio (think: podcasts with multiple guests, where you get one high quality audio track per speaker)

You can try multi-track audio recordings on our public beta server (https://beta.jam.systems). Tap on our own user and then "Start Podcast Recording". When you tap on your own user again and then "Stop Podcast Recording" the browser will prompt you with downloads for all audio tracks (we will make this more smooth going forward).

# Custom UI

For everyone who wants to add audio rooms to their own app but needs full control over the look and feel we have added an API and JavaScript library (and NPM package) so you can "build your own" ui for Jam. This basically means that Jam is running "headless" as an audio room server and makes sure audio works while you can build exactly the ui that you want.

E.g. let's say you have an app like Google Docs and you want to allow people to talk about a document. In this case you might want something that doesn't look like a room on Clubhouse or Twitter Spaces but rather like a line of avatars and with the API and library you can build this yourself now:

https://www.npmjs.com/package/jam-core

https://gitlab.com/jam-systems/jam/-/tree/master/ui/examples

# Managed hosting

For everyone who wants to use Jam but doesn't want to install and maintain Jam themselves we are run and support Jam for you (think: what Wordpress.com is to Wordpress.org):

https://jamshelf.com

I am working on an open source tool (Jam) that can be used to record podcasts with guests.