Real Time Communications
Jitsi: 20 years of Real Time Communications
How the Jitsi project has adapted and remained current in the RTC industry for almost 20 years
<p>The Jitsi project was founded almost 20 years ago, under a different name and just for academic purposes.</p>
<p>Almost 20 years later, the project could not be in a better shape! It has gone through a name change and several acquisitions by large corporations, while remaining current in the industry and innovating all along.</p>
<p>This presentation will take a trip down memory lane and see where Jitsi came from, how it has managed to stick around for so long, and what the future holds.</p>
Additional information
| Type | maintrack |
|---|
More sessions
| 2/5/22 |
<p>What is new in WebRTC, what can we expect to see in the next couple of years? I'll describe some new APIs and speculate on how they might be used. I'll introduce whipi (an opensource implementation of the new WebRTC Ingest Protocol) and use it to illustrate how the WebRTC world is changing. I'll try to predict some new usages of WebRTC - niche high value apps. Finally I'll describe how to create a decentralized web (aka web 2.5) using the datachannel and existing browser technology.</p>
|
| 2/5/22 |
<p>The broadcasting industry has for years been dominated by a specific set of technologies (RTMP, HLS, etc.) that, while effective, suffer from high latencies and so are not always a good option. The IETF has started to look into WebRTC for that, starting from ingestion using the WHIP protocol. This presentation will introduce WHIP, some existing implementations, and how this could be expanded to distribute streams to a wide audience via WebRTC as well.</p>
|
| 2/5/22 |
<p>REST, the architecture underlying the web's protocols, has proven its benefits in creating a globe-spanning, decentralized information network. However, REST is showing its age - it was designed when surveillance capitalism, identity theft, information warfare, and other threats were largely hypothetical concerns. Unavoidably, REST leaves many of these issues unaddressed. Best practices fill some gaps, but may not be universally adopted.</p> <p>The Interpeer Project has been awarded a grant ...
|
| 2/5/22 |
<p>Our mobile devices have various apps that need updates from various servers at various intervals. Each app connecting to its own server on its own schedule, perhaps using inefficient technologies, can cause a lot of battery drain. Push Notification services are systems that can route all the important updates our devices need - whether they're instant message, VoIP, or social updates - into one shared channel.</p> <p>Unfortunately, the status quo in push notification services rely on ...
|
| 2/5/22 |
<p>Machine learning models have made it to the browser. Virtual backgrounds and background blurs are everywhere! Many recent developments including Tensorflow WASM backend, smaller ML models, pre-trained model repositories have enabled widely used virtual backgrounds and backgrounds blurs.</p> <p>This talk will explore how a simple background blur works, how developers can code their own blur for a WebRTC call, and most interestingly - what other ML/AI applications can be built using the same ...
|
| 2/5/22 |
<p>The cloud-native approach based on containerized micro-services has transformed the software landscape but is largely focused on non-real time web-based applications, especially in the case of service meshes which use web proxies to interconnect workloads. Media Streaming Mesh uses real-time media proxies to observe, route, encrypt and protect north-south and east-west media traffic.</p> <p>This talk introduces the Media Streaming Mesh architecture and its use-cases, gives an update on ...
|
