What's next?

If possible, we hope to integrate support for CJK (Chinese, Japanese, Korean) word segmentation search directly into Joplin. This would eliminate the need to implement it in external applications that call the Joplin REST API. We expect to achieve this through WebAssembly (WASM), which offers natural cross-platform compatibility and relatively high performance. For Chinese word segmentation, this would add approximately 2.7MB to the WASM file. If we integrate it into Joplin, would this be acceptable? @laurent