Replies: 5 comments 12 replies
-
|
Not possible in Chromium, maybe looked at Firefox if possible this way. |
Beta Was this translation helpful? Give feedback.
-
|
@gorhill @gwarser Since I'm not familiar with DNS stuff, I told OP to move the discussion to github. |
Beta Was this translation helpful? Give feedback.
-
|
uBO will need to have own domain and use subdomains for this, like |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible with cloudflare pages? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
Yes, it would require some new infrastructure:
|
Beta Was this translation helpful? Give feedback.
-
|
I doubt @gorhill agrees. Once you get domain, you owe responsibility of it. Whenever we abandon the domain, anyone can abuse that. Being free from such responsibility has been central to this project. |
Beta Was this translation helpful? Give feedback.
-
I understand. By only referencing the domain in the filter list you could easily revoke or change the use of this domain with a simple update of the filter list. Or even only implement such a feature and let somebody else have the responsibility of providing such a domain (it doesn't need to be done by the uBO team, just like there are filter lists from other teams). |
Beta Was this translation helpful? Give feedback.
-
|
Normally I'd suggest giving a tip about it to https://github.com/AdguardTeam/AdGuardHome/issues, but development on that tool has borderline collapsed since around February, with issue reports being left to linger there for years. However, distributing list updates by DNS sound like nonsense to me. I at least don't think DNS works that way. I also fully expect there to be some sort of max limit to how long a TXT-type query ping result can be; very likely not long enough to handle potentially 4-digit amounts of entries at a time. uBO supporting hours for update intervals was new to me (They only supported 1 day or longer for around 10 years), so since they're trying out new things anyway to the best of my current knowledge (which may not be perfect), why not set the interval for Quick Fixes down from 12 to 6 hours during the YouTube war thingie? |
Beta Was this translation helpful? Give feedback.
-
Hmmm... 2 yt filters already cost ~240 characters www.youtube.com##+js(trusted-replace-fetch-response,/"adPlacements.*?AD_PLACEMENT_KIND_START.*?"\}\}\}\]\,/, ,url:player?key=)
www.youtube.com##+js(trusted-replace-fetch-response, /"adSlots.*?SLOT_TYPE_PLAYER_BYTES.*?\}\]\}\}\]\,/, , url:player?key=) |
Beta Was this translation helpful? Give feedback.
-
Does not matter when CDNs update content on the servers every two days. |
Beta Was this translation helpful? Give feedback.
-
|
@gwarser I think cloudflare is quite fast? It contains today's fix already: https://ublockorigin.pages.dev/filters/quick-fixes.txt |
Beta Was this translation helpful? Give feedback.
-
|
Maybe the TXT record could contain the last modified time if the quick fixes list |
Beta Was this translation helpful? Give feedback.
-
That would be two TXT string values though (with each having a 255 character limit). It would only become a bit difficult if a single filter entry would be longer than 255 entries, then the usual way is to split it into two values.
That could make the load on the CDN worse because now you would have all uBO clients updating the filter list at the same time. It only really helps if you get rid of the frequent HTTP refreshes. |
Beta Was this translation helpful? Give feedback.
-
|
Is a peer-to-peer solution for acquiring the ublock filterfiles compliant with Chrome's guidelines? Given the high number of uBlock installations, sharing the filter list among clients could be achieved effortlessly. I mean, there are bittorrent/webtorrent extensions. No need for a domain or a centralized solution with peer-2-peer. Just an idea. |
Beta Was this translation helpful? Give feedback.
-
The problem: You have a large website that updates it's anti-adblock measures multiple times a day. You want to quickly distribute changes to the filter list to your users, but the 12 hours expiry of the "quick fixes" list is not low enough. But you can't lower the expiry of the list because that would overload the CDN.
The idea: Maybe it's possible to use DNS to distribute quick changes to filter lists and get free caching from DNS resolvers.
There is now a widespread, global infrastructure of DNS-over-HTTPS resolvers. Some (for example Cloudflare) can even provide JSON reponses for easy querying from within JavaScript. DNS TXT records allow the distribution of arbitrary text and DNS resolvers cache the record for the duration of the TTL.
A filter list could have a special syntax which defines DNS records that contain additional filters, something like:
Now each time I visit
thatsite.comuBlock Origin would fetch the TXT records fromthatsite.ublockdns.example.com(using a DNS-over-HTTPS server configured by the user) and use the filters from the TXT records as well. The DNS records would have a reasonably low TTL and each DNS resolver would cache the records for that duration (with the cache being shared among all of the resolver's users), resulting in a much lower load on the upstream servers.Since DNS records can't be very large they would only contain the most recent changes until every user will have them from the main filter list anyway. So if the "quick fixes" list has an expiration of 12 hours hours a filter can be rotated out of the DNS records after 12 hours.
Beta Was this translation helpful? Give feedback.
All reactions