Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of PeerTube and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
PeerTube makes moderation federated: instances can now subscribe to each other's blocklists
The 8.3.0 candidate opens a new line and is by far the largest release in this window. Instances can subscribe to remote blocklists and watched-word lists that periodically re-sync, automatically muting accounts and servers and re-tagging existing videos and comments in the background, and an instance can publish its own blocklist as a public log for others to consume. A dense security block lands with it — cross-IP account login lockout, per-account rate limits on abuse and comment creation, OTP encryption moved to GCM, SVG sanitisation. The preceding 8.2 train was narrower: download bandwidth throttling and stabilisation.
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.
The 8.3.0 candidate opens a new line and is by far the largest release in this window. Instances can subscribe to remote blocklists and watched-word lists that periodically re-sync, automatically muting accounts and servers and re-tagging existing videos and comments in the background, and an instance can publish its own blocklist as a public log for others to consume. A dense security block lands with it — cross-IP account login lockout, per-account rate limits on abuse and comment creation, OTP encryption moved to GCM, SVG sanitisation. The preceding 8.2 train was narrower: download bandwidth throttling and stabilisation.
The through-line from 8.2 to 8.3 is that PeerTube keeps building for the instance admin rather than the viewer, but the unit of defence has changed. 8.2 handed a single admin local controls — per-instance and per-IP download throttles aimed at scraping botnets. 8.3 makes those defences shareable, so moderation decisions propagate between instances on their own, while new plugin auto-tagger registration lets classification be automated too. The security list reads like a post-audit sweep rather than incremental hardening.
Expect 8.3 to spend its remaining candidates on stabilisation as 8.2 did, with the manual migration script and the multi-minute startup migration the main upgrade risks to shake out. Whether subscribed lists get curation or trusted-publisher tooling isn't visible in these entries.
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 PeerTube 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 PeerTube 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. rtpengine is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 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. rtpengine is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 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 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.