Safe Browsing is a Google API that’s free to use for non-commercial purposes, and allows client applications to look up websites in a database to see whether they pose a known risk.
The Enhanced version has offered more extensive protection using real-time URL lookups and machine learning, though it sends information to Google – which the tech titan claims “is only used for security purposes.”
What’s more, the Googlers observe, the size of the local list and the need to maintain connectivity for updates can present a challenge for devices that are resource constrained or have intermittent network access.
So in Chrome for desktop and iOS, and Android later this month, the Standard tier of Safe Browsing is getting privacy-preserving, real-time protection.
This requires some technical enhancement like the implementation of an asynchronous mechanism to prevent network calls from blocking page loads and degrading the user experience.
The system works by first looking in a local cache file to see if the website URL to be visited is known to be safe.
The original article contains 564 words, the summary contains 172 words. Saved 70%. I’m a bot and I’m open source!
This is the best summary I could come up with:
Safe Browsing is a Google API that’s free to use for non-commercial purposes, and allows client applications to look up websites in a database to see whether they pose a known risk.
The Enhanced version has offered more extensive protection using real-time URL lookups and machine learning, though it sends information to Google – which the tech titan claims “is only used for security purposes.”
What’s more, the Googlers observe, the size of the local list and the need to maintain connectivity for updates can present a challenge for devices that are resource constrained or have intermittent network access.
So in Chrome for desktop and iOS, and Android later this month, the Standard tier of Safe Browsing is getting privacy-preserving, real-time protection.
This requires some technical enhancement like the implementation of an asynchronous mechanism to prevent network calls from blocking page loads and degrading the user experience.
The system works by first looking in a local cache file to see if the website URL to be visited is known to be safe.
The original article contains 564 words, the summary contains 172 words. Saved 70%. I’m a bot and I’m open source!