Teable
Secrets get encrypted at rest while the computed-field engine keeps getting shored up
A side-by-side editorial comparison of HumHub and Nextcloud Desktop — release velocity, themes, recent moves, and the top alternatives to consider.
HumHub's public feed carries only betas, and 1.19's is still about surviving the upgrade.
The four releases visible here are all pre-release: 1.19.0-beta.2 and beta.1, and 1.18.0-beta.6 and beta.5 before them. The 1.19 line is dominated by upgrade-path and data-integrity repair — a foreign key violation aborting the comment content_id migration on databases with orphaned rows, fatal errors when purging content whose underlying record was gone, and in beta.2 a fatal SCSS build loop left behind when the 1.19 move of static/themes into protected/humhub stranded an empty theme skeleton. Beta.2 also fixes a real leak: activities from private spaces appearing in the summary mail and dashboard of users holding only a pending invite or join request.
34.0.2 arrives exactly as forecast: fifteen more backported sync-correctness fixes
The desktop client is running three maintenance trains at once — 34.0 as the new stable line, 33.0 and 4.0 as backport branches — and nearly every entry in the window is a bot-authored backport list rather than a feature note. 34.0.2 continues that shape with fifteen backports, weighted toward the failure modes that lose or duplicate files: deletion of server-side items excluded from sync, special characters preserved in chunked upload paths, placeholder directories no longer re-uploaded after remote deletion, stale chunked-upload chunks cleaned up, and new files syncing correctly on Windows. The rest is macOS tray and FinderSync behavior.
The four releases visible here are all pre-release: 1.19.0-beta.2 and beta.1, and 1.18.0-beta.6 and beta.5 before them. The 1.19 line is dominated by upgrade-path and data-integrity repair — a foreign key violation aborting the comment content_id migration on databases with orphaned rows, fatal errors when purging content whose underlying record was gone, and in beta.2 a fatal SCSS build loop left behind when the 1.19 move of static/themes into protected/humhub stranded an empty theme skeleton. Beta.2 also fixes a real leak: activities from private spaces appearing in the summary mail and dashboard of users holding only a pending invite or join request.
The 1.19 cycle is being spent making the migration survivable on real installations rather than adding capability, which is the usual shape when a schema and directory-layout change meets databases and webroots that have accumulated years of drift. Beta.2 extends that into the installer itself, where an unreachable database was offering to re-set-up a live instance during a transient outage. The permission and visibility fixes point the same way: tightening authorisation and content boundaries is cleanup of an existing model, not an extension of it.
Only beta tags appear in this feed, so a 1.19.0 stable is the obvious next milestone, but nothing here dates it. The beta.1-to-beta.2 gap of about a month is a faster rhythm than the roughly six months between the 1.18 and 1.19 betas.
The desktop client is running three maintenance trains at once — 34.0 as the new stable line, 33.0 and 4.0 as backport branches — and nearly every entry in the window is a bot-authored backport list rather than a feature note. 34.0.2 continues that shape with fifteen backports, weighted toward the failure modes that lose or duplicate files: deletion of server-side items excluded from sync, special characters preserved in chunked upload paths, placeholder directories no longer re-uploaded after remote deletion, stale chunked-upload chunks cleaned up, and new files syncing correctly on Windows. The rest is macOS tray and FinderSync behavior.
This is a correctness campaign, not a feature cycle. The recurring shape of the fixes — folder move/rename data loss, lock tokens invalidated on path change, placeholder directories resurrected after deletion, stale chunks left behind — says the team is systematically closing a class of sync-integrity bugs in the virtual-file layer that the macOS File Provider rewrite exposed. Three releases into the 34.0 line the composition has not changed, which suggests the class is larger than the rewrite itself and the team is still finding its edges.
Expect the same shape again: macOS File Provider fixes and Windows VFS path handling backported to 34.0.x, with the 4.0 branch taking only the applicable subset. Nothing in these entries points to a new user-facing capability landing soon.
Other Collab 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 HumHub or Nextcloud Desktop.
Secrets get encrypted at rest while the computed-field engine keeps getting shored up
Security and governance controls catch up to the Copilot build-out
A social-networking engine in careful maintenance across two supported branches.
7.1.3 ships on the Mac, closing a release spent almost entirely on rebuilding Feedly sync.
Hive keeps tightening the same three seams: planned time, admin control, and AI review scope
A dated canary most days, with the beta line carrying the same commits later.
See all HumHub alternatives → · See all Nextcloud Desktop alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HumHub and Nextcloud Desktop 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. HumHub and Nextcloud Desktop 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 Collab products to evaluate alongside.
Top HumHub alternatives in Collab are ranked by recent ship velocity. Browse the "HumHub alternatives" section above for the current picks, or visit /alternatives/humhub for the full list with editorial commentary on each.
Top Nextcloud Desktop alternatives in Collab are ranked by recent ship velocity. Browse the "Nextcloud Desktop alternatives" section above for the current picks, or visit /alternatives/nextcloud-desktop for the full list with editorial commentary on each.