Search Providers (e.g. Semantic Search) #596
davepwsmith
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Have you considered allowing extensions to search? The current search works well for something quite targeted but I have been impressed by the way e.g. Karakeep has integrated a semantic search layer. They used Meilisearch, which is quite heavyweight and requires the use of external models to generate embeddings, but there are lighter alternatives like QMD (or sqlite-vec directly, which QMD is built on top of) which integrate a small local embedding model. Once your collections of notes, bookmarks, etc. start to get large, it's amazing how useful these more complex search providers become.
If you didn't want to include these kinds of significant dependencies (which I would understand...), I took a quick look at how it might be done, and it seemed like a first step might be to abstract the search provider to allow others? Then if there were a standard set of search-like endpoints (https://search-provider/search?q=xxx) you could allow results from external services.
I am no expert though, so it could all be much more difficult than I imagine...
All reactions