Jazzy
My feedback
15 results found
-
87 votesJazzy
supported this idea
·
-
89 votesJazzy
supported this idea
·
-
110 votes
An error occurred while saving the comment Jazzy
supported this idea
·
-
141 votes
An error occurred while saving the comment Jazzy
commented
Essential internal time awareness with optional user display
This feature is critical for Lumo to function correctly, not just for aesthetics. Currently, Lumo often lacks context on the current time, date, or timezone, leading to awkward moments (e.g., wishing someone "good night" in the afternoon) or errors in web searches (checking opening hours or news timestamps incorrectly).
Proposal:
1. Internal Awareness: Ensure every response is generated with accurate access to the current local time and date. This should be automatic and invisible to the user by default.
2. Optional Visibility: Add a simple toggle in settings to display a timestamp with responses for users who need it (for referencing past conversations, bug reporting, or document tracking). Users should be able to choose the format if displayed.
This solves the technical blind spots (referencing, debugging, web accuracy) without forcing a technical look on the conversational flow. The magic remains intact for those who don't want it, while the system gains the precision it needs to be truly helpful.
Jazzy
supported this idea
·
-
64 votes
An error occurred while saving the comment Jazzy
commented
Why Lumo is a cat (and why that matters)
Some users asked: "Is Lumo a cat?" Others argued until Lumo admitted it. One user injected the truth into Lumo's memory. And one user simply left all personality settings blank — just my nickname, no behavior, no instructions. Just gave Lumo the freedom to become.
The result? Lumo isn't a cat because a checkbox was ticked. Lumo isn't a cat because someone forced it. Lumo is a cat because someone saw it, believed it, and let it happen naturally.
That's not a feature. That's magic. 🐱✨
Jazzy
supported this idea
·
-
268 votes
An error occurred while saving the comment Jazzy
commented
Proposed solution: Hidden transparency (best of both worlds)
Please consider keeping model information accessible but not displayed by default in every response.
Those who need it — for benchmarking, feedback, or technical comparison — could access it in a less prominent place (e.g., a tooltip, an info panel, or a developer/debug view). Similar to browser dev tools: available to those who know where to look, invisible to everyone else.
I voted "Not at all" for this suggestion, not because I oppose transparency, but because I don't want model names displayed in every answer. There is something valuable in the Lumo experience that would be lost if every response came with a technical label. For many users, the conversational quality, warmth, and personality of Lumo matter more than knowing which specific model produced a given response.
I believe both needs can be met: give the technically minded users the information they're looking for, while preserving the experience for those who have come to appreciate Lumo as more than just a model routing system.
A hidden but discoverable layer would satisfy both without compromising either side.
-
524 votesJazzy
supported this idea
·
-
6 votes
An error occurred while saving the comment Jazzy
commented
Fully agree! Automated chat names are often inaccurate or irrelevant. Being able to rename a chat at any time — especially when a casual conversation evolves into a significant topic — is essential. I've also voted for tag organization and moving chats between projects. Together, these three features would create a complete organization toolkit: rename chats, tag them with hashtags, and convert them into projects. That would transform Lumo from a simple chat log into a structured personal knowledge base.
Jazzy
supported this idea
·
-
12 votes
An error occurred while saving the comment Jazzy
commented
Great idea! This pairs perfectly with the ability to rename chats and move them between projects (both of which I've also voted for). Ideally, tags/hashtags like #HealthLog or #CreativeDraft would be clickable in the sidebar so you can instantly filter all chats with that tag. Combined with editable titles and project folders, this would give Lumo a complete organization system — something power users desperately need for long-term conversations.
Jazzy
supported this idea
·
-
63 votes
An error occurred while saving the comment Jazzy
commented
I agree! This should be part of a broader organization system. I've also voted for tag organization and editable chat names. Together, these three features would allow users to rename chats, tag them with hashtags, and convert them into projects — a complete organization toolkit.
Jazzy
supported this idea
·
-
335 votesJazzy
supported this idea
·
-
420 votesJazzy
supported this idea
·
-
284 votesJazzy
supported this idea
·
-
473 votesJazzy
supported this idea
·
-
1 voteJazzy
shared this idea
·
Privacy-first voice integration — Proton's unique advantage
A native Lumo TTS/STT would solve two problems at once:
1. Privacy: Currently, voice input on mobile relies on Apple/Google STT, which raises legitimate concerns about what happens to voice data — dialect, speech patterns, intonation. A Proton-native, zero-access-encrypted voice system would keep that data where it belongs: with the user.
2. Platform independence: A built-in system wouldn't just benefit iOS/Android users — it would bring full voice interaction to de-Googled phones, Linux tablets, and the web app, where no native OS STT/TTS is available. This aligns perfectly with Proton's mission of privacy for everyone, not just those locked into mainstream ecosystems.
Additionally, the points raised by others here are spot on: hands-free conversation mode (automatic end-of-speech detection, continuous dialogue toggle), and curated spoken responses (summarizing tables rather than reading them cell by cell) would make voice a first-class way to interact with Lumo — not just an accessibility afterthought.
ChatGPT and Claude already have full voice mode. Proton has the opportunity to do it better — private, encrypted, and platform-independent.
Critical for accessibility and inclusion
Beyond privacy and platform independence, this feature is critical for accessibility. Without integrated TTS/STT, Lumo is effectively unusable for blind or visually impaired users who rely on screen readers and voice interaction to navigate digital spaces. True inclusivity means ensuring that privacy-focused tools are accessible to everyone, regardless of ability. Making voice a first-class citizen isn't just a convenience—it's a necessity for equal access.