Category Archives: Google

AI site scraper bots are overwhelming web sites

In the never-ending search for content to feed into their Large Language Models, ‘AI’ companies are using distributed networks of bots (automated programs) to download the contents of web sites everywhere on the Internet. Many sites are being overwhelmed by this traffic. Some site owners are being forced to upgrade their hosting service, while others have simply shut down.

If your response to that is to point out that Google does the exact same thing, and has for years, you’d be right, except for a few important differences:

  • Google’s searchbot doesn’t try to download every page on every web site. It’s much more selective about what it grabs.
  • Googlebot clearly identifies itself, which makes it much easier to classify its requests and limit its impact. The vast majority of ‘AI’ scraper bots falsely identify themselves as ordinary web users.
  • Google publishes a list of host IP ranges used by Googlebot, and they consist of specific, limited subnets that are clearly owned by Google. The vast majority of ‘AI’ scraper bots are spread around the world, on largely unrelated groups of hosts, often running on virtual private servers owned by VPS providers.
  • When Googlebot crawls your site, one or two hosts read a small batch of related/linked pages, then go away and come back for more later. ‘AI’ crawlers spread their requests across hundreds or even thousands of hosts, each one reading as little as one page, which makes identifying and blocking them difficult.

All of these things make the job of managing traffic for a web site much more difficult than it was before the current ‘AI’ boom.

In my work on managing traffic for clients, I have been lucky in that two of them are not legally allowed to sell to anyone outside of Canada. For those clients, I eventually just blocked traffic from every country except Canada. Traffic from major search providers is always allowed, and special procedures are required for certificate updates, but this made a huge difference. Web sites that need traffic from other countries obviously can’t use this drastic approach.

Thankfully, all of this pointless and damaging traffic will stop when the current ‘AI’ bubble bursts, and that can’t come soon enough for me.

The Register talks about this, describing the new ‘AI’ crawlers as site destroyers, which is accurate.

Here’s Drew Curtis, the owner/operator of the long running humour site fark.com, talking about this problem.

The EFF posted about this problem and suggests some solutions.

There has been some progress on ‘local models’, which refers to running LLM ‘AI’ software locally (i.e. on your own computer). The idea is that if you can run an LLM on your own computer, you don’t have to pay for the use of commercial services. And local models do actually work, but with much less useful results. Your laptop just doesn’t have the processing power to produce truly useful results. According to Sean Goedecke, this is unlikely to change, even with significant increases in processing power. So the ability to run local models will not have any effect on the deluge of traffic hitting web sites.

Google Search ‘Classic’

You may have noticed that Google Search results are getting crappier. The ads are still fairly unobtrusive, but a typical search results page is filled with other junk that is often of no interest at all.

The good news is that Google just enabled a new feature in Search that may remind you of the good old days when search results were less cluttered. It’s called ‘Web search’. No kidding.

Google's new web search feature

To see Web search in action, go to google.com and search for something. Near the top of the search results page, you should see a horizontal menu, starting with ‘All’, ‘Images’, and ‘Videos’. Click the ‘More’ entry, and select ‘Web’.

As you can see, this cleans up the results page significantly.

I like this feature so much that I’ve made it my default search in Firefox. Here’s how to do that:

  1. By default, you can’t add custom search engines to Firefox. To enable that function, enter about:config in Firefox’s address bar and press Enter. You’ll be asked if you’re sure you want to proceed; click ‘Accept the risk’. Then type browser.urlbar.update2.engineAliasRefresh. You should see a small ‘+’ box to the right. Click that.
  2. Click Firefox’s ‘hamburger’ menu button, which looks like three horizontal lines, at the top right. Select ‘Settings’.
  3. Click ‘Search’ in the left sidebar.
  4. Firefox search settings

  5. Scroll down to the ‘Search Shortcuts’ list. At the botton of that list, there should be an ‘Add’ button. Click that.
  6. Firefox Add Search dialogIn the small dialog that appears, enter a name for the new search (I call it ‘Google Classic’), the URL https://www.google.com/search?q=%s&udm=14, and then give it a shortcut alias like ‘gc’. Then click ‘Add Engine’.
  7. Scroll up the Settings page until you see ‘Default Search Engine’. Click the drop-down list and select the search engine you just added.

