Tinode vs Slack
Side-by-side trajectory, velocity, and editorial themes.
Mature open-source chat server on a steady maintenance-and-tuning cadence
Tinode is shipping small, disciplined releases: a feature drop in v0.25.0 (chat pinning, subscriber counts, dark mode, in-call messaging) followed by bug-fix and dependency-maintenance point releases. Recent work is stability-focused — Postgres v5 and AWS v2 driver upgrades, CORS config, push-dispatch tuning. A v0.26 alpha line shows message reactions in development.
The arc is incremental hardening of a self-hosted messaging stack rather than expansion of its capability surface. Feature work lands in a minor version and is quickly followed by cleanup point releases; the reactions branch surfacing in the 0.26 alphas is the one forward-looking signal in this window.
The v0.26.0-alpha tags point to message reactions as the next headline feature to reach a stable release. Near term, expect further point releases shaking out regressions from the Postgres and AWS driver upgrades.
Slack is quietly rebuilding itself as a runtime for third-party agents.
Slack's developer platform has shifted its center of gravity from bots-that-reply to agents-that-act. The last month is dominated by agent primitives: apps can now receive the context a user is looking at, Slackbot can call external tools over MCP, and a dedicated agent messaging surface ships alongside steady CLI and Block Kit work.
Each release fills in a piece of an agent platform — context in, tools out, and a native place for agents to converse. Block Kit is gaining richer primitives (containers, data visualization) that read as the display layer for agent output. Three CLI releases in a month show the tooling keeping pace with the expanding surface.
Expect the next moves to connect these pieces: agent context feeding MCP tool calls, and Block Kit's new blocks becoming the standard way agents render results in-channel.
See more alternatives to Tinode →
See more alternatives to Slack →