Rocket.Chat vs Tinode

The 8.8 candidate line is winding down. rc.2 is a bare Meteor version bump with no user-visible change, following rc.1 which promoted Voice Call Screen Sharing to stable and turned on the in-room call interface for every call, screen sharing available or not, alongside repairs to a message list that could quietly load a whole room's history in the background. The release that still defines the line is rc.0: LDAP and SAML deprecated on non-Premium workspaces with 9.0.0 named as the cutoff, forced end-to-end encryption for new private rooms, classification banners for ABAC-managed rooms, and the apps-engine default runtime moved from Deno to Node.

Two threads run at once and point in different directions. The calling stack keeps maturing on its own — voice, then screen sharing, now a consistent in-room surface for both — which is Rocket.Chat absorbing functions its users would otherwise reach for a separate tool to get. Against that, the 9.0 licence requirement for LDAP and SAML sorts the install base: regulated and government deployments that will pay, and unlicensed self-hosted workspaces that were there for the absence of a per-seat bill. The rc train itself has settled into a familiar shape, one substantive rc.0 followed by bumps and fixes.

Expect 8.8 to go final once the message-list fixes settle, with the LDAP and SAML licence requirement, not any calling feature, as the story of 9.0. The open question is whether the Deno-to-Node runtime switch surfaces app compatibility reports before then.