After making these changes, searches you perform in Firefox (by entering search terms in the address bar or search box) should produce ‘Web’ search results.

Changes coming to Chromium and Firefox

There’s interesting news from the world of web browser software. And when I say ‘interesting’, I mean possibly extremely annoying, depending on which browsers you use, and how you use them.

First up, there’s been an interesting debate in the Firefox bug list, since 2014, about whether to change the behaviour of the Backspace key.

It’s possible that you weren’t even aware that you could use your keyboard’s Backspace key to navigate to the previous page in Firefox. This functionality has existed in most browsers at one time or another, but it was removed in Google Chrome version 52 in July 2016. It’s a convenient shortcut for doing the most common thing you can do in a web browser, and I have personally used it for years.

The problem is that some users apparently run into trouble when they try to use Backspace to erase the previous character in a text box on a web page, such as in a form, only to find that they have navigated to the previous page instead. This can result in the loss of form data, and I imagine that could be very annoying.

Because of the debate about this, Mozilla software engineers went so far as to track the usage of the Backspace key in Firefox. And while I applaud their methods, I don’t necessarily agree with their analysis. For example, they found that the Backspace key is the most pressed keyboard shortcut in Firefox, with forty million users pressing the key and triggering a ‘previous page’ navigation every month.

By comparison, the next most common keypress is Ctrl-F, which is the browser-universal key combination for searching within the current page. That keypress is used by about sixteen million users per month. Fifteen million users per month use F5 and Ctrl-R to reload the current page.

So far so good, but the Mozilla engineers somehow used this information to conclude that many of the Backspace presses (and subsequent navigation to the previous page) were unintentional. I don’t follow their reasoning, frankly. Isn’t it just as likely that that people frequently use the Backspace key to go to the previous page?

Regardless, Mozilla is changing the behaviour of the Backspace key in Firefox from version 86 onwards. That version is scheduled for release on February 23, 2021. There will be workarounds, so this isn’t likely to be a huge problem for most people, but there will clearly be a bit of fumbling as people get used to the change.


Meanwhile, Google is planning to cut off access to several of its services for Chromium-based web browser software, on March 15, 2021. This won’t affect Google’s own Chrome browser, but any browser built on the Chromium browser engine that isn’t Chrome will lose access on March 15.

The Google services involved include bookmark synchronization, the ‘safe browsing’ feature, search suggestions, spell checking, and others. It’s important to recognize that these functions are not necessary for basic browser use, and their loss likely won’t affect many users. Losing search suggestions and spell checking seem like minor annoyances at worst. Loss of the safe browsing feature is unfortunate, but other safeguards exist. Anyone who uses bookmark sync is going to be annoyed at losing that feature.

At the same time, it’s interesting to note that people who are using a non-Chrome Chromium browser to avoid using Google software never really accompished their goal if they used any of the soon-to-be-disabled features. They might as well have been using Chrome all along.

Google maintains that it was never their intention to make these services available to non-Chrome browsers. Which is why, despite having frequently expressed annoyance at Google for discontinuing software and services that they had strenuously promoted, this change doesn’t bother me.

Related articles

Chrome 81.0.4044.92

A new version of Chrome addresses thirty-two security issues in previous versions.

Details of the vulnerabilities fixed in Chrome 81.0.4044.92 are sketchy, which is normal for newly-discovered and mostly unpatched security bugs. Google has published vulnerability identifiers (CVE numbers), along with links to Google’s internal bug tracking system, and credited the researchers who discovered them.

The links are mostly non-functional, and will remain so until Google decides that it’s safe to publish the vulnerability details. Even the CVE numbers aren’t that helpful: if you search the CVE list at Mitre.org for one of these recent vulnerabilities, you’ll see a placeholder page with no details — for now.

In a perfect world, it would be easy to discover exactly what a software update would change, before it’s installed. Sadly, opportunistic assholes have made this impractical and even dangerous for security-related updates. So, regardless of how one feels about the developer, at some level we have no choice but to trust them with security updates.

Chrome’s ‘three vertical dots’ menu is the place to start if you want to check which version you’re running and install an update. Drill down to Help > About Google Chrome. If an update is available, it will be installed automatically, after which you’ll see a Relaunch button.

Chrome 80.0.3987.162 and 80.0.3987.163

Two Chrome releases this week address at least eight security vulnerabilities and other bugs.

The release notes for Chrome 80.0.3987.162 provide details for some of the security vulnerabilities. A usual, Google holds off publishing vulnerability details until most installs have been updated.

Chrome 80.0.3987.163 appears to roll back a bug fix that was addressed in an earlier version.

You can trust Google to update your installation of Chrome, or do it youself, by navigating its three-vertical-dots menu to Help > About Google Chrome. This will trigger a check for updates, and if a newer version is available, you should see an Update button or link.

Chrome 80.0.3987.149

Version 80.0.3987.149 of Google’s Chrome web browser is a security release. It includes fixes for at least thirteen security vulnerabilities.

Like most modern browsers, and many of Google’s software products, Chrome updates itself reliably, if somewhat unpredictably. This is arguably a good thing, as long as updates don’t break things and do improve security.

Regardless of your viewpoint on automatic updates, keeping your web browser up to date is critical if you use it to do any actual web browsing. Otherwise the risk of a drive-by malware infection is significantly higher.

To check the version of your Chrome browser, navigate its three-vertical-dots menu to Help > About Google Chrome. If there’s a newer version, you’ll see a button or link for installing it.

Chrome 80.0.3987.122

Three more security vulnerabilities are fixed in the latest Chrome, version 80.0.3987.122.

According to the release notes, one of the vulnerabilities fixed in Chrome 80.0.3987.122 is already being exploited ‘in the wild’ so anyone using Chrome should check their version and update immediately.

To determine whether you need to install the new version, navigate Chrome’s menu button () to Help > About Google Chrome. You’ll see the current version, and if a newer one is available, there should be a button that allows you to install it.

Chrome 80.0.3987.116

Sometimes when Google releases a new version of Chrome, the release announcement doesn’t mention any security fixes. That’s intentional:

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.

Chrome 80.0.3987.116 was announced on February 18, but the initial announcement didn’t include any mention of five security vulnerabilities that were fixed in that version. Those details were added a few days later.

Three of the vulnerabilities addressed in Chrome 80.0.3987.116 were reported to Google by third party security researchers.

To check your current version of Chrome, click its menu button (three vertical dots) and navigate to Help > About Google Chrome. If a newer version is available, you should see a button or link that allows you to install it.

Chrome 80.0.3987.87

The latest release of Google’s Chrome web browser, announced on February 4, includes fifty-six security fixes. As usual, details on all of the related vulnerabilities will not be released until a majority of users are updated with a fix.

The full change log for Chrome 80.0.3987.87 is a whopper, with over sixteen thousand changes in all. A little light reading for anyone with a few hours to spare. But hey, at this point if you don’t trust Google you probably shouldn’t be using Chrome. In the same way that you shouldn’t be using Windows 10 if you don’t trust Microsoft.

Chrome updates itself on its own mysterious schedule, unless you’ve taken extreme (and continuous) measures to prevent it. You can find out which version you’re running by navigating Chrome’s menu (hidden behind the three-vertical-dots menu button at the top right) to Help > About Google Chrome. If a newer version is available, you should see a button or link to install it.