Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hackr.io: detection #15655

Closed
8 of 9 tasks
Prakash4844 opened this issue Nov 13, 2022 · 9 comments
Closed
8 of 9 tasks

hackr.io: detection #15655

Prakash4844 opened this issue Nov 13, 2022 · 9 comments

Comments

@Prakash4844
Copy link

Prerequisites

  • I read and understood the policy as to what is a valid filter issue
  • I verified that the issue has not already been reported (use this button to find out)
  • I forced an update of my filter lists (how to do this: click "Purge all caches", then click "Update now")
  • I did not remove any of the default filter lists, or I verified that the issue is not caused by removing any of the default lists
  • I did not enable external filter lists, or I verified that the issue still occurs without enabling external filter lists
  • I do not have custom filters/rules, or I verified that the issue still occurs without custom filters/rules
  • I am not using another content blocker along uBO
  • I verified the issue is not caused by the browser built-in blocker, or DNS blocking (standalone or through VPN)
  • I did not answer truthfully to all the above checkpoints

URL address of the web page

https://hackr.io/

Category

detection

Describe the issue

Ublock Origin Gets Detected as Shown in Screenshot.

Screenshot(s)

Screenshot(s)

image

Configuration

uBlock Origin: 1.44.4
Chromium: 108
filterset (summary): 
  network: 91295
  cosmetic: 38589
  scriptlet: 16692
  html: 0
listset (total-discarded, last updated): 
  default: 
    user-filters: 12-0, never
    easylist: 64280-53, 7h.52m
    easyprivacy: 30822-1171, 2h.20m
    plowe-0: 3668-867, 4d.23h.31m
    ublock-abuse: 76-0, 4d.23h.33m
    ublock-badware: 3968-108, 1d.5h.34m
    ublock-filters: 31205-112, 1d.5h.32m
    ublock-privacy: 257-1, 4d.23h.34m
    ublock-quick-fixes: 533-14, 2h.18m
    ublock-unbreak: 1893-42, 2d.20h.34m
    urlhaus-1: 12389-0, 2h.19m
filterset (user): [array of 12 redacted]
trustedset: 
  added: [array of 30 redacted]
  removed: 
    edge-scheme
modifiedUserSettings: [none]
modifiedHiddenSettings: [none]
supportStats: 
  allReadyAfter: 37229 ms (selfie)
  maxAssetCacheWait: 1430 ms
popupPanel: 
  blocked: 32
  blockedDetails: 
    hackr.io: 10
    affilimate.io: 1
    doubleclick.net: 1
    ezodn.com: 1
    google-analytics.com: 1
    google.com: 5
    googleoptimize.com: 1
    googlesyndication.com: 1
    googletagmanager.com: 1
    hotjar.com: 1
    jobbio.com: 2
    quantserve.com: 1
    s-onetag.com: 1
    servenobid.com: 1
    sonobi.com: 1
    stakingsmile.com: 1
    unblockia.com: 1
    wisepops.com: 1
@stephenhawk8054
Copy link
Member

I can only reproduce if turning on Strict mode in Edge's Tracking Prevention. Check if you are using it or other extensions.

@Prakash4844
Copy link
Author

Yes, I checked I was using Strict Tracking Prevention
image

After Disabling it, Ublock Origin isn't detected anymore.

Thanks

@stephenhawk8054
Copy link
Member

Please check what you have ticked on carefully

  • I verified the issue is not caused by the browser built-in blocker, or DNS blocking (standalone or through VPN)

@mapx-
Copy link
Contributor

mapx- commented Nov 13, 2022

Weird, I'm still constantly getting anti adb in chrome (on normal refresh without bypassing the cache)

@stephenhawk8054
Copy link
Member

stephenhawk8054 commented Nov 13, 2022

Weird, I'm still constantly getting anti adb in chrome (on normal refresh without bypassing the cache)

Ah you're right, refreshing without bypassing cache triggers the anti-adblock again.


Confirm it's only on chromium.

@stephenhawk8054
Copy link
Member

This one works for me

hackr.io##+js(no-fetch-if, googlesyndication)

Can anyone else check it?

@mapx-
Copy link
Contributor

mapx- commented Nov 13, 2022

yes, working

@stephenhawk8054
Copy link
Member

@mapx- For the anti-adb can be closed by user, should the filter be moved to annoyances or stay in main list? I'm still not sure for the case when it can be closed but comes back after every refresh/new link.

@mapx-
Copy link
Contributor

mapx- commented Nov 13, 2022

it's ok in the main list. It would be annoyance if after closing it does not appear anymore (at least in the same session)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants