SiYuan
SiYuan opened a 3.8 branch and put AI agents, embeddings search and MCP in the first alpha.
A side-by-side editorial comparison of FreshRSS and EGroupware — release velocity, themes, recent moves, and the top alternatives to consider.
FreshRSS keeps turning a reader into a queryable archive — and hardening the parts that touch the web.
Two major releases and their bug-fix follow-ups define this window. 1.28.0 added sorting and filtering by user-modified date with a matching search operator, sorting by article length, an advanced search form, an overview of dates with the most unread articles, and API-level sharing of feed visibility. 1.29.0 layered on sort-order preferences at global, category and feed level, feed-provided icons, and a purge CLI. Security work runs alongside throughout — cURL restricted to HTTP and HTTPS, reauthentication in sudo mode, Content-Security-Policy frame-ancestors, and compliance with HTTP 429 and 503 including Retry-After.
EGroupware is pushing its old branch off a cliff on 15 August, and sweetening the landing with passkeys.
Releases arrive in pairs — one for the 23.1 branch, one for the current 26.x — usually within minutes of each other and usually flagged SECURITY. The 23.1 notes have carried an end-of-support warning for weeks; coverage stops on 15 August 2026. The 26.x side of each pair carries the actual product work: WebAuthN as a second factor, CalDAV timezone and recurrence fixes, invoice XML exemption codes, OpenID library upgrades.
Two major releases and their bug-fix follow-ups define this window. 1.28.0 added sorting and filtering by user-modified date with a matching search operator, sorting by article length, an advanced search form, an overview of dates with the most unread articles, and API-level sharing of feed visibility. 1.29.0 layered on sort-order preferences at global, category and feed level, feed-provided icons, and a purge CLI. Security work runs alongside throughout — cURL restricted to HTTP and HTTPS, reauthentication in sudo mode, Content-Security-Policy frame-ancestors, and compliance with HTTP 429 and 503 including Retry-After.
The feature line is consistently about retrieval rather than reading: search operators, sort dimensions, date overviews and per-level preferences all treat the archive as a queryable dataset instead of an inbox to clear. In parallel, the CLI surface keeps growing — purge policies, SQLite export with retention — which points at self-hosters automating maintenance rather than clicking through settings. Security fixes are steady and specific to the fact that a feed reader fetches arbitrary remote content, which is what makes the cURL protocol restriction and CSP work necessary rather than optional. Releases pair a feature drop with a fast bug-fix follow-up every time.
Given the pattern of a major release followed within weeks by a patch, and the steady expansion of CLI commands, expect the next major to continue extending search and automation surfaces rather than reworking the reading experience.
Releases arrive in pairs — one for the 23.1 branch, one for the current 26.x — usually within minutes of each other and usually flagged SECURITY. The 23.1 notes have carried an end-of-support warning for weeks; coverage stops on 15 August 2026. The 26.x side of each pair carries the actual product work: WebAuthN as a second factor, CalDAV timezone and recurrence fixes, invoice XML exemption codes, OpenID library upgrades.
The pattern is a forced migration executed through security cadence rather than announcement. Each paired release makes the gap wider: 23.1 receives the fix, 26.x receives the fix plus features, and the deadline text repeats. Underneath, the substantive work is authentication — WebAuthN, OpenID Connect verification fixes, email_verified handling — for a self-hosted suite whose buyers care about exactly that.
Expect one or two more 23.1 security releases before 15 August and then nothing, with the paired-release rhythm collapsing to a single 26.x train afterwards.
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 FreshRSS or EGroupware.
SiYuan opened a 3.8 branch and put AI agents, embeddings search and MCP in the first alpha.
The whistleblower hotline vendor is assembling a compliance suite, one module at a time.
Contract automation grows up: admin permission maps, 2FA, and forms that do their own arithmetic.
The knowledge graph quietly turned itself into a meetings product.
A minimal RSS reader that made passkeys the only way in, then went back to polishing the reading experience.
A Go bookmark manager rebuilding itself around an API — and only ever shipping release candidates.
See all FreshRSS alternatives → · See all EGroupware alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Collab. EGroupware is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. EGroupware is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 FreshRSS alternatives in Collab are ranked by recent ship velocity. Browse the "FreshRSS alternatives" section above for the current picks, or visit /alternatives/freshrss for the full list with editorial commentary on each.
Top EGroupware alternatives in Collab are ranked by recent ship velocity. Browse the "EGroupware alternatives" section above for the current picks, or visit /alternatives/egroupware for the full list with editorial commentary on each.