jeremyis
Joined 16 years ago
Joined 16 years ago
We recently evaluated play.ht for TTS but decided against it because you had an async API which was harder to implement. Alternatives have sync APIs (including Google Cloud). Do you have plans to release a sync client for standard TTS?
Looks helpful! What else is on the roadmap?
I also feel like when I share the screenshot - via slack, the million messaging clients my various friends / colleagues use, etc. - the context and convo is often lost.
I see the value here in unifying that data in one place - instead of the screenshot, I can just share a link and then go and find all the screenshots somewhere. I like that. Actually, now that I think about it, if you set the `og tags`[1], chat apps should also make an image preview when you paste a link (maybe you are already doing this - I didn't check) so it's a similar effect as what we do today but with the added benefits of cataloging / commenting / finding.
Congrats on launching. Who do you envision as the primary users and first niche use cases?
Ps - I coorganize a software engineer meetup here. We’ve got good representation!
As a side project, I actually built a tool to help with this: "Calculeeto" (http://calculeeto.herokuapp.com/). Besides walking you through the process of breaking down your project and adding buffer, it also has features to assign dependencies and generate a schedule based on number of teammates -- it even adds time for communication overhead: http://calculeeto.herokuapp.com/?debug4
I never launched or finished it but it seemed useful.
Also, not all Michelin restaurants are that good... (In NYC, I think they are because it is so competitive but I've been disappointed in SF and Hong Kong for instance).
So FYI - just because a restaurant has a Michelin star, it doesn't mean it is always packed nor good.