Google starts requiring a captcha over time

[slifty]

One of the flaws with this approach is that the random and algorithmically generated queries look random and algorithmically generated.

In other words, Google can tell that it is a robot, and eventually if the wrong keyword combinations appear it may trigger a forced captcha.

Some possible solutions to explore:

1. Find an alternative URL source
2. Find a way to access the feeling lucky button
3. Change the frequency or general quantity of calls
4. ???

[slifty]

(One possible alternative source is duckduckgo)

[slifty]

@peterberbec you experimented with duckduckgo -- my main concern is that when I tried it I noticed a little bit more instances of attempted NSFW results (they didn't go through, but that could be disconcerting to users). What was your experience with the experiment?

[afxgit]

Tried startpage.com?

[peterberbec]

DDG paused if it hit NSFW if the safeoff tag wasn't on. not optimal.

Anyone know bing? Might be good to have M$ do something useful for once...

[slifty]

I lowered the number of tabs to just 2, which seems to be far less likely to start bothering google.

[slifty]

The lowered number of tabs seems to have significantly lowered the number of reports of captcha requests. They still happen, but not as often (and I have personally experienced them a lot less as well)