Ad blocking doesn't exist just because a bunch of developers randomly chose to work in this field. It has become a thing and continues to grow solely due to public interest and involvement of a huge number of people. Today, there is an entire community that's united by the desire to make the Internet a cleaner and safer place for everyone.
Recently, AdGuard Pro for iOS received a very small update. Basically, we just updated localizations and one or two random bug fixes. It looks very unassuming at first glance, but it means a whole lot. Why? To explain that, we need to go back in time and look at AdGuard Pro's bumpy road to where it is today.
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.
We talk a lot about the importance of privacy, and it is often tightly linked to data security. One of the cornerstones of data safety is two-factor authentication. Most of you are probably familiar with this concept, as it has become pretty much a security standard by now, but I'll throw in a refresher.
Everybody who has any interest in Android OS is currently talking about Android Q beta that has been released just recently. The developers' blog post provides a lot of food for thought, but it doesn't answer the most important question: how does Android Q affect AdGuard? :) Read on to find out.