Re:Launch HN: Metal (YC W23) – Embeddings as a Service
by kaycebasques on Tuesday March 28, 2023 @09:28PM
(#35350847)
Congrats on the launch. I started exploring applications of generative AI towards technical documentation this week. I quickly realized that embeddings are a key piece of the puzzle and I can give you some initial validation: I definitely don't want to manage this stuff myself and it really seems like I shouldn't need to. Also I am comfortable with services like Firebase so your product immediately makes sense to me because I basically think of it like Firebase for embeddings.
This is probably more feature creep than you can or want to sign up for at the moment, but I also don't really want to deal with manually transforming my Markdown or HTML into the sections of text that you use as input for embeddings. It would be nice if I could just provide URLs to my live documentation or Markdown source code, and your service takes a best guess at how to split it up into sections and then generate embeddings for each of those sections.
Last, I would be happy to talk to you all about docs strategy for your own docs sometime (I'm not looking for work at the moment; I just enjoy helping people with this stuff). You can contact me and learn more about my background via the social links on https://technicalwriting.tools (a blog about technical writing tooling topics that I just spun up).
Re:Launch HN: Metal (YC W23) – Embeddings as a Service
by tlowe11 on Tuesday March 28, 2023 @09:50PM
(#35351047)
Great to hear! Humbled by the Firebase comparison as well :) We've talked about the markdown/HTML feature, definitely something we want to build. And I'll ping you!
This is probably more feature creep than you can or want to sign up for at the moment, but I also don't really want to deal with manually transforming my Markdown or HTML into the sections of text that you use as input for embeddings. It would be nice if I could just provide URLs to my live documentation or Markdown source code, and your service takes a best guess at how to split it up into sections and then generate embeddings for each of those sections.
Last, I would be happy to talk to you all about docs strategy for your own docs sometime (I'm not looking for work at the moment; I just enjoy helping people with this stuff). You can contact me and learn more about my background via the social links on https://technicalwriting.tools (a blog about technical writing tooling topics that I just spun up).
Good luck!