[wcarss]

I've been building an alternative around asynchronous audio, called heysync[0].

I can't stand being in long video meetings where everyone waits around smiling and one person talks forever. I also deeply miss the easy chats we used to have in the office, when we didn't have to schedule meetings just to talk. But I don't want to dedicate my time to sitting in a discord-like audio channel while I'm doing work.

So, heysync is the answer to my own problems. It has a similar feature set to IRC or to Slack, because I love those products, but it's built with asynchronous audio communication in mind, in a way a Slack app just couldn't provide.

You just talk, and heysync transcribes the message and stores the audio for easy playback. Your colleagues can either read or listen to what you just said. They can listen live, or later, so you can seamlessly talk even if the person you're talking to isn't there, or is multitasking.

0 - https://heysync.chat

(edit: I was downvoted pretty hard for contributing this -- if anyone wants to share why, here or via email at [e-mail], I would love to learn how to do so better.)

[_underfl0w_]

Not sure about the downvotes either. Your comment doesn't read as being any more "spammy" than similar comments hocking self-made projects on HN as alternatives to existing things. This fits my use case - having a team lead that can code and speak fine but has difficulty writing intelligible sentences in English. Sounds useful for e.g. slightly-less distracting pair programming too.

[Wowfunhappy]

I love these types of posts when they're clearly on-topic. With all respect to the author, this didn't seem close enough to the conversation at hand. A platform for asynchronous audio communication is not going to replace Slack, which is made for text messages.

If the GGP had said "I hate Zoom meetings where everyone waits around smiling and one person talks forever", the post would have made more sense to me. Or, if the GP's product can also function as a more basic Slack replacement, their post should have led with that.

[wcarss]

Ah, interesting! I'm intrigued that it didn't come across, so thank you for the feedback. My app is fundamentally a text chat client like slack -- with markdown support, reactions, channels, DMs, and at some point threads and bots.

It just also allows you to speak via audio, and captures that audio inline with the chat, in both audio and text form, which is the key selling point. It is visually and in terms of day to day use very similar to Slack, or IRC. My desire to build heysync is literally borne out of frustration that this featureset is not possible within Slack itself, which I use daily.