Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
HOMER vs PeerTube
A side-by-side editorial comparison of HOMER and PeerTube — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER vs PeerTube: at a glance
What is HOMER?
Homer's storage churn pauses long enough to ship a catalog backup CLI.
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held and told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog and added hours as a retention unit. 11.0.323 is the first quiet release in the run — a QoS chart axis fix for dashboard timezones, plus the catalog backup and restore CLI that shipped untagged in 11.0.322. Around these sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, and two inline GHSA fixes hardening node /query auth.
What is PeerTube?
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.
HOMER vs PeerTube: editorial side-by-side
HOMER
5.0MEETINGS
Homer's storage churn pauses long enough to ship a catalog backup CLI.
◆ Current state
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held and told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog and added hours as a retention unit. 11.0.323 is the first quiet release in the run — a QoS chart axis fix for dashboard timezones, plus the catalog backup and restore CLI that shipped untagged in 11.0.322. Around these sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, and two inline GHSA fixes hardening node /query auth.
◆ Where it's heading
Homer is stabilizing a storage rewrite by moving work out of DuckDB rather than tuning it further — native compaction merges in Go, outside DuckDB's memory_limit, and lets DuckLake alone allocate snapshot and file IDs, the exact behavior that corrupted catalogs before. A backup and restore path for the catalog is the logical next admission that the catalog is the thing most likely to break, and shipping it inside another release rather than tagging it separately fits a project releasing several times a week. Defaults stay conservative while each escape hatch is proven.
◆ Prediction
If native compaction holds up in the field, expect it to become the default engine and the DuckDB compaction path to be deprecated; the near-term releases will likely keep closing memory and catalog-locking edges around it.
PeerTube
0.0MEETINGS
PeerTube 8.2 spends its release candidates hardening instances against scrapers and locking down account data
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to HOMER and PeerTube
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 HOMER or PeerTube.
mediasoup
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
Mux
Every manual control Mux ships now arrives with a Robots workflow that does it for you
See all HOMER alternatives → · See all PeerTube alternatives →
Recent activity from HOMER and PeerTube
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3h agoHOMERCatalog backup/restore CLI ships; QoS axes follow dashboard timezone
- 1d agoHOMERNative compaction made safe for live catalogs; retention in hours
- 2d agoHOMERCompaction merge bounded after silent OOM kills on live catalogs
- 4d agoHOMERAlerts store the firing query and replay it in search
- 5d agoHOMERDuckDB memory caps raised so high ingest stops killing the engine
- 5d agoHOMERPer-user dashboard IDs unblock multi-user installs
- 2mo agoPeerTubePeerTube 8.2.0 release candidate 3
- 3mo agoPeerTubePeerTube 8.2.0 rc2: m4b audio, playlist hotkey, concurrency fixes
- 3mo agoPeerTubeDownload throttling, an NGINX fix, and a privacy deprecation for the accounts API ⚡
Frequently asked questions
What is the difference between HOMER and PeerTube?
They serve adjacent needs but don't currently overlap on shipped themes. HOMER is currently shipping more aggressively (velocity 5.0 vs 0.0), 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.
Is HOMER better than PeerTube?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HOMER is currently shipping more aggressively (velocity 5.0 vs 0.0), 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.
What are the best alternatives to HOMER?
Top HOMER alternatives in Meetings are ranked by recent ship velocity. Browse the "HOMER alternatives" section above for the current picks, or visit /alternatives/homer-voip for the full list with editorial commentary on each.
What are the best alternatives to PeerTube?
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.