Conversation
|
Sorry for asking this here but:
Any reason for it being that long? A shorter update interval of maybe a few hours could be useful for lists such as Yhonay/antipopads which have a high update frequency. Thanks for this huge update by the way. |
|
I just mind the hit on the remote servers. |
|
That makes sense. I just thought whoever uploads the list can decide how much load they want to have on their server by updating the |
Does this also apply to |
No What I could do is to automatically mark |
The removed code was quite old, and was about how user filters were persisted before/after uBO version 1.11, related to the following issue: - #2314 The assets storage refactoring was released in: - https://github.com/gorhill/uBlock/releases/tag/1.11.0
This fixes the following issues: #2281, #2037, #1961, #1749, #1429, #1293, #1275, #344.
The purpose of the refactoring was to address many issues arising from the old assets management code:
Expires:directive in Adblock Plus-compatible filter lists, if present. However the minimal interval is set to 2 days.checksums.txtresource hosted on GitHub to find out whether some specific assets have changed: the update logic is now completely time-based.checksums.txtwill be deprecated and will no longer be updated. Eventually in some future it will be removed from the repository.assets/assets.json, which is itself an update-able asset from uBO's point of view.assetsBootstrapLocationcan be used by derivative works of uBO to provide a different set of stock assets, including which filter lists should be enabled by default at install time. There is also a corresponding settingassetsBootstrapLocationwhich can be used by admins to tell uBO what are the stock assets and which filter lists are enabled by default at install time.assets/ublock/filter-lists.jsonwill be deprecated and will no longer be updated. Eventually in some future it will be removed from the repository.