Not to mention, Joplin allows more than structured text (native embedded images/media, even more kinds of content with plugins) and the text-only joplin.ai.chat() will definitely “need” to be supplemented with multi-modal AI support.

As for new techniques, I imagine the declining AI subsidies will raise the popularity of context reuse (reducing token use by not having the LLM re-read the whole notebook; is that what it’s called? I don’t remember much from videos/articles about AI trends because I don’t use it). This will require a huge framework for managing data structures distilling every cached context window… And I think non-LLM functions will be added too to save tokens, for example an LLM may want to know “is there an unfinished TODO?” without reading all of them.

Not a bad idea to make infrastructure separating the model-calling backend from user-facing frontend: only a single plugin manages local models and API key to remote models.
But isn’t this a bit of scope creep for a note-taking app? As I understand it, this whole AI framework has existed as a first-party plugin for a while now, with no AI API in the base app (which is quite bloated as is).

Not to mention, lots of recent contributions are heavily AI-made: not ideal for an app handling important private stuff.

To save you a risky click, in case you just wanted to know if they have legs: yes. Not very different from anthropomorphic lizards.

She’s Ellen Joe from Zenless Zone Zero and that “massive booty” is actually a shark tail.