Sounds like a nightmare to maintain. No chance that this will be implemented without a public api to pull from.
Yeah, but on the other hand it is very suited for a FLOSS project, where everyone can contribute, instead of such things in non-open-source browsers.
So maybe it indeed needs another project/GitHub repo/website, where people can add/contribute data and you would only be one user of that. Nevertheless it can be your initiative to create that…
I'd rather start the initiative to end ridiculous password requirements except for length and obvious repetitive characters.
Well... in a perfect world you'd succeed, but I doubt you'll get far this way... 😆
I agree with to much ressources for a FOSS project to maintaine.
Often the problem is the websites doesn't inform the user about the complete passwort restrictions. Even the admins didn't knew it themself!
Myself I contact the admins all the time. IMO this is more in the responsibility of the (FOSS) users to flood the admins with questions about that. If more users asking such questions they will think more about it.
In context of KeePassXC this Issue can IMO be closed or set to something like "nice to have - but will never implemented"
I'm closing it since the web credentials standard is now approved
the web credentials standard
The _what_?
See #1870
Most helpful comment
I'd rather start the initiative to end ridiculous password requirements except for length and obvious repetitive characters.