The difference between the two security features is that Safe Browsing will compare a visited site to a locally stored list of domains, compared to Enhanced Safe Browser, which will check if a site is malicious in real-time against Google’s cloud services.

While it may seem like Enhanced Safe Browsing is the better way to go, there is a slight trade-off in privacy, as Chrome and Gmail will share URLs with Google to check if they are malicious and temporarily associate this information with your signed-in Google account.

    • Thanks for the suggestion!

      I had a look, and must admit it sets my spidey sense in something of a tingle 🤔

      Their website says “© 2019 - 2021”, and the blog has a single post from 2019. Similarly, the knowledge base has one single post.

      Similarly, their GitHub doesn’t seem to have had any changes in the /src project, although this might be because they’ve moved development to /src.next.

      Actually, looking at /src.next, there does seem to be a lot of activity, with issues being closed regularly. Maybe it’s just the classic case of devs focusing on dev work and not outward communication or site maintenance.

      I’ll give it a go at some point and see how it feels 👍