Gmail password generator1/8/2023 ![]() If said user-sourced per-site custom setting information could be safely and anonymously crowdsourced, then as soon as eBay or Reddit or LinkedIn or Facebook or local-bank-in-my-town added or modified their policy (which we all know happens) valid custom-configuration values on that FQDN or domain would be identified at each use. SO: Yes, I am getting into solutioning here, but I felt it essential to provide a counterpoint, outside the box options to earlier nay-saying analysis (sorry folks!) Optimally, having Dashlane figuring it out 100% would be excellent I must agree with u/tramplemestilsken and others that parsing websites' unstructured human-readable data either continuously or on the fly is a feature maintenance nightmare. A data field that Dashlane checks within that entry would obviate that work and further manage passwords. Especially when sites you frequent have mutually exclusive configuration values, this onus is on the user to switch back and forth configs. ![]() ![]() I believe giving people willing to toil through configuring the auto-generator value set options when presented on a per-site basis has a lot of value.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |