[_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.