[NSFW] 20.gay And Gay20.com UBlock Origin Detection How To Fix

by StackCamp Team 63 views

Hey guys! Let's dive into this issue of uBlock Origin being detected on 20.gay and gay20.com. It's super frustrating when websites figure out you're using an ad blocker and then bug you to turn it off. We're going to break down the problem, look at the details, and figure out how to fix it. So, let's get started!

Prerequisites

First off, the person reporting this issue has gone through a checklist to make sure it's a genuine problem and not something caused by other factors. They've confirmed that this isn't a typical issue related to YouTube, Facebook, Twitch, or a shortener/hosting site. They've also made sure to read the policy on what makes a valid filter issue. This is awesome because it helps us focus on real problems and avoid wasting time on duplicates or misconfigurations.

  • [x] Not a YouTube, Facebook, Twitch, or shortener/hosting site issue
  • [x] Read and understood the policy
  • [x] Verified it's not a duplicate
  • [x] Didn't remove default filter lists
  • [x] No additional filter lists enabled
  • [x] No custom filters/rules
  • [x] Verified no interference from browser's content blocker, DNS blocking, or VPN
  • [x] All other extensions turned off
  • [x] Issue caused by uBlock Origin, not site or browser
  • [x] Browser is up to date
  • [x] Truthfully answered all checkboxes

This thoroughness is super helpful because it means we can trust that the issue is specific to uBlock Origin and the website in question.

The Problem: Detection on 20.gay and gay20.com

Website URLs:

  • https://20.gay/
  • https://gay20.com/

Category: Detection

Description: The core issue here is that the webpages are detecting the presence of uBlock Origin and prompting users to disable the extension. This is a common tactic websites use to try and force users to view ads, which can be super annoying. The goal is to prevent this detection so users can browse without being nagged or having their experience disrupted.

Why is This Happening?

Websites use various techniques to detect ad blockers. These can range from simple checks for the presence of ad-blocking JavaScript libraries to more sophisticated methods that analyze network requests and DOM modifications. When a site detects an ad blocker, it can display messages, block content, or even redirect users.

For example, websites might use JavaScript code to check if specific ad-serving domains are blocked. If they are, the site knows an ad blocker is active. Another method involves creating dummy ad elements and seeing if they get blocked. If they do, the site again infers that an ad blocker is in use.

Understanding Detection Methods

  • JavaScript Detection: Websites often embed JavaScript code that checks for the presence of ad blockers. This can involve looking for specific variables or functions that ad blockers are known to modify or block.
  • Dummy Elements: Some sites create dummy ad elements and see if they are blocked by the ad blocker. If these elements are blocked, the site assumes an ad blocker is active.
  • Network Request Analysis: Websites can monitor network requests to see if requests to known ad-serving domains are being blocked. If they are, it’s a strong indicator that an ad blocker is in use.

User Details

Browser: Opera

Other Extensions Used: None (which is great for troubleshooting!)

