Skip to content

Prevent blocked words in generated hash #156

Open
@jens-duttke

Description

@jens-duttke

The most Adblockers block resources if they contain specific words in the file name.

While creating hashes for file names, this should be considered to make sure, resulting files don't get blocked, because of their filename.

Some examples of blocked patterns from the popular EasyList filter list:

.120x600.
120-600.gif|
.160x600.
160x600.jpg|
.300x250.
.468x60.
700_200.jpg|
.clkads.
.cyad1.
.intad.
.internads.
.mobileads.
.nativeads.
.popupvideoad.
.refreshAds.
.rolloverad.
.sponsorads.
.streamads.
.textads.
.theadtech.
.topad.
.videoad3.
.videoad4.

For the above patterns, we can deduce that atleast /(ad|\d{2,}[x_-]\d{2,})/i should be avoided.

Children projection filters may also filter files if their name contains words like "sex", "porn", "p0rn", "fuck", "shit", "tits", "suck", "wank", "anal", "penis" etc.

I think this should be considered a problem, since the number of adblock users is very high:
https://www.quora.com/What-percent-of-internet-users-use-adblock

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @jens-duttke

        Issue actions

          Prevent blocked words in generated hash · Issue #156 · webpack/loader-utils