Syncthing
Syncthing 2.1.7 hits a fourth release candidate as fixes move from protocol to sync logic.
A side-by-side editorial comparison of AFFiNE and Joplin — release velocity, themes, recent moves, and the top alternatives to consider.
AFFiNE breaks a run of dependency-only canaries with a fix for blob uploads after quota changes.
AFFiNE is a collaborative workspace (docs, whiteboard, knowledge base) shipping canary builds across cloud, self-hosted Docker and native iOS/Mac apps. After five canaries of dependency work (piscina security patch, Node.js 22.23.3, Swift EventSource, ESLint v10, a broad dependency refresh), canary.921 fixes server-side blob sync: uploads read the current workspace storage limit, cancellation only hits the matching upload, and failed storage reservations retry more reliably. Before that came a stable iOS Share Extension, MCP Server visibility tied to Copilot, and config-driven OAuth and payment settings.
Joplin 3.7 ships AI chat, semantic search, and MCP integration — all off by default, all controllable by the user.
Joplin 3.7 is the product's first real AI release: an in-app chat panel for querying the currently open note, semantic (meaning-based) search across notebooks, and an MCP server that lets external AI assistants connect to Joplin's note graph. The implementation is privacy-first by design — AI is disabled by default, local models (Ollama, LM Studio) are explicitly supported, and cloud AI services only receive the specific note content relevant to a request rather than the full notebook. A companion documentation post published September 14 lays out the privacy model explicitly.
AFFiNE is a collaborative workspace (docs, whiteboard, knowledge base) shipping canary builds across cloud, self-hosted Docker and native iOS/Mac apps. After five canaries of dependency work (piscina security patch, Node.js 22.23.3, Swift EventSource, ESLint v10, a broad dependency refresh), canary.921 fixes server-side blob sync: uploads read the current workspace storage limit, cancellation only hits the matching upload, and failed storage reservations retry more reliably. Before that came a stable iOS Share Extension, MCP Server visibility tied to Copilot, and config-driven OAuth and payment settings.
The canary channel is moving from toolchain housekeeping back to product fixes, starting with storage and sync correctness on the server. The three active lines remain mobile capture, making Copilot and MCP switchable per deployment, and getting quota, payment and auth behaviour right for self-hosted and cloud workspaces.
A stable release bundling the iOS Share Extension and the recent storage fixes is the most likely next visible move; the entries don't show its timing.
Joplin 3.7 is the product's first real AI release: an in-app chat panel for querying the currently open note, semantic (meaning-based) search across notebooks, and an MCP server that lets external AI assistants connect to Joplin's note graph. The implementation is privacy-first by design — AI is disabled by default, local models (Ollama, LM Studio) are explicitly supported, and cloud AI services only receive the specific note content relevant to a request rather than the full notebook. A companion documentation post published September 14 lays out the privacy model explicitly.
Joplin is repositioning from a sync-agnostic note-taking app into an AI-native knowledge base, differentiated by opt-in, local-first controls. The HMD Terra M preload partnership and the warrant canary point to a deliberate push toward privacy-conscious enterprise and professional users who distrust cloud-first tools. The MCP integration is particularly strategic: it makes Joplin's note graph accessible to external orchestration pipelines without locking into any particular AI provider.
The next major release will likely expand AI chat to multi-note context — currently limited to the open note — and add more configurable MCP tools. The HTR (handwritten text recognition) project from the 2024 French government partnership is also likely to appear in a near-term release.
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 AFFiNE or Joplin.
Syncthing 2.1.7 hits a fourth release candidate as fixes move from protocol to sync logic.
Teable tries a chat-first workspace: the grid becomes one output of an AI conversation.
Elgg ships paired 7.1.2 and 6.3.9 patches: both branches stay in maintenance mode.
SiYuan's second 3.8.9 alpha in a day adds TIFF previews and depth limits for automation.
Hive gives clients a passwordless portal for every proof waiting on them, across companies.
GitHub previews a package firewall that blocks malicious dependencies at install time.
See all AFFiNE alternatives → · See all Joplin alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. AFFiNE and Joplin are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. AFFiNE and Joplin are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
Top AFFiNE alternatives in Collab are ranked by recent ship velocity. Browse the "AFFiNE alternatives" section above for the current picks, or visit /alternatives/affine for the full list with editorial commentary on each.
Top Joplin alternatives in Collab are ranked by recent ship velocity. Browse the "Joplin alternatives" section above for the current picks, or visit /alternatives/joplin for the full list with editorial commentary on each.