I'd like edit this because, while I continue to agree with Doug it'd be nice to have a broader "overall" and "ongoing" context with Lumo, as I'm experimenting with the Projects option I'm finding it works as persistent context, at least across the project matters. So it's still interesting to me to see a broad relationship context with Lumo covering all our interactions, but it feels less pressing for me with the Projects option.
I agree with this suggestion. Current Lumo conversations lack continuity. Users can't build on prior analysis, track patterns over time, or maintain context for long-term projects without repetitive re-entry. And, to expand on Doug's comments -
Stores conversation summaries/data points encrypted at rest (leveraging existing Proton Drive infrastructure)
Requires explicit user consent for what gets remembered
Allows user review/deletion anytime
Maintains zero-access encryption (Proton cannot read stored memory)
Provides clear indicators when memory is accessed
Why This Fits Proton's Model:
Leverages existing encrypted storage (Drive, chat history at rest)
Aligns with zero-access encryption philosophy
User-controlled access matches Proton's privacy-first approach
Technical constraints are manageable given current infrastructure
Key Use Cases:
Long-term research & organizational resilience tracking
Creative writing consistency
Learning journeys with cumulative understanding
Strategy evolution in political/community organizing
Suggested Implementation:
David
I'd like edit this because, while I continue to agree with Doug it'd be nice to have a broader "overall" and "ongoing" context with Lumo, as I'm experimenting with the Projects option I'm finding it works as persistent context, at least across the project matters. So it's still interesting to me to see a broad relationship context with Lumo covering all our interactions, but it feels less pressing for me with the Projects option.
I agree with this suggestion. Current Lumo conversations lack continuity. Users can't build on prior analysis, track patterns over time, or maintain context for long-term projects without repetitive re-entry. And, to expand on Doug's comments -
Proposed Solution: Opt-in, user-controlled cross-session memory that:
Stores conversation summaries/data points encrypted at rest (leveraging existing Proton Drive infrastructure)
Requires explicit user consent for what gets remembered
Allows user review/deletion anytime
Maintains zero-access encryption (Proton cannot read stored memory)
Provides clear indicators when memory is accessed
Why This Fits Proton's Model:
Leverages existing encrypted storage (Drive, chat history at rest)
Aligns with zero-access encryption philosophy
User-controlled access matches Proton's privacy-first approach
Technical constraints are manageable given current infrastructure
Key Use Cases:
Long-term research & organizational resilience tracking
Creative writing consistency
Learning journeys with cumulative understanding
Strategy evolution in political/community organizing
Suggested Implementation:
Phase 1: User-defined "memory notes" (explicitly saved, encrypted)
Phase 2: Opt-in conversation summarization
Phase 3: User-controlled pattern recognition
Anyway, just some thoughts because this is a very strong upvote matter for me too.