historicaerials.com: detection

[MustangMike96]

Prerequisites

• This is NOT a YouTube, Facebook, Twitch or a shortener/hosting site report. These sites MUST be reported by clicking their respective links.
• I read and understand the policy about what is a valid filter issue.
• I verified that this issue is not a duplicate. (Use this button to find out.). Comment in the old issue threads even when they are closed or even if you have a different problem.
• I did not remove any of the default filter lists, or I have verified that the issue was not caused by removing any of the default lists.
• I did not enable additional filter lists, or I have verified that the issue still occurs without enabling additional filter lists.
• I do not have custom filters/rules, or I have verified that the issue still occurs without custom filters/rules.
• I am not using uBlock Origin along with other content blockers.
• I have verified that the web browser's built-in content blocker/tracking protection, network wide/DNS blocking, or my VPN is not causing the issue.
• I have verified that other extensions are not causing the issue.
• If this is about a breakage or detection, I have verified that it is caused by uBlock Origin and isn't a site issue.
• I did not answer truthfully to ALL the above checkboxes.

URL address of the web page

https://www.historicaerials.com/viewer

Category

detection

Description

On two machines, the Historic Aerials viewer page is able to detect uBlock. It does not specify that it is uBlock, however that is the only blocker I use. I am able to replicate this issue in Firefox and Chrome on both of my machines.

On Firefox, I am able to inspect element and remove the popup. This has been happening for a month or so.

Other extensions used

I mainly use Firefox, so this is my list:
Old Reddit Redirect
Return YouTube Dislike
SponsorBlock for YouTube

Screenshot(s)

Screenshot(s)

Configuration

Details

uBlock Origin: 1.61.2
Firefox: 133
filterset (summary):
 network: 143362
 cosmetic: 49789
 scriptlet: 21458
 html: 2231
listset (total-discarded, last-updated):
 default:
  user-filters: 1-0, never
  ublock-filters: 41133-134, 4m Δ
  ublock-badware: 12522-1, 4m Δ
  ublock-privacy: 1652-23, 4m Δ
  ublock-unbreak: 2603-1, 4m Δ
  ublock-quick-fixes: 190-23, 4m Δ
  easylist: 78518-248, 4m Δ
  easyprivacy: 53317-71, 4m Δ
  urlhaus-1: 24990-0, now
  plowe-0: 3549-992, now
filterset (user): [array of 1 redacted]
userSettings: [none]
hiddenSettings: [none]
supportStats:
 allReadyAfter: 218 ms (selfie)
 maxAssetCacheWait: 85 ms
 cacheBackend: indexedDB
popupPanel:
 blocked: 11
 network:
  adroll.com: 1
  facebook.net: 1
  google-analytics.com: 1
  googlesyndication.com: 1
  googletagmanager.com: 1
  hotjar.com: 1
  pagefair.com: 1
  pub.network: 1
  twitter.com: 3
 extended:
  ###ad_left
  ###ad_right
  ##+js(no-setInterval-if, data-google-query-id)

[stephenhawk8054]

Fixed here: 682e9a8

[MustangMike96]

Ever since last week, https://www.historicaerials.com/viewer is once again able to detect uBlock and now I am unable to remove the warning. I have verified this on three separate machines and multiple browsers on each, and everything else from above is the same. The fix from mid-December worked well up until last week.

[anerdonamotorcycle]

Looks like this adblock detection is back, tested on a freshly installed and updated VirtualBox VM running Ubuntu 24.04, with both uBlock Origin on Firefox 135.0.1 and uBlock Origin Lite on Chromium 133.0.6943.141, both browsers running fresh profiles with no other add-ons installed, both versions of uBlock left set to their defaults, and no other adblocking running on my network.

[stephenhawk8054]

Fixed here: e40d889

[MustangMike96]

Fixed here: e40d889

Hello! The fix worked up until today. Between yesterday and today, Historic Aerials once again updated something in the background and is able to detect uBlock Origin again.

I tested this in separate browsers and on different machines. Some just display a gray overlay and do not let me click, but most will display a popup that tells me to disable the blocker.

@stephenhawk8054 would we be able to reopen this issue or should I make a new request?

[arencambre]

Since this was not reopened, I created a new issue at #30450

[liamengland1]

It was already fixed in a7f69e3, no need to open another issue @arencambre

[arencambre]

I’m confused. I opened the other issue because this one had not been reopened.