+1, displaying in a Emacs buffer solves any issues I could have. If you're already 'in' Emacs, this will be more frictionless than shell scripts around man
amanneedsamaid
joined 2 years ago
My fault entirely. I guess my argument would be that those other corporations also shouldn't be creating password managers, at least 'within their ecosystem'.
I believe a password database should preferably be stored locally, and at least in a cloud that is completely separate from your essential account(s) (i.e Proton, Google, Microsoft accounts, etc.) I have no doubt Proton's implementation is secure, but I think the principle of using it is not ideal.
Unless Proton OS is a consideration, I dont think a browser is a natural progression. There are plenty of private browser options already being developed (and I think the proton extensions cover most conveniences). The only way I'd see a Proton browser as a positive thing is if they went all in on ladybird or some other completely independent browser engine.
My bad, v tired when I replied. That is an interesting feature the only similar solution I can think of is using something like Fossify Dialer (a fork of the now ad-ridden and proprietary Simple Dialer) and use T9 dialing. That could achieve a similar speed / memorization as a gesture.
You could definitely get good enough at T9 to at least call people without looking at the screen.
I think its redundant and an incredibly bad idea to have my email, vpn, calendar, and cloud provider host my passwords. If I wanted a cloud based password manager, I'd use a standalone tool like Bitwarden. (imo, I realistically think protons implementation in probably just as secure for the average user.)
Either way, I think a password database is too important to store in the cloud, so I use KeePass.
A new proton product that isn't useless? ahem PASS
I like this, and I REALLY hope Proton ignores the fact that a web browser came first in their community poll for their next service / product. That result shocked me, I couldn't think of a worse (specifically, more redundant) application for them to release / develop.
Just tried it and really enjoyed, but the contact sources just don't seem to work? Two options, one from sms and one from com.android.contacts, and neither are correct (missing / duplicate contacts). Confused as to why the dialer can't just pull from my contacts like every other dialer, or I'd probably switch!
I use fossify dialer, not familiar with Drupe, but works well for me.
Emacs find-file with vertico and orderless achieve this nicely.
If anything I use them for everything because I find it much easier / faster.
Image Toolbox + Aves Libre is my current setup.
Pixel with GrapheneOS for me.