Country: No response (This info can sometimes be helpful but isn't critical here.)

Screenshot:

Based on the provided screenshot, we can see the typical message that websites display when they detect an ad blocker. It usually asks the user to disable the ad blocker to continue browsing the site. This is what we're trying to prevent.

Configuration Details

It's super helpful that the reporter included their uBlock Origin configuration details. This gives us a snapshot of their setup, including the versions of uBlock Origin and Chromium, the filter lists they're using, and any custom settings. Here’s a breakdown:

uBlock Origin: 1.65.0
Chromium: 135
filterset (summary):
 network: 169828
 cosmetic: 52539
 scriptlet: 25504
 html: 0
listset (total-discarded, last-updated):
 default:
 user-filters: 0-0, never
 ublock-filters: 40527-307, 4m Δ
 ublock-badware: 11370-18, 4m Δ
 ublock-privacy: 3373-2, 4m Δ
 ublock-unbreak: 2663-0, 4m Δ
 ublock-quick-fixes: 289-0, 4m Δ
 easylist: 76679-413, 4m Δ
 easyprivacy: 54365-584, 4m Δ
 urlhaus-1: 31665-0, now
 plowe-0: 3420-0, now
 CHN-0: 25044-57, now
filterset (user): [empty]
userSettings: [none]
hiddenSettings: [none]
supportStats:
 allReadyAfter: 510 ms (selfie)
 maxAssetCacheWait: 50 ms
 cacheBackend: indexedDB
popupPanel:
 blocked: 3
 network:
 jads.co: 1
 juicyads.com: 2

Key Configuration Points

  • uBlock Origin Version: 1.65.0
  • Chromium Version: 135
  • Filter Lists: The user is using a pretty standard set of filter lists, including the uBlock filters, EasyList, EasyPrivacy, and others. This is a good starting point.
  • User Filters: No custom filters are in place, which simplifies troubleshooting.
  • Blocked Domains: jads.co and juicyads.com are being blocked, which are known ad-serving domains. This is normal and expected.

Steps to Resolve the Detection Issue

Okay, so we know the problem and have a good understanding of the setup. Now, let's talk about how to fix this. Here’s a step-by-step approach we can take:

1. Update Filter Lists

The first thing to try is updating the filter lists. Sometimes, the fix is as simple as that. New filters are added regularly to combat ad-blocker detection methods.

  • How to do it: Open uBlock Origin’s dashboard, go to the “Filter lists” tab, and click “Update now.”

2. Add Specific Filters

If updating the filter lists doesn’t work, we can try adding specific filters to address the detection on these sites. This is where we might need to get a little technical, but it's totally doable.

  • How to do it: Go to the “My filters” tab in uBlock Origin’s dashboard and add the following filters (we'll come up with the actual filters in the next step):

    # Add filters here

3. Investigate and Create Filters

To create effective filters, we need to investigate how the site is detecting uBlock Origin. We can use the browser’s developer tools (usually accessed by pressing F12) to look at network requests and JavaScript code.

  • Steps to investigate:
    1. Open the developer tools and go to the “Network” tab.
    2. Reload the page.
    3. Look for any suspicious requests or scripts that might be related to ad-blocker detection.
    4. Check the “Console” tab for any error messages or warnings that could give us clues.
    5. Use the “Sources” tab to inspect the site’s JavaScript code and look for detection scripts.

4. Potential Filter Solutions

Based on common detection methods, here are a few potential filters we might try:

  • Blocking Detection Scripts:

    ||20.gay/path/to/detection/script.js$script
||gay20.com/path/to/detection/script.js$script

    Replace /path/to/detection/script.js with the actual path of the detection script if we find one.

  • Cosmetic Filters (hiding elements):

    20.gay##.detection-message-class
gay20.com##.detection-message-class

    Replace .detection-message-class with the actual CSS class of the detection message element.

  • Inline Script Blocking:

    20.gay##+js(abort-on-property-read, detectedAdBlock)

gay20.com##+js(abort-on-property-read, detectedAdBlock) ```

This filter attempts to block scripts that try to read a property named `detectedAdBlock`, which is a common detection technique.

5. Test and Refine Filters

After adding filters, it’s crucial to test them to make sure they work without breaking the site. If a filter is too aggressive, it might block essential functionality.

  • Testing:
    1. Reload the page after adding a filter.
    2. Check if the detection message is gone.
    3. Make sure the site still works as expected.
    4. If something breaks, remove or modify the filter.

6. Report Back and Share Solutions

Once we find a working solution, it’s super important to report back. This helps others who might be experiencing the same issue. We can share the filters we’ve created so they can be added to the filter lists and benefit everyone.

Example: Let's Say We Found a Detection Script

Okay, let's walk through a hypothetical example. Imagine we used the developer tools and found a script at https://20.gay/js/detect.js that seems to be responsible for the detection. We could add the following filter:

||20.gay/js/detect.js$script

This filter tells uBlock Origin to block the script, preventing the detection from running. We would then test the site to make sure everything still works as expected.

Staying Ahead of the Game

Ad-blocker detection is an ongoing game of cat and mouse. Websites are constantly trying new techniques, and ad blockers have to adapt. By understanding how these detections work and being proactive in creating filters, we can stay one step ahead.

Tips for Staying Updated

  • Regularly update filter lists: This is the easiest way to get the latest protections.
  • Monitor community discussions: Keep an eye on forums and communities where people discuss ad-blocking issues and share solutions.
  • Learn basic filter syntax: Understanding how filters work allows you to create your own solutions.

Final Thoughts

Dealing with ad-blocker detection can be a bit of a hassle, but it’s totally manageable. By following these steps – updating filter lists, investigating detection methods, creating specific filters, and sharing solutions – we can keep our browsing experience clean and ad-free. So, let's keep those filters sharp and enjoy a less intrusive web!