Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of Jitsi and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
Jitsi rearchitects transcription and adds Document PiP as GSoC 2026 projects ship
Jitsi is modernizing its core infrastructure through Google Summer of Code 2026 contributions: distributed tracing now spans backend components, transcription has been rearchitected after nearly a decade on the Jigasi-based system, and Document Picture-in-Picture is available in browser meetings. The product is absorbing substantive capability work through its open-source contributor pipeline rather than a dedicated product team.
rtpengine opens the mr26.3 branch with a rollback message and leaner call state.
Sipwise's rtpengine media proxy opened a new mr26.3 branch on October 19. Its first build, mr26.3.1.1, carries everything from mr26.2.1.5 plus a rollback NG control message, relaxed loop detection for duplicate packets arriving over a second apart or from endpoints no longer local, ICE agent teardown when a peer drops ICE, inject-audio mixing fixes, and a long run of "lightweight string" refactors across call IDs, tags, SDP and recording fields. Three days earlier, a hardening batch went to four branches, followed by compile-fix releases.
Jitsi is modernizing its core infrastructure through Google Summer of Code 2026 contributions: distributed tracing now spans backend components, transcription has been rearchitected after nearly a decade on the Jigasi-based system, and Document Picture-in-Picture is available in browser meetings. The product is absorbing substantive capability work through its open-source contributor pipeline rather than a dedicated product team.
The transcription rearchitecture and distributed tracing suggest Jitsi is investing in the backend foundations needed to scale or extend to new use cases — potentially AI-assisted meeting features that require more reliable speech input. Document PiP extends the multi-window collaboration surface. The GSoC model means capabilities arrive in bursts aligned with academic timelines.
AI transcription or summarization features are a likely application of the new transcription architecture, given the investment in rebuilding it from scratch and the AI-meeting category trend.
Sipwise's rtpengine media proxy opened a new mr26.3 branch on October 19. Its first build, mr26.3.1.1, carries everything from mr26.2.1.5 plus a rollback NG control message, relaxed loop detection for duplicate packets arriving over a second apart or from endpoints no longer local, ICE agent teardown when a peer drops ICE, inject-audio mixing fixes, and a long run of "lightweight string" refactors across call IDs, tags, SDP and recording fields. Three days earlier, a hardening batch went to four branches, followed by compile-fix releases.
Development continues on two levels: correctness fixes backported across every supported branch, and newer work, such as the rollback message and memory-lighter call state, landing on the newest line. Opening mr26.3 adds a fifth maintained branch, so the backport load grows.
Expect mr26.3.1.x point builds and continued synchronized backports to mr12.5 through mr26.2. The entries don't show when older branches stop receiving fixes.
Other Meetings products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Jitsi or rtpengine.
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
HOMER 11.0.369 fixes S3 auth on Ceph-based storage and stops compaction memory growth.
Element Call starts moving to new LiveKit transports and falls back to remote SFUs when needed.
JW Player moves CMAF VOD into the dashboard, adds AV1, and opens Broadcast Live to audio-only feeds.
Nextcloud Talk Desktop 2.3.3 adds accessibility options and bundles Talk v25.0.6.
Nextcloud Talk patches v22 and v23 while v25 stable sits five weeks past its last RC.
See all Jitsi alternatives → · See all rtpengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Jitsi and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jitsi and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top Jitsi alternatives in Meetings are ranked by recent ship velocity. Browse the "Jitsi alternatives" section above for the current picks, or visit /alternatives/jitsi for the full list with editorial commentary on each.
Top rtpengine alternatives in Meetings are ranked by recent ship velocity. Browse the "rtpengine alternatives" section above for the current picks, or visit /alternatives/rtpengine for the full list with editorial commentary on each.