Jazzy
My feedback
128 results found
-
14 votesJazzy
supported this idea
·
-
24 votesJazzy
supported this idea
·
-
227 votesJazzy
supported this idea
·
-
37 votesJazzy
supported this idea
·
-
388 votes
An error occurred while saving the comment An error occurred while saving the comment Jazzy
commented
This is exactly what I've been looking for!
I want to add a critical security perspective: Currently, users who need WebDAV (e.g., for Joplin, Home Assistant, or other tools) are forced to use unofficial bridges like proton-webdav-bridge or Rclone. These workarounds require us to trust third-party software with our credentials or API tokens, which creates a significant security vulnerability and contradicts Proton's zero-access encryption promise.
An official implementation is not just about convenience—it's about closing this security loophole. Please prioritize making WebDAV an official, native feature so we can stay within the trusted Proton ecosystem without resorting to risky external tools.
Thank you for working on this!Jazzy
supported this idea
·
-
86 votesJazzy
supported this idea
·
-
343 votesJazzy
supported this idea
·
-
1,211 votesJazzy
supported this idea
·
-
794 votesJazzy
supported this idea
·
-
1,421 votesJazzy
supported this idea
·
-
482 votesJazzy
supported this idea
·
-
1,910 votesJazzy
supported this idea
·
-
4 votesJazzy
supported this idea
·
Jazzy
shared this idea
·
-
48 votes
An error occurred while saving the comment Jazzy
commented
Great idea! I completely agree that searching the full content of chats (not just titles) is essential.
However, I'd like to add a crucial dimension to this: Offline capability.
Many users need to access and search their chat history without an internet connection (e.g., on flights, in areas with poor signal, or for privacy reasons). A local search function would be even more powerful if it worked on chats that are marked as 'available offline' (similar to Proton Drive).
Ideally, this would include:- Highlighting search terms within the text.
- Navigating up/down between results.
- Working entirely locally on the device without needing a server connection.This would turn the search feature into a true productivity tool for offline scenarios.
Jazzy
supported this idea
·
-
4 votesJazzy
shared this idea
·
-
97 votesJazzy
supported this idea
·
-
118 votesJazzy
supported this idea
·
-
134 votes
An error occurred while saving the comment Jazzy
commented
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.
Jazzy
supported this idea
·
-
159 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
·
-
73 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
·
Follow-up to my previous comment:
I see many requests for WebDAV, but I want to highlight why my concern is unique and urgent:
Most users ask for WebDAV for convenience. My request is driven by security necessity.
Currently, the only way to use Proton Drive with essential tools (like Joplin for notes or Home Assistant for backups) is to use unofficial third-party bridges (e.g., proton-webdav-bridge or Rclone scripts).
The Paradox: By forcing users to these workarounds, Proton inadvertently creates a security vulnerability:
Users must trust external, unmaintained code with their credentials.
These tools often decrypt data locally in ways that bypass Proton's zero-access model.
We are pushed away from the secure Proton ecosystem into risky, unofficial territory.
My plea: Please don't just add WebDAV as a "nice-to-have" feature. Add it as a core security requirement to prevent users from having to compromise their safety to use your product. An official implementation closes this loophole and keeps everyone within the trusted Proton environment.
This isn't just about Linux or convenience—it's about maintaining the integrity of our security model.