Show HN: Bema: Work messaging built for humans

Commenters saw Bema as an attempt to make work messaging less interruptive and improve its signal-to-noise ratio. Some welcomed the effort, saying they were burned out on existing messaging apps and would gladly use a better alternative. Others pointed to Derrick Reimer’s earlier Level project as a warning that the idea may be difficult to make work, and questioned whether employees or organizations would adopt another tool. A commenter nostalgic for IRC argued that protocol-based, user-chosen clients might have avoided today’s walled gardens; others countered that IRC had serious usability and reliability problems, and that decentralized tools are hard for ordinary workers to navigate.

Trust, integration, and conversation structure were central concerns. One commenter questioned granting Bema Slack access without a clear account of how data is processed; the developer clarified that Bema bidirectionally syncs selected public Slack channels and said the setup should be explained more clearly. Another commenter doubted that a different interface layered over Slack could work, since users’ habits and expectations are shaped by the platform itself. People also stressed that any replacement must handle threads and topics well, with one praising Zulip’s channel-and-topic model. Views of Slack itself divided: some described frustrating bugs and declining usability, while others felt its core experience had changed little and was not as bloated as Discord.