- Edited
This is a great idea. There are a few problems with using Google Safe Browsing for execution.
Google Safe Browsing is owned by Google, so Google gets to define what 'safe browsing' means.
Google Safe Browsing is not a high quality source.
For example https://51.fi is a known phishing site (referenced in https://phishing.army/download/phishing_army_blocklist_extended.txt) and does not trigger a warning in Chrome.
- If we were to use GSB that would have impact on performance (as you have to query the API, through a proxy presumably).
How would user end up there anyway? Most likely through a search engine. Which is why we implement all reputable scam/phishing lists into Kagi Search already.
For example:
In the future we will implement the measure into Orion, and it will be using crowd-sourced data, like we do in Kagi Search.