Wolflordy
My feedback
29 results found
-
129 votes
An error occurred while saving the comment
Wolflordy
supported this idea
·
-
11 votes
An error occurred while saving the comment
Wolflordy
commented
This would be a great additional feature that I really need. It's obnoxious to be working around this issue.
Wolflordy
supported this idea
·
-
77 votes
Wolflordy
supported this idea
·
-
125 votes
An error occurred while saving the comment
Wolflordy
commented
This works on browser.
-
185 votes
Wolflordy
supported this idea
·
-
421 votes
Wolflordy
supported this idea
·
-
3 votes
Wolflordy
shared this idea
·
-
14 votes
Wolflordy
supported this idea
·
-
20 votes
Wolflordy
supported this idea
·
-
204 votes
Wolflordy
supported this idea
·
-
186 votes
Wolflordy
supported this idea
·
-
1,083 votes
Wolflordy
supported this idea
·
-
117 votes
Wolflordy
supported this idea
·
-
50 votes
Wolflordy
supported this idea
·
-
759 votes
Wolflordy
supported this idea
·
-
352 votesWork on this has started. More details: https://proton.me/blog/2026-autumn-winter-roadmaps
Wolflordy
supported this idea
·
-
13 votes
Wolflordy
supported this idea
·
-
25 votes
An error occurred while saving the comment
Wolflordy
commented
This would be a fantastic addition to Lumo's security profile, and would make it a clear better over Confer in every aspect.
I'm sympathetic to the cost Proton might have to bear for this. TEE is an Nvidia thing, and their GPUs are expensive. The architecture behind setting up TEE is also not trivial. However, I'd really like Lumo Plus users to be able to use TEE.
Perhaps Lumo is waiting on FHE to be commercially viable for large-scale LLMs. However, that's at least a decade out. And TEE is the only real stop-gap between now and then.
I'm shocked at how low this proposition is on uservoice given how privacy and security conscious Proton's userbase normally is.
Wolflordy
supported this idea
·
-
71 votes
Wolflordy
supported this idea
·
-
102 votes
Wolflordy
supported this idea
·
This would be really useful as a toggle