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 PeerTube and SRS — release velocity, themes, recent moves, and the top alternatives to consider.
PeerTube 8.2 spends its release candidates hardening instances against scrapers and locking down account data
The window is the 8.2.0 release-candidate train. The first candidate is the substantive one: Node.js 20 support removed, iOS below 15.4 dropped, an NGINX I/O fix for video downloads, and new configuration keys that throttle download bandwidth per instance and per IP. It also announces that the public /api/v1/accounts endpoint will move behind moderator authentication in v9. Later candidates fold in security fixes and two small features.
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.
The window is the 8.2.0 release-candidate train. The first candidate is the substantive one: Node.js 20 support removed, iOS below 15.4 dropped, an NGINX I/O fix for video downloads, and new configuration keys that throttle download bandwidth per instance and per IP. It also announces that the public /api/v1/accounts endpoint will move behind moderator authentication in v9. Later candidates fold in security fixes and two small features.
The direction here is defensive operations rather than new viewer-facing capability. Bandwidth throttling exists because botnets download entire catalogues, and the accounts endpoint deprecation is a privacy decision applied to the federation surface. PeerTube is optimising for instance admins who have to survive hostile traffic, and it is willing to break runtime and client compatibility to do it.
A general 8.2.0 release should follow once the candidate stream of security backports settles, with the accounts endpoint deprecation carried forward as a v9 breaking change.
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 PeerTube 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 PeerTube 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 0.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 0.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 PeerTube alternatives in Meetings are ranked by recent ship velocity. Browse the "PeerTube alternatives" section above for the current picks, or visit /alternatives/peertube 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.