←back to thread

80 points pz | 2 comments | | HN request time: 0.445s | source

Hi HN, I’m Phil, one of the co-founders building emdash. Previously, I was an early engineer at Facebook and led Customer Products at Square.

We’ve focused on making chat and video work together so distributed teams can stay aligned without drowning in information. You can try it here: https://emdash.io.

It frustrated us how easily important conversations would happen and then disappear. Slack never quite matched how we worked. Channels were too coarse which led to noisy notifications and broken search. Zoom meetings weren’t much better–unless someone took perfect notes (which rarely happened), video calls became black holes of lost knowledge.

We spent too much time trying to find the information we needed to do our jobs.

To address this, we’re testing a few concepts and would appreciate your feedback on the value of the following:

(1) Automatically record, summarize, and transcribe your team’s video chats. We store meeting content directly inside discussions to facilitate search and discovery.

(2) Make it easy to manage & organize conversations of varying scope. A chat between team members can be forked into a dedicated Discussion with its own audience permissions and subscription. Individual messages or entire Discussions can be moved after the fact. Conversations can evolve unpredictably, so having the right tools to keep them organized post-hoc was important to us.

(3) Improve search with AI and hierarchical information retrieval. We use LLMs to uncover insights, summarize content, and connect the dots across related discussions, meetings, and documents. You can ask questions like “What are the team’s priorities this week?” or “What did we decide to do with feature X?” and get back a generative response AND deep links into the original chats and meetings.

Try it out: https://emdash.io and tell us what you think!

1. niutech ◴[] No.43186906[source]
Have you seen what is happening with Slack now? It's down for hours. Doesn't it teach businesses that the crucial instant messaging should be self-hosted for privacy & independence on 3rd party? Why would businesses use your hosted product instead of e.g. open source Nextcloud Talk, Element.io or Mattermost on their own server?
replies(1): >>43187070 #
2. wielrls ◴[] No.43187070[source]
Absolutely. If your team has the expertise and bandwidth, self-hosting Mattermost or similar tools makes a ton of sense. We may even explore a self-hosted version of emdash in the future.

That said, most customers tell us they’d rather focus their resources on their core business vs manage every tool themselves. Even those who’ve tried self-hosting haven’t necessarily seen better uptime vs Slack.