-
Notifications
You must be signed in to change notification settings - Fork 48
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
sublists #67
Comments
I would ultimately like to do this but need to research how some of the other lists maintainers manage this before doing so. It's also a time commitment that I don't have right now to implement immediately. |
You can just divide it into few files, then use |
* Test of subfilter lists * Update ultralist.txt * Update ultralist.txt Relates to #67
Forgot this was still open, thanks for closing @KonoromiHimaries |
…bscription Add CSS Style Companion Filter List - this list will be for elements that should be removed and *only* loaded when either ultralist.txt (and all corresponding sublists) or *just* css_style_filters.txt are enabled. Related #67
…bscription Add CSS Style Companion Filter List - this list will be for elements that should be removed and *only* loaded when either ultralist.txt (and all corresponding sublists) or *just* css_style_filters.txt are enabled. Related #67
Delete css_style_companion_filters.txt Related #67
… & update boardingarea.com filters Related: #67
Sublist for filters related to empty advertising placeholders. The intention with this sublist is to remove all of these currently existing filters from `utlralist.txt` so eventually `ultralist.txt` is ONLY a list that exists to subscribes to all sublists. This will allow the flexibility for users to only subscribe to certain features of ultralist.txt e.g. only remove newsletter & empty ad boxes but don't change any CSS elements like sticky headers. (e.g. don't subscribe to `css_style_filters.txt` Relates to #67
Moving forward, I will be moving empty advertising filters into the The long-term intention with This should allow the flexibility for users to only subscribe to certain features of Web Annoyances Ultralist e.g. users who only want to remove social buttons & empty ad boxes but don't want to change any CSS elements of a site like sticky headers or newsletter subscription requests (e.g. don't subscribe to This is also the reason behind recently creating |
Reopening to help others track maintenance progress of moving existing filters from |
move ultralist.txt filters to sublists Related #67
…filters from ultralist.txt to sublist Related #67
…ilters from ultralist.txt to sublists Related #67
…investors.com,marieclaire.com,popularmechanics.com,roadandtrack.com,runnersworld.com,shondaland.com,si.com,townandcountrymag.com & move filters from ultralist.txt into sublists Related #67
Related #67 Move mariettatimes.com -> marthastewart.com from ultralist.txt to sublists
It might make sense to give cookie/gdpr filters their own sublist. Also, I see a bunch of social filters in the generic sublist. I'd be happy to submit a pull request for one or both of these if you're interested. |
Should paywall filters go in a separate list too? And what's the policy in this repo? Are all paywalls removed when possible? |
@GeneralKenobi1 I agree with splitting up cookie/gdpr filters - I can create a new sublist for that and I would be happy to accept a PR - Right now most of those filters would be in the @llacb47 I prefer not to have a separate paywall sublist, the general policy for Web Annoyances Ultralist is to remove them if it's a soft paywall/warning that only requires modifying CSS or blocking a 1st or 3rd party script - no script injection workarounds or faking subscription status. There are separate extensions users can use if they want to go that route, e.g. Bypass Paywalls Clean for Firefox & Bypass Paywalls Clean for Chrome or even something as simple as Cookie Auto Delete for Firefox & Cookie Auto Delete for Chrome |
There's a paywall scriptlet bypass right here, are you going to remove it? :P https://github.com/yourduskquibbles/webannoyances/blob/master/ultralist.txt#L186 |
@GeneralKenobi1 I just added a new |
Looks like that is just removing a cosmetic DOM element, not injecting scripts or changing the page content that isn't already loaded in the DOM when a user navigates to the page? |
Line 186 in 8a0a299
I'm not saying you should remove it by the way, just saying this policy limits how much paywall bypassing can be done |
I see you pointed to L186 in edit now, yes I will remove that, no need to create undue risk when other extensions exist. Probably added it a long time ago when I found the filter on reddit or something like that. Thanks for pointing out |
It's OK, it's not the intention or primary goal of this list to bypass paywalls so don't want to host that anyway and risk taking the whole project down. |
…-me*.*] to ad_placeholders.txt Related #67
This sublist is to address display issues caused by CSS companion filters removing content that shouldn't be removed on adguard for iOS due to CSS style modifying filters not being loaded (iOS & Safari design constraint) Related #67
@hawkeye116477 What exactly do you mean by autosorting? |
I mean that script will sort rules alphabetically. You can then set launching it through GitHub Actions for example twice per day, so it will be automatic process. |
do you can divide the webannoyances list into a sublists
example. you can based on the model of polishsubfilters
https://github.com/KonoromiHimaries/PolishSubFilters/tree/master/internal-filters
or polishannoyancefilters model
https://github.com/PolishFiltersTeam/PolishAnnoyanceFilters/tree/master/PPB
potential benefits
The text was updated successfully, but these errors were encountered: