Teable
Secrets get encrypted at rest while the computed-field engine keeps getting shored up
A side-by-side editorial comparison of HumHub and pagedown — 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.
pagedown is down to one small fix a year, mostly absorbing changes from elsewhere.
The last six releases contain no new capability. 0.24 fixes missing horizontal rules under unnumbered h1 headers in the poster_jacobs format; 0.23 stops non-ASCII header text erroring during TOC processing; 0.22 drops a call to `xfun::attr()` before it disappears upstream; 0.21 sets an `is.paged.js` knit option so knitr knows paged.js loads its own JS and CSS; 0.20 raises the R floor; 0.19 patches a browser rendering regression with `overflow-x: clip`.
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 last six releases contain no new capability. 0.24 fixes missing horizontal rules under unnumbered h1 headers in the poster_jacobs format; 0.23 stops non-ASCII header text erroring during TOC processing; 0.22 drops a call to `xfun::attr()` before it disappears upstream; 0.21 sets an `is.paged.js` knit option so knitr knows paged.js loads its own JS and CSS; 0.20 raises the R floor; 0.19 patches a browser rendering regression with `overflow-x: clip`.
pagedown sits between three things it does not control — paged.js, headless Chrome, and Pandoc — and its release history is a record of each of them moving. The one release in the window with anything resembling design intent is 0.21, which lets other packages detect a paged.js context rather than guess it. Cadence has thinned to roughly one release a year, and the last genuinely new features (long-table headers, Sass support, streamed PDF transfer) are outside this window.
Expect another single-fix release triggered by a paged.js, Chrome or Pandoc change. Nothing here suggests new output formats are coming.
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 pagedown.
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 pagedown alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HumHub 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HumHub 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 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 pagedown alternatives in Collab are ranked by recent ship velocity. Browse the "pagedown alternatives" section above for the current picks, or visit /alternatives/pagedown for the full list with editorial commentary on each.