Using Jam is not the best way forward, IMO, because it's using another application's code base that you'd need to integrate with. The best path forward IMO is the rewrite, to rebuild the application from the ground up.
Hi nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424. In your view is the Jam Systems platform still the most viable starting point for a Nostr Nests re-write? Or are there other open source / web based audio conferencing platforms that are worthy of consideration?
Discussion
I see that Jam also offer an SDK, as a basic third party library... https://gitlab.com/jam-systems/jam/-/tree/master/ui/packages/jam-core
Something like that may save a lot of heavy lifting, and could significantly reduce the overall development time, in terms of of a re-write, but I take the point that you're inviting in a variable degree of uncertainty & bloat, by leaning on a third party.
It would be very interesting to get input from others on what they perceive as the best path forward, in terms of the technicals.
I wonder if a lightweight WebRTC implemention might be a reasonable starting point? Or am I overlooking newer/more relevant browser based comms libraries/APIs?
WebRTC for the audio portion seems like a great starting point.