Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm thinking of adding support for text files. Only thing holding me back is that it would make the app much larger.

I'm also considering making the models more a la carte so you can manage which ones your want to use depending on your use case. That way you could use for text, image/video, or both.



How so? Indexing text seems fairly straightforward?


Adding more capability means adding another set of model weights.


Right but indexing text is, like, you already have the text…


For the best performance you'd probably want to use something other than CLIP's text encoder, but yeah you already have the text and could index it.

If enough people asked for it, I would consider adding a different embeddings models.


Exactly




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: