@ice.d , questo merita una richiesta separata. Purtroppo, ciò che proponi era la giustificazione originale per la rimozione di questa funzionalità per impostazione predefinita, anche se infondata. Ciò che proponi renderebbe quella preoccupazione fondata:
opened 09:57PM - 28 Jun 26 UTC
closed 09:41AM - 29 Jun 26 UTC
When I reproduce [`bitwarden/clients/issues/4697`](https://github.com/bitwarden/… clients/issues/4697#issue-1576623971) at [`theyworkforyou.com/user/login`](https://www.theyworkforyou.com/user/login/), I am informed that:
> There is no user registered with an email of <q>`wr5u53jt@rokejulianlockhart.addy.io`</q>, or the given password is incorrect.
However, my account exists, which the success state from `ydotool key 29:1 47:1 47:0 29:0` demonstrates:
https://github.com/user-attachments/assets/c06e5e4d-819f-48f0-ab3b-a981f45eef0a
Had I not already estimated the cause, I would have wasted time by going through password reset after password reset, surprised at the failure. Knowing that the password is incorrect would prevent me uselessly evaluating whether alternative e-mail addresses authenticate.