Has anyone else noticed that even with solid residential proxies their accounts still get banned quick if the real browser TLS fingerprint doesnt match up with the JA3 fingerprint antidetect browser setup especially when mixing UULE 3 geolocation parameters for Google location and HTTP/2 SETTINGS fingerprint that screams browser fingerprint coherence issues or fingerprint randomisation detection leading to antidetect browser detection and wondering if its the real browser vs Chromium fork difference thats killing it lately.