Start using new filters server instead of AG backend

[ameshkov]

Metadata

https://filters.adtidy.org/[platform]/filters.json

Translations

https://filters.adtidy.org/[platform]/filters_i18n.json

Filters

https://filters.adtidy.org/[platform]/filters/[filterId].txt

For instance:
https://filters.adtidy.org/[platform]/filters/2.txt
https://filters.adtidy.org/[platform]/filters/[filterId]_optimized.txt

_optimized suffix stands for "mobile optimized" filters versions.
We use it by default in case of iOS and Android apps.

[platform] possible values:

• windows - Adguard for Windows
• mac - Adguard for Mac
• android - Adguard for Android
• ios - Adguard for iOS
• extension/chromium - Chromium browser extension
• extension/firefox - Firefox extension
• extension/safari - Safari extension

I suppose we could ignore Checksum: field for now as anyway we use https.

[TPS]

@gorhill, this is likely relevant to uBlock origin, as several builtin filterlists are from AdGuard.

[ameshkov]

Yep, indeed.

@gorhill it would be better if you switch to this server instead of using adguard.com.

Russian filter:
https://filters.adtidy.org/extension/chromium/filters/1.txt

English filter:
https://filters.adtidy.org/extension/chromium/filters/2.txt

Turkish filter:
https://filters.adtidy.org/extension/chromium/filters/13.txt

Filters updates requests create a huge load, so moving filters to a CDN will help us with unloading the website.

[gorhill]

Ok I will change -- but can't just now, because of early design choice years ago -- the key for a list is the URL itself, so there currently no way for me to change the URL without losing a user's selection of the list. Do you plan to redirect the old URLs to the new ones server-side?

[ameshkov]

Do you plan to redirect the old URLs to the new ones server-side?

Oh, didn't think about it until you've mentioned it:)

Yep, we will definitely do it.

[ameshkov]

the key for a list is the URL itself

What are you planning to do with EasyList? They've also changed URLs recently.

[gorhill]

I plan/started to fix this, to no longer use the URL as a key.

[TPS]

[platform] possible values:

…

• extension/firefox - Firefox Safari extension

@ameshkov That can't be correct, right? 😜

@gorhill Based on the above, the current Ff version of uBo would need the extension/firefox URLs, I think, though after gorhill/uBlock#622 (@ameshkov, I think this discussion is relevant to AG Ff, also) becomes required by a stable Ff version, I think then you'd switch over to extension/chromium URLs, though I hope you'd keep up current uBo for those of us on legacy platforms (e.g., Pale Moon). 🙏

[ameshkov]

@ameshkov That can't be correct, right? 😜

Just a typo, thanks for noticing it:)

In fact there's no difference between extension/firefox and extension/chromium, we've divided it just in case:)

[ameshkov]

@ameshkov, I think this discussion is relevant to AG Ff, also

Just recently tested it. I think we'll wait a bit more until WebExtensions API becomes more reliable.

[Revertron]

Done.