BrianD
My feedback
59 results found
-
647 votes
BrianD
supported this idea
·
-
1,573 votes
BrianD
supported this idea
·
-
374 votes
BrianD
supported this idea
·
-
8 votes
BrianD
shared this idea
·
-
1,559 votes
BrianD
supported this idea
·
-
59 votes
BrianD
supported this idea
·
-
1,867 votes
BrianD
supported this idea
·
-
2,911 votes
Partially rolled out, as per: https://proton.me/support/pass-offline-access
As per the Spring/Summer Roadmap this will extend out to the Pass Extension: https://proton.me/blog/pass-roadmap-spring-summer-2026
-
1,760 votes
BrianD
supported this idea
·
-
269 votes
An error occurred while saving the comment
BrianD
supported this idea
·
-
469 votes
An error occurred while saving the comment
BrianD
commented
exists on mobile now, not yet for web app :(
-
367 votes
An error occurred while saving the comment
BrianD
commented
This would be useful, and considering Proton runs so much of their own infrastructure i'd hope it is possible
BrianD
supported this idea
·
-
1,319 votes
An error occurred while saving the comment
BrianD
commented
Graphene, Lineage, Calyx etc already exist. I think this would be cool but it would really stretch resources when there are viable alternatives available.
-
1,881 votes
An error occurred while saving the comment
BrianD
commented
For the degoogled folks who have a serious threat model, this is a must
BrianD
supported this idea
·
-
130 votes
An error occurred while saving the comment
BrianD
commented
I think this is done right? at least it does not default to .ch
-
490 votes
An error occurred while saving the comment
BrianD
commented
I think this now exists for Proton Business and Visionary plans... surprised the family plan doesn't have the same though.
-
393 votes
An error occurred while saving the comment
BrianD
commented
This should be implemented with key transparency, right? I think it uses multiple public keystores https://proton.me/support/key-transparency
-
3,885 votes
BrianD
supported this idea
·
-
2,067 votes
BrianD
supported this idea
·
-
2,000 votes
BrianD
supported this idea
·
super important to be as flexible as possible with recurrence scheduling