There is a website where I sometimes Sign In successfully. On the occasion of each success, I write down the various Brave Browser > Settings. Usually, an adjustment to the ‘Trackers & Ads’ and/or ‘Fingerprinting’, . . . and a lot of attempts to connect, ‘just kind of, sort of, stumbles to a success’.
Then, trying again, moments later, may succeed, or fail. Failures are noted by the website; roughly or simply:
- ‘Oops’ (99.9% of the time)
- ‘Unrecognized username and password’ (if using Safari on iPhone)
I can see in some of the NoScript (using Firefox) settings, that the troublesome website wants to know a lot about the connecting computing device/software. The website has a particular issue with wanting to get feedback re WebGL (that I usually have disabled).
I did, once, enable WebGL, but that did not satisfy the troublesome website.
Watching / monitoring the communications via Developer Tools, I can see that the pacing of Request < > Reply events, being monitored by the website, is probably the focal point of failure.
If I just happen to catch the window of opportunity, then there is a successful Sign In. Takes about 30 minutes, to make such a catch.
Looks like CitiBank is somewhat the same:
‘Citibank online freezes for a few seconds - #3 by event3horizon’