ameshkov

10 ms·

61.
by ameshkov 4y ago
I wouldn’t say that these are exceptions or that they’re meaningless. EU and US antitrusts are just very slow, but we’ve already seen examples how antitrust authorities in other countries change the situation (see South Korea vs Apple, but
62.
by ameshkov 4y ago
At this point I don’t believe that public discussion can change anything. Antitrust can, though, and in my opinion it would be better if the discussion was steered that way.
63.
by ameshkov 4y ago
If my comment makes you think that I support this rule in any way, maybe I should’ve explicitly stated that I do not. What I am saying is that the title is misleading as it tries to represent an old rule as if it is something new.
64.
by ameshkov 4y ago
This is getting posted again and again and I don’t understand why. There are no news here. Ad blockers were never allowed to Play store, here is the relevant policy: https://support.google.com/googleplay/android-develop
65.
by ameshkov 4y ago
AdGuard is not a russian company since long time ago. We moved the HQ in 2014, the core team including the owners are also on Cyprus, and finally half of AdGuard websites are even blocked by russian authorities. Anyways, I guess we’ll never
66.
by ameshkov 4y ago
Actually, AdGuard Home checks for updates periodically (unless it’s docker or snap) and can update itself right from the admin panel.
67.
by ameshkov 4y ago
I only talked with the layer of the defending side. They say that this is a nonsense, but with such a complex matter you can never be absolutely sure.
68.
by ameshkov 4y ago
iOS? Do you have "advanced protection" enabled? Since some time ago standard content blocking rules are not enough and we need a WebExtension to be allowed to run on YT to block ads there. Oh and one more thing: there's an op
69.
by ameshkov 4y ago
This is my article from 2017. Here's a short update on what happened since then: 1. DMCA takedowns did not destroy ad blocking (thank god), but there were a couple more times when it was tried, nothing huge though. 2. Streisand effect
70.
by ameshkov 4y ago
Oh no, that were numbers for a month, not a day
71.
by ameshkov 4y ago
Thank you! I've passed that to EasyList maintainers.
72.
by ameshkov 4y ago
In this particular case this is not the case and they don't retry. They just really want to download updates REALLY often.
73.
by ameshkov 4y ago
You're missing three orders of magnitude.
74.
by ameshkov 4y ago
Author here. Actually, it's getting better, I've just looked up the stats and for the last 30 days we only served 70TB of access denied pages, this is about 33-34B requests.
75.
by ameshkov 4y ago
This question was discussed so many times in W3C group. Mostly this boils down to one thing: there needs to be an alternative to service workers and there are tons of legitimate use cases for long-living background pages or workers. I think
76.
by ameshkov 4y ago
The main issue is that their lifetime is limited and they're getting constantly killed. This happens all the time even when the service worker is being actively used.
77.
by ameshkov 4y ago
DNS-based solutions can't block everything since they're limited to blocking domains. But wait until we bring a content filtering proxy to AdGuard Home, this will be the day when you'll finally get clean pages and you won&#x2
78.
by ameshkov 4y ago
We did our best with Safari, but believe me, it actually works worse than AdGuard in Chrome and Firefox. Safari with all its limitations is no better than Chrome with MV3.
79.
by ameshkov 4y ago
It's worse than it was and the reason for that is not the declarativeNetRequest, but replacing background page with a service worker. You see, now extensions are supposed to do background work in an ephemeral service worker. This servi
80.
by ameshkov 4y ago
As I understand, Edge will also migrate to MV3 completely. Also, I am not entirely sure other Chromium-based browsers will be able to maintain MV2 compatibility in the long run.
81.
by ameshkov 4y ago
> The service workers vs. background script issue discussed by AdGuard will affect many or most extensions. This is so true. It is often overlooked, but the root problem of Manifest V3 is not declarativeNetRequest, but this service worke
82.
by ameshkov 4y ago
No plans were announced so these are purely my speculations but to me it seems logical. The only piece of reliable information is this: I once asked Google engineer whether they plan to support declarative cosmetic rules (that's what w
83.
by ameshkov 4y ago
Let's be fair to Safari devs, you should probably search for all statuses and not just the bugs and feature requests that are still open: https://bugs.webkit.org/buglist.cgi?bug_status=UNCONFIRMED&b...
84.
by ameshkov 4y ago
This sort of boycotting will only work when widely supported by both developers and users and this is not the case. Despite all the public outcry and news outlets telling that the end is near, it didn't affect the Chrome's share.
85.
by ameshkov 4y ago
All true, and we (content blockers devs) were saying this all for years, since MV3 was first announced. MV3 brings very little (if any) privacy and security enhancements, this is for the future MV4 when extensions will be dumbed down to set
86.
by ameshkov 5y ago
Tbh I thought these sanctions are against govt officials and not the general population.
87.
Apple bans accounts of developers from Belarus(developer.apple.com)
191 points by ameshkov 5y ago|86 comments
88.
by ameshkov 5y ago
Same issue with all our addons. What’s even more frustrating is that unlisted addons are also affected, you cannot even sign an addon since it needs to go through a manual review now.
89.
by ameshkov 5y ago
It’d be easier to use Cloudflare WARP command line client for the same purpose. Apple uses Cloudflare for their private relay so there’s a chance that these IPs won’t be blocked.
90.
Quad9 and Sony Music: German Injunction Status(quad9.net)
430 points by ameshkov 5y ago|225 comments

More ›