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

Issues with Instart Logic sites #96

Open
NilsEnevoldsen opened this issue Aug 16, 2018 · 0 comments
Open

Issues with Instart Logic sites #96

NilsEnevoldsen opened this issue Aug 16, 2018 · 0 comments

Comments

@NilsEnevoldsen
Copy link
Contributor

NilsEnevoldsen commented Aug 16, 2018

Instart Logic is an adblock-circumventing service that uses a "nanovisor" (often identifiable by the string g00) to make third-party requests appear as first-party requests.

A long list of sites using Instart Logic is given in the background links below, but I am specifically having trouble with Gamepedia sites such as https://mtg.gamepedia.com and https://dota2.gamepedia.com.

When loading these sites with Ka-Block! 3.1, many images are broken. On closer inspection, this is because the images do not have a src attribute, but rather a x-defer-src attribute. There is javascript to un-break this attribute, but it's (sorta correctly) blocked by the sdad\\.guru rule.

I tried creating the following rule…

[
    {
        "trigger": {
            "url-filter": "/g00/"
        },
        "action": {
            "type": "block"
        }
    }
]

…but this doesn't work because the main page (e.g. https://mtg.gamepedia.com/Main_Page) uses inline javascript to navigate to a page with g00 in it (e.g. https://mtg.gamepedia.com/g00/Main_Page?i10c.encReferrer=&i10c.ua=4, but it then rewrites the URL as https://mtg.gamepedia.com/Main_Page to hide the fact that it navigated you), which results in a Safari error page. If you disable javascript entirely, you can verify that the images do have src attributes at the original page, and it's only the g00 page that has obfuscated them.

I don't know if Safari Content Blockers have the tools to deal with this. uBlock Origin uses websockets to solve this issue. It seems like preventing inline javascript from navigating to a blocked page (as opposed to navigating to a Safari error page) would be a partial solution, but I don't know if that's possible.

P.S. Thanks for Ka-Block! ❤️

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

1 participant