reCAPTCHA Verification using Google search

Zurarczurx wrote:

It's not because Safari's web-tracking defences are good. I use Brave and I use Firefox with a variety of privacy and JS shields and it has no problems with Google search - and I haven't got a Google account. This particular Safari problem can be caused by having Private Relay turned on or, as in my case, because Safari re-submits the query many times and as a result Google thinks that the request comes from a bot.

If the OP has Private Relay turned on then they should turn it off.

Indeed, Private Relay is (in part) a contributory factor.

In simple terms, Private Relay is one of Apple's many privacy technologies, this feature being designed to inhibit tracking by hiding the true IP source address of the user's traffic. Notwithstanding the limited IP address-pool utilised by the Apple Private Relay service, when using Private Relay, the IP address associated with a session regularly changes. Private Relay critically and effectively disrupts one element of Google's profiling/tracking.

If utilised, turning-off Private Relay removes its protection for all your traffic - not just browsing.  Leaving Private Relay enabled, but signing in to Google services, will suppress the annoyance presented by Google while preserving the benefits afforded by Private Relay for other traffic.

Clearly, the suggested workaround-measure sacrifices privacy from Google's [arguably insidious] gaze, but this is ultimately the crux of the issue. Google's countermeasure for technologies designed to block its own core business interest, is facilitated by "encouraging" an end-user to weaken their security posture - either by signing-in to Google services, or though adding annoyances that result in temporary relaxation of security/privacy measures.

Perhaps unsurprisingly, inhibiting data collection impacts Google's core marketable business asset - this being data relating to end-user habits, interests, browsing habits and associated internet activity.

This tedious behaviour can be suppressed by ensuring that you have signed-in to your Google account.

Apple's built-in web-tracking defences are so good that Google seemingly has difficulty with reliable device fingerprinting for user tracking. Remember, Google's main business interest is user-profiling for targeted advertising.

Signing-in to any Google service with your Google Account credentials should resolve your current frustration - at the expense of allowing Google limited ability to follow your individual browsing habits.

It's been a problem for me for a long time (I'm still on Sequoia). If I recall correctly from when I tried to fix it the accepted web sentiment is that for some reason Safari seems to get stuck in a loop and sends the search request to Google repeatedly which Google interprets as the search coming from a bot and therefore requires a catcha to prove you're human.

I too have switched Safari's default search to DDG, although I'm gradually shifting away from Safari because of this and other problems. I find that DDG isn't as good a search engine as Google and Google works fine in Firefox, so that's what I tend to use now.

It's not because Safari's web-tracking defences are good. I use Brave and I use Firefox with a variety of privacy and JS shields and it has no problems with Google search - and I haven't got a Google account. This particular Safari problem can be caused by having Private Relay turned on or, as in my case, because Safari re-submits the query many times and as a result Google thinks that the request comes from a bot.

If the OP has Private Relay turned on then they should turn it off.

Google search works fine in FF with FF's strict tracker blocking turned on and the site fixes option disabled - settings which break many sites. I've also got a JS blocker which blocks the Google trackers, uBlock Origin as belt and braces and AdBlock. Google works fine through all these shields. Google search also works fine in Brave - a browser designed specifically for privacy.

I understand the prevailing view round these parts that Apple is automatically better, but the limitations of Safari Webkit are well documented. This is a Safari problem, not a Google problem. The OP should give feedback.

Product Feedback - Apple

It looks like you're trying to access search in private browsing. Does it happen in a regular window?

I don't use DuckDuckGo, but I do use Google search, and I'm never confronted with a verification request.

Zurarczurx wrote:

Google search works fine in FF with FF's strict tracker blocking turned on and the site fixes option disabled - settings which break many sites. I've also got a JS blocker which blocks the Google trackers, uBlock Origin as belt and braces and AdBlock. Google works fine through all these shields. Google search also works fine in Brave - a browser designed specifically for privacy.

I understand the prevailing view round these parts that Apple is automatically better, but the limitations of Safari Webkit are well documented. This is a Safari problem, not a Google problem. The OP should give feedback.

Product Feedback - Apple

At no point have I suggested that Apple's features or associated capabilities are any better or worse than those provided by other measures.

However, objectively and in absence of definitive evidence to the contrary, it might be reasonably argued that the alternative measures (that you ably describe) are perhaps less effective in blocking Google's sophisticated tracking and profiling. In not seeing Google's prompt, this may be good indicator that Google is maintaining its capabilities... 🙂