Hi Michael, Colleagues have pointed me to an escalation path internally at Google; I've filed one, and pointed back to this email thread. It's not clear whether one specific thing changed that can be reverted - Google's anti-abuse team is constantly evolving their strategies for detecting automated attacks. I can't promise anything, but hope that the team will follow up here, and that together a solution can be found. -Ken On Tue, May 3, 2022 at 6:13 PM Michael Catanzaro via webkit-dev < webkit-dev@lists.webkit.org> wrote:
Hi, see:
https://bugs.webkit.org/show_bug.cgi?id=240041
It is a little finicky, in that it *sometimes* works, and I don't know why. But usually Google blocks us. See screenshot:
https://bugs.webkit.org/attachment.cgi?id=458768
I was hoping that it could be avoided by a user agent quirk, but sadly they are doing some deeper level of fingerprinting.
Can anybody who is able to get attention from Google help get this reverted *urgently*? This is beyond unacceptable. I doubt we'll have any luck via the ask nicely approach, but it's worth a try.
Michael
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
-- I support flexible work schedules, and I’m sending this email now because it is within the hours I’m working today. Please do not feel obliged to reply straight away - I understand that you will reply during the hours you work, which may not match mine. (credit: jparent@)