Closed byheaven closed 13 hours ago
That's an appealing idea. If the server side of fireSeqSearch could be implemented as a logseq plugin, then there could be lots of benefits.
However, my current implementation is strongly coupled with Rust and tantivy. Moving to local HTTP server means that I need to rewrite the program totally, and I don't know if this is possible.
I'm open to discussing this idea, but I don't think I'll work on it in the foreseeable future.
Thank you again for your suggestion
Currently Logseq only has datalog query API, instead of the page & fulltext search API, so I think this won't be trivial. But I submitted a feature request to Logseq. You can add a vote there to make the feature more possible to be implemented :) https://discuss.logseq.com/t/add-support-for-page-fulltext-search-api/13842
As far as I know (from the WeChat group), they are developing the full text searching tools now.
I'm going to support Obsidian as Tier 1 target, so I'll avoid logseq-only APIs when possible.
Is it possible to use the original service? Thank you!