Jitsi Meet Desktop
A maintenance-mode Electron wrapper that reworked its window model and now gates remote control on consent.
A side-by-side editorial comparison of Fourwaves and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
Daily one-line releases, currently pointed at multi-event payment administration.
Fourwaves ships a near-daily changelog of single changes, which makes the shape unusually legible: small, specific work with no batching and no version numbers. The current window splits into two threads — transaction administration for organizations whose payments pool through a shared gateway, and event-day navigation for attendees. Nothing in the last ten entries touches architecture or pricing.
A tight patch train is still paying off HOMER's move to a DuckLake storage engine.
HOMER 11 is shipping point releases every few days, and nearly all of them touch the DuckLake-backed storage layer it now runs on: partition hygiene, snapshot expiry, tiered-volume reclaim, corrupt metadata detection. The capture and correlation side is getting real work too, most notably transitive B2B call-leg resolution. This is a project stabilizing a storage migration in public rather than adding surface.
Fourwaves ships a near-daily changelog of single changes, which makes the shape unusually legible: small, specific work with no batching and no version numbers. The current window splits into two threads — transaction administration for organizations whose payments pool through a shared gateway, and event-day navigation for attendees. Nothing in the last ten entries touches architecture or pricing.
The payment filters landing on consecutive days point at organizations running several events through one gateway, where the reporting problem is separating whose money is whose. Alongside that, the attendee path is being tightened — a live-and-upcoming view on the event home, adding presentations to a personal agenda straight from a session list. Both threads read as an academic conference platform maturing for organizations that run many events rather than one.
The transaction filters look mid-thread rather than finished, so the next step is most likely exporting or reconciling a filtered set rather than another filter dimension. The entries do not support a firmer call than that.
HOMER 11 is shipping point releases every few days, and nearly all of them touch the DuckLake-backed storage layer it now runs on: partition hygiene, snapshot expiry, tiered-volume reclaim, corrupt metadata detection. The capture and correlation side is getting real work too, most notably transitive B2B call-leg resolution. This is a project stabilizing a storage migration in public rather than adding surface.
The pattern across these releases is a backend that works but hasn't yet been made operationally boring. Storage bugs keep arriving from the field — future-dated partitions from bad RTPengine timestamps, obsolete files never physically deleted, corrupt table ids — which is what a young lakehouse layer under real VoIP capture volume looks like. Correlation and the coordinator API are where the actual feature work is landing, aimed at operators running multi-B2BUA chains and GitOps-managed deployments.
Expect the patch cadence to continue on storage correctness and retention until field reports thin out; the aliases CRUD API documented in 11.0.301 suggests config-as-code deployment is the next area to get real attention.
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 Fourwaves or HOMER.
A maintenance-mode Electron wrapper that reworked its window model and now gates remote control on consent.
3CX is rebuilding the PBX around MCP and a dedicated AI server, then letting admins self-serve the rest.
PeerJS keeps publishing release candidates that restate the same two fixes.
This feed is an archive of old Slack desktop releases, not current product news.
Discord is turning the chat client into a storefront and Nitro into a rewards program.
Meet is bolting consent controls onto the AI features it spent the last year adding.
See all Fourwaves alternatives → · See all HOMER alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fourwaves and HOMER 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. Fourwaves and HOMER 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 Fourwaves alternatives in Meetings are ranked by recent ship velocity. Browse the "Fourwaves alternatives" section above for the current picks, or visit /alternatives/fourwaves for the full list with editorial commentary on each.
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.