mediasoup
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
A side-by-side editorial comparison of Nextcloud Talk and SRS — release velocity, themes, recent moves, and the top alternatives to consider.
The 25.0 alpha turns Talk toward classified channels and retention control — the stable lines only get call fixes.
Three tags landed the same day from different branches. The 25.0.0 alpha is where the work is: classified conversations, announcements and channels, an owner role with promote and demote, global message search across the conversation list, conversation preservation that restricts deletion and purging, a setting limiting who can start calls, an upload editor with image compression, combined file-share messages, and a multi-speaker call view. It requires Nextcloud 35. The 23.0.10 and 22.0.17 releases are lockstep backports carrying the same two external-call fixes — iframe permissions and room-creation hardening — under a large volume of dependency bumps.
SRS opens a 7.0 line built on a Go proxy tier, and drops features it no longer wants to carry.
SRS shipped the stable 6.0 line's first release on 12 August and, three hours later, the first development build of 7.0. The 6.0 line is now in pure maintenance — the r1 changelog is seven merges of DVR, WebRTC and edge fixes. Everything new is in 7.0-d0: RTSP playback, RTMPS, IPv6 across every protocol, HEVC in both directions between RTMP and WebRTC, and HLS fMP4 segments for HEVC and LL-HLS.
Three tags landed the same day from different branches. The 25.0.0 alpha is where the work is: classified conversations, announcements and channels, an owner role with promote and demote, global message search across the conversation list, conversation preservation that restricts deletion and purging, a setting limiting who can start calls, an upload editor with image compression, combined file-share messages, and a multi-speaker call view. It requires Nextcloud 35. The 23.0.10 and 22.0.17 releases are lockstep backports carrying the same two external-call fixes — iframe permissions and room-creation hardening — under a large volume of dependency bumps.
Talk is growing the structure that distinguishes a team chat product from a call tool: channels and announcements rather than only conversations, an ownership tier above moderation, and search that spans the whole list instead of one room. Running alongside it is a governance layer — classification, preservation against deletion, and restricting call initiation to named groups — which reads as organizations needing retention and access answers before they will replace a commercial platform. The stable branches meanwhile receive nothing but fixes, so all directional work is gated behind the Nextcloud 35 requirement.
The 25.0 line should proceed through further alphas and betas before a final, with the channels and classification work the most likely to change shape under testing. Whether the external-call hardening being backported twice reflects a deeper issue is not something these notes make clear.
SRS shipped the stable 6.0 line's first release on 12 August and, three hours later, the first development build of 7.0. The 6.0 line is now in pure maintenance — the r1 changelog is seven merges of DVR, WebRTC and edge fixes. Everything new is in 7.0-d0: RTSP playback, RTMPS, IPv6 across every protocol, HEVC in both directions between RTMP and WebRTC, and HLS fMP4 segments for HEVC and LL-HLS.
The project is trading breadth of legacy surface for a narrower, better-covered core. 7.0-d0 removes the embedded GB28181 SIP server, multi-threading, Cygwin, and most configuration hot reload, while introducing a Go proxy server and origin-cluster architecture alongside the C++ media core. Protocol coverage keeps generalizing — each release makes a codec or an address family a property of the server rather than of one delivery path.
Expect the 7.0 line to run a long alpha and beta train the way 6.0 did, with the Go proxy and origin clustering carrying most of the remaining work and 6.0 continuing to receive backported fixes in parallel.
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 Nextcloud Talk or SRS.
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
Every manual control Mux ships now arrives with a Robots workflow that does it for you
WebinarJam's feed is a funnel-marketing curriculum with no product releases in it.
See all Nextcloud Talk alternatives → · See all SRS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Meetings. SRS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. 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. SRS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top Nextcloud Talk alternatives in Meetings are ranked by recent ship velocity. Browse the "Nextcloud Talk alternatives" section above for the current picks, or visit /alternatives/nextcloud-talk for the full list with editorial commentary on each.
Top SRS alternatives in Meetings are ranked by recent ship velocity. Browse the "SRS alternatives" section above for the current picks, or visit /alternatives/srs for the full list with editorial commentary on each.