BrianD
My feedback
80 results found
-
1,538 votes
BrianD
supported this idea
·
-
680 votes
BrianD
supported this idea
·
-
1,642 votes
BrianD
supported this idea
·
-
485 votes
BrianD
supported this idea
·
-
9 votes
BrianD
shared this idea
·
-
1,641 votes
BrianD
supported this idea
·
-
70 votes
BrianD
supported this idea
·
-
1,918 votes
BrianD
supported this idea
·
-
3,007 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,849 votes
BrianD
supported this idea
·
-
272 votes
An error occurred while saving the comment
BrianD
supported this idea
·
-
486 votes
An error occurred while saving the comment
BrianD
commented
exists on mobile now, not yet for web app :(
-
373 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,357 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,948 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
·
-
132 votes
An error occurred while saving the comment
BrianD
commented
I think this is done right? at least it does not default to .ch
-
521 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.
-
396 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
-
4,052 votes
BrianD
supported this idea
·
-
2,087 votes
BrianD
supported this idea
·
super important to be as flexible as possible with recurrence scheduling