fireSeqSearch icon indicating copy to clipboard operation
fireSeqSearch copied to clipboard

Logseq 0.8.15 now supports local http server API.

Open byheaven opened this issue 2 years ago • 3 comments

Is it possible to use the original service? Thank you!

byheaven avatar Dec 30 '22 15:12 byheaven

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.

  1. Easier for me to push updates
  2. Don't need to run another app at startup
  3. Reuse some logseq libs

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

Endle avatar Dec 30 '22 19:12 Endle

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

xxchan avatar Jan 01 '23 23:01 xxchan

As far as I know (from the WeChat group), they are developing the full text searching tools now.

byheaven avatar Jan 02 '23 02:01 byheaven

I'm going to support Obsidian as Tier 1 target, so I'll avoid logseq-only APIs when possible.

Endle avatar Sep 18 '24 02:09 Endle