Remove from project all filter lists which are not selected by default #602
Comments
|
i was about to ask for the implementation of a 'select all' option, which would be useful but partially moot if this change occurs |
|
I would have not accepted to implement such feature anyways. |
|
ok, why not (out of interest)? |
|
Common sense (see Tips). The question is rather why would someone want to do this? |
|
couldn't it be faster to deselect the undesired or -necessary lists than selecting individually the ones that should be active. i haven't compared the content of the lists in detail so, it could mostly be pointless i suppose. |
gorhill
added a commit
that referenced
this issue
Aug 17, 2015
- When #602 is completely fixed, the only filter lists packaged with the extension will be those which are selected by default out-of-the-box. So scripts to update 3rd-party assets have been changed for this. - Removed "bad" filter lists: - "ESP: Filtros Nauscopicos": no longer maintained - "ROU: RO-LIST": contains questionable exception filters. (See: uBlock-LLC/uBlock#693)
gorhill
added a commit
that referenced
this issue
Aug 17, 2015
All the assets which are not selected by default out-of-the-box will be converted into an empty file. This is a first step, the final step will be to removed completely the files from the package once everybody is using v1.1.0.0+.
gorhill
added a commit
that referenced
this issue
Aug 18, 2015
|
Fixed in efccaf1. |
gorhill
added a commit
that referenced
this issue
Aug 25, 2015
gorhill
added a commit
that referenced
this issue
Aug 25, 2015
External filter lists are not meant to appear in checksums.txt.
This was referenced Aug 26, 2015
Closed
gorhill
added a commit
that referenced
this issue
Nov 25, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
They cause the package to be too large.
The 3rd-party filters pane will still allow to easily select these non-default 3rd-party filter lists, only difference is that they will have to be downloaded the first time they are selected (this already happens anyway for most 3rd-party filter lists -- to fetch latest versions). A couple of current stock 3rd-party filter lists are already natively remotely fetched (not part of uBlock's package).
The transition needs to be completely transparent to users (as in nothing to do), and this requires
filter-lists.jsonto be backward compatible until all uBlock Origin installations have been updated to deal with the filter lists which are now pointing strictly to their remote locations.The text was updated successfully, but these errors were encountered: