BrianD
My feedback
41 results found
-
906 votesBrianD supported this idea ·
-
1,246 votesBrianD supported this idea ·
-
994 votesBrianD supported this idea ·
-
5,942 votesBrianD supported this idea ·
-
18,389 votesBrianD supported this idea ·
-
321 votes
An error occurred while saving the comment BrianD supported this idea · -
433 votes
An error occurred while saving the comment BrianD commentedexists on mobile now, not yet for web app :(
-
355 votes
An error occurred while saving the comment BrianD commentedThis would be useful, and considering Proton runs so much of their own infrastructure i'd hope it is possible
BrianD supported this idea · -
2,281 votes
An error occurred while saving the comment BrianD commentedGraphene, Lineage, Calyx etc already exist. I think this would be cool but it would really stretch resources when there are viable alternatives available.
-
3,014 votes
An error occurred while saving the comment BrianD commentedFor the degoogled folks who have a serious threat model, this is a must
BrianD supported this idea · -
906 votesBrianD supported this idea ·
-
284 votes
An error occurred while saving the comment BrianD commentedI think this is done right? at least it does not default to .ch
-
514 votes
An error occurred while saving the comment BrianD commentedI think this now exists for Proton Business and Visionary plans... surprised the family plan doesn't have the same though.
-
655 votes
An error occurred while saving the comment BrianD commentedThis should be implemented with key transparency, right? I think it uses multiple public keystores https://proton.me/support/key-transparency
-
7,748 votesBrianD supported this idea ·
-
5,479 votesBrianD supported this idea ·
-
5,084 votesBrianD supported this idea ·
-
1,479 votesBrianD supported this idea ·
-
278 votesBrianD supported this idea ·
-
179 votesBrianD supported this idea ·
super important to be as flexible as possible with recurrence scheduling