Thanks! The project is still early stages, haven't had a chance to get the app signing set up - right now the easiest way to get started is using the web interface via docker compose.
What's holding me back from AI repos and agents isn't running it locally though. Its the lack of granular control. I'm not even sure what I want. I certainly don't want to approve every request, but the idea of large amounts of personal data being accessible, unchecked, to an AI is concerning.
I think perhaps an agent that focuses just on security, that learns about your personal preferences, is what might be needed.
Agreed regarding the privacy/security hesitations. Running the models locally with ollama is an option, but of course there's the hardware requirements and limitations of open source models to contend with. ultimately it's a balance between privacy and ease of use, and I'm not sure that there's a good one-size-fits-all for that balance.
For sure. The idea here (or at least how I've been using it) is to use Atomic as catchall place to put personal notes, interesting articles, research ideas .. pretty much anything, and Atomic will handle the categorization and knowledge synthesis. For example, I have a knowledge base that uses RSS to sync top Hacker News articles and I'll occasionally generate new wiki-style articles which summarize and synthesize the articles based on top-level categories (AI, hardware, philosophy, you name it).
What's holding me back from AI repos and agents isn't running it locally though. Its the lack of granular control. I'm not even sure what I want. I certainly don't want to approve every request, but the idea of large amounts of personal data being accessible, unchecked, to an AI is concerning.
I think perhaps an agent that focuses just on security, that learns about your personal preferences, is what might be needed.
Agreed regarding the privacy/security hesitations. Running the models locally with ollama is an option, but of course there's the hardware requirements and limitations of open source models to contend with. ultimately it's a balance between privacy and ease of use, and I'm not sure that there's a good one-size-fits-all for that balance.