Yet another Hacker News

Show HN: Bema: Work messaging built for humans

10 points ben_d 1 hour ago 11 comments

Hi HN! I'm Ben, the founder of Bema. I've been frustrated with the current state of work messaging software for a while now, and I've heard similar complaints from friends and coworkers. (Too many channels, easy to lose things, distracted from actual work.) I set out to build a platform that would encourage asynchronous communication with an option to break glass if needed. Here's the result, let me know what you think.

jon-wood 53 minutes ago | parent

While I applaud the sentiment here how many people work for an organisation that would be ok giving full Slack access to something like this, especially given the complete lack of information on how that data is being processed beyond an incredibly vague mention of Cloudflare in the privacy policy?

skinfaxi 28 minutes ago | parent

While I am of the same mind, many orgs have no idea what people are connecting to what. You can hook up slack with an unofficial mcp using tokens taken from your web session and your IT department would be none the wiser.

drcongo 50 minutes ago | parent

It says "Connect with your current messaging provider" and then never mentions that ability again. What does that look like?

Personally, I absolutely despise what Slack has become and would love to replace it, but I can't see anything about this app that might persuade me or my coworkers to install it.

edit: Don't mean to sound harsh about what you've built, but that page is not selling the app for you!

ben_d 45 minutes ago | parent

Thanks for the feedback! We support bidirectional message syncing with selected public channels in your Slack organization. You invite the app to public channels you want to sync and then we have a setup wizard to help you setup your organization in Bema. Can definitely make this more obvious in the marketing copy.

boxed 33 minutes ago | parent

I don't see how this can work even in theory. The shape of the platform always gets deeply ingrained in the behavior and even semantics of the users using it. Having radically different UIs on top of existing systems that other users might or might not see the same is fraught.

xnorswap 41 minutes ago | parent

> despise what Slack has become

I'm genuinely struggling to understand how slack is much different now than 5 or more years ago. There's a handful of features that are easy to ignore, but the fundamental experience has barely changed in a decade.

What is it about slack that you despise?

sgarland 27 minutes ago | parent

Same. It’s perhaps a little more bloated, but it’s nothing like what Discord has become, as a counter.

hmokiguess 18 minutes ago | parent

Signal to noise ratio is such a frustrating problem to solve.

I really wish you succeed and I will take whoever claims that space if they manage to do it right, I am burnt out from all messaging apps and utterly dissatisfied with where things are.

I wish we stayed on IRC, that was peak.

solyin 11 minutes ago | parent

No it wasn't. If you didn't have an irc bouncer there was no scrollback, mod abuse was rampant, netsplits were just a thing we accepted. It didn't work on mobile because they didn't exist back then. I'm not saying what we have today is any better, but let's not look at IRC with rose-tinted glasses and think it didn't have room to improve.

hmokiguess 9 minutes ago | parent

All that you're talking about are UX problems, had we stayed with the Protocol first and "bring your own client" I'm convinced life would have been better.

Everything nowadays is a walled garden behind a PaaS

solyin 16 minutes ago | parent

The no interruptions thing is neat but oh god, tags?

Zulip's got the channel/topic thing right. You join the #engineering channel and then there's the "PostgreSQL migration" topic.

Any new system has to not be shit at threads like slack is.