Alexander
My feedback
13 results found
-
226 votes
An error occurred while saving the comment Alexander
supported this idea
·
-
19 votesAlexander
supported this idea
·
-
570 votesAlexander
supported this idea
·
-
159 votesAlexander
supported this idea
·
-
738 votesAlexander
supported this idea
·
-
825 votesAlexander
supported this idea
·
-
721 votesAlexander
supported this idea
·
-
1,001 votesAlexander
supported this idea
·
-
659 votes
Subscribers now have access to offline view with the introduction of the Proton Pass desktop app for Windows:
For more information, including what's coming next, check out: https://proton.me/blog/proton-pass-windows-app
Alexander
supported this idea
·
-
632 votesAlexander
supported this idea
·
-
238 votesAlexander
supported this idea
·
-
578 votesAlexander
supported this idea
·
-
11 votes
An error occurred while saving the comment Alexander
commented
Hi Proton team. Incredible work with this app, thank you for all the robust feature updates and providing an unparalleled level of security and therefore peace of mind while navigating the web and managing accounts.
I just want to echo that I think this is a really critical feature that could dramatically enhance the user experience. I've often found myself re-creating numerous fields and copying their values, just so I can customize the order of my fields. This often results in user error and realizing I actually would have preferred a slightly different order, meaning I end up repeating my actions.
I think the utility of this feature has become even more pronounced since you all introduced the Identities feature. Now that we can create entire custom sections, I'm finding broad applicability for their use, particularly for technical projects. For example, it's a great way to store information about managing an app development setup (e.g. SSH, VPS, database, application credentials). These can get complicated, and new values worth saving tend to emerge over time, so I think it would be incredible to be able to reorder fields and sections on the fly, instead of needing to recreate them, which is becoming infeasible in my most nuanced entries due to their length.
Again, thanks for all the awesome work, hope this feedback is useful to you, and very much looking forward to whatever you all are cooking up next. Appreciate your time!
Alexander
supported this idea
·
Hi Proton Mail team, thanks for your great work on this application. I just want to add my intense agreement to this thread. This is a totally critical security measure for me and stands out as an unusual gap in security for an otherwise remarkably secure suite of tools. I agree with others in this thread that it would be great to either limit login to username only, so as to never need to expose any component of login credential publicly, or if not that then the ability to toggle each email as a login option. In the case of toggles, personally I'd toggle a single one on and treat it precisely like a never-shared username, so the username approach would be totally sufficient for my use case, but I recognize the relative lack of flexibility of that approach compared to the toggles. Regardless of mode of solution, I absolutely must be able to restrict the ability to login to my Proton account for a specific address. Until then, I keep finding myself jumping back to Gmail (extremely reluctantly) in order to send outgoing messages, and it's becoming a major problem when it comes to custom domain email address management.
Again, thank you very much for these tools, they're essential to me, which is precisely why I feel so strongly about the criticality of this feature request. Appreciate all your hard work!