Washington Post detects as "Private"

[BKelley56]

I wish this worked in Chromium browser. It did at first, now it doesn't. Works in Palemoon though!!!

You can get rid of this nonsense by using uBlock Origin and add the following line in the "My Filters" section:

Code: Select all

washingtonpost.com##^script:has-text(Turn off private browsing)

and hit "Apply changes"

I had the same warning and I don't even use private mode...

[Edit]
How to install uBlock Origin in Pale Moon

[nicolaasjan]

I wish this worked in Chromium browser. It did at first, now it doesn't. Works in Palemoon though!!!

You can get rid of this nonsense by using uBlock Origin and add the following line in the "My Filters" section:

Code: Select all

washingtonpost.com##^script:has-text(Turn off private browsing)

and hit "Apply changes"

I had the same warning and I don't even use private mode...

[Edit]
How to install uBlock Origin in Pale Moon

For Chrome or Chromium there is another filter in 'uBlock filters' blocking this:

Code: Select all

washingtonpost.com##+js(acis, document.querySelector, "0x)

This was added on October 10^th
With Chromium I have no problems accessing washingtonpost.com.

Are your filters up to date?

[Moonraker]

With ublock origin enabled i can browse the site just fine with no private browsing overlay banner.

[BKelley56]

I wish this worked in Chromium browser. It did at first, now it doesn't. Works in Palemoon though!!!

You can get rid of this nonsense by using uBlock Origin and add the following line in the "My Filters" section:

Code: Select all

washingtonpost.com##^script:has-text(Turn off private browsing)

and hit "Apply changes"

I had the same warning and I don't even use private mode...

[Edit]
How to install uBlock Origin in Pale Moon

For Chrome or Chromium there is another filter in 'uBlock filters' blocking this:

Code: Select all

washingtonpost.com##+js(acis, document.querySelector, "0x)

This was added on October 10^th
With Chromium I have no problems accessing washingtonpost.com.

Are your filters up to date?

I have UBlock Origin installed in Palemoon, and I have the filter statement that I referenced in the post above. That item you posted above, is that something that needs to be removed or installed? I'm a bit confused.

[RJARRRPCGP]

Same kind of bullplop for me, even when I disabled ABPrime!

[coffeebreak]

What currently works for me is a site-specific user agent override for washingtonpost.com using Pale Moon's native UA string for version 28.7.2.

[nicolaasjan]

I wish this worked in Chromium browser. It did at first, now it doesn't. Works in Palemoon though!!!

You can get rid of this nonsense by using uBlock Origin and add the following line in the "My Filters" section:

Code: Select all

washingtonpost.com##^script:has-text(Turn off private browsing)

and hit "Apply changes"

I had the same warning and I don't even use private mode...

[Edit]
How to install uBlock Origin in Pale Moon

For Chrome or Chromium there is another filter in 'uBlock filters' blocking this:

Code: Select all

washingtonpost.com##+js(acis, document.querySelector, "0x)

This was added on October 10^th
With Chromium I have no problems accessing washingtonpost.com.

Are your filters up to date?

I have UBlock Origin installed in Palemoon, and I have the filter statement that I referenced in the post above. That item you posted above, is that something that needs to be removed or installed? I'm a bit confused.

I presume you mean :

Code: Select all

washingtonpost.com##+js(acis, document.querySelector, "0x)

That filter is part of the default uBlock filters and is meant just for Chromium browsers as you can see in
chrome://ublock0/content/asset-viewer.html?url=ublock-filters
when you search in there for 'washingtonpost.com' :
You will see :

Code: Select all

!#if env_chromium
washingtonpost.com##+js(acis, document.querySelector, "0x)
!#endif

So you don't have to remove or add anything.
I advise you to at least enable all available uBlock filters :



If you still have the problem in Chromium, this is obviously not the place to ask for support.
Instead you can try here or here.

[RJARRRPCGP]

What currently works for me is a site-specific user agent override for washingtonpost.com using Pale Moon's native UA string for version 28.7.2.

Now, it looks like the server-end will ban you, with a false-private-mode error report, until you enter the following for the UA:

general.useragent.override.washingtonpost.com

rv:60.9) Goanna/4.4 PaleMoon/28.7.2 (The text I snipped off is OS information, other than the "Mozilla/5.0" string.)

Or

Goanna/4.4 PaleMoon/28.7.2

For Windows 7 SP1, this means the following string:

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.9) Goanna/4.4 PaleMoon/28.7.2

Is the "rv:"section to report the version of Firefox to report??? Or is that regarding the OS??? That looks like a UA to report Firefox 60.9, to me.

[coffeebreak]

the "rv:"section

AFAIU it refers to the Gecko release version. (see 1, 2)

People's native user agents will vary a little depending on their OS (and its architecture) and their browser's architecture. Anyone can find their own native UA by first selecting Native mode in preferences, and then opening either about:support or about: since the user agent displays on both of those pages.

My own native UA is: Mozilla/5.0 (Windows NT 6.1; rv:60.9) Goanna/4.4 PaleMoon/28.7.2
(because Windows 7 x86)