Vasily Bagirov on
AdGuard for Safari proved to be a popular ad blocking solution soon after its initial release. It took us a bit more than a month to update it from v1.1 to v1.2, and almost half a year to reach v1.3. As you know, if we do something for so long, it's probably going to be worth it. This time is not an exception, hopefully: on top of multiple smallish but important changes and fixes, we have two big ones. Let's have a look at them.
About a month ago we posted an article about the first Beta version of AdGuard 3.0 for iOS. Today, it's time to officially release it into the App Store! Why is it such a big deal? Unless you've read the aforementioned article, you probably wouldn't believe how much new stuff there is, so I'll go over the changes one more time here.
Daria Magdik on
Andrey Meshkov on
There's been a lot of talk lately about the changes that await Google Chrome in the near future. In short, Google is going to change Chrome's extension platform. Developers confirmed it multiple times that the old API is going to be deprecated and that the new declarative webRequest API is inevitable. Translating it into human language, it will effectively kill a lot of extensions, and significantly reduce the capabilities of ad blockers.
Not very long ago (this month, in fact) I wrote about a big AdGuard for Windows beta update. As you can guess, todays release is largely based on that beta version. You'll see similar phrases about the same new features, so if you had a chance to read the previous article, feel free to skip those parts. But there's also a bit of fresh stuff, so even regular Blog readers will find something new here. Okay, enough with the prelude, let's get to the action!