Hi, I want to discuss the GSOC idea # 1
Is AI-supported search for notes idea can be implemented in a seperate plugin ???
Or is this mandatory to be implemented as a core application functionality?
Hi, I want to discuss the GSOC idea # 1
Is AI-supported search for notes idea can be implemented in a seperate plugin ???
Or is this mandatory to be implemented as a core application functionality?
If it can be done as a plugin it should be a plugin
I am planning to implement Idea #1 as a Joplin plugin. My question is about the LLM API key setup , should users configure their own API key in the plugin settings, or would Joplin provide a shared API key for all users?
For context, I already built a plugin where each user enters and stores their own API key, which I then encrypt locally. I want to confirm whether this is the expected approach before proceeding with the full implementation.
Users configure their own API key in the plugin settings
As this idea is for "AI-supported search for notes" how necessary is it for an external LLM requiring a key vs a local one?
I will make the plugin totally customize-able a user will be able to add a API key or setup LLM locally
Models like all-MiniLM-L6-v2 run in ~200MB RAM basically nothing.
For my previous ai chat plugin I took the LLM API from user and encrypted it and saved it and then used that encrypted API key for answering the user queries based on notes
@laurent @Daeraxa I have one last query.
as joplin will implement AI-supported search for notes idea as a separate plugin so there will be no chance of having sharing the same search box? AI-supported search for notes plugin should have its own search box? as this question is crucial for drafting my proposal