@ak42
If your fear is about fake reporting, allowing for local filtering should be the way to go, and should not be too complicated to implement.
The problem is that, with very few exceptions, any filtering done by Kagi is after we receive the 10-50 results that we aggregate from upstream indexes. We are severly limited in what we can tell those indexes what to omit before we make the search on your behalf.
This means that, if we just allow people to post massive lists of regex block list rules, the majority of time you are just going to be effectively DDoSing us, checking tons of rules that will likely never hit - and we run on extremely cheap hardware as it is.
That is why our approach is a limited number of very simple rules that we can somewhat optimize around, instead of completely arbitrary regex - and for common things like known malware lists etc., we can pull those sources in and implement them in a way we don't have to worry about this so much. We do allow this for URL rewrites, but again, there is a cap to how many can be used at once, and we don't have to worry about everyone just sharing and pasting massive lists into their settings that are basically doing nothing most of the time.
To that extent, client-side filtering plugins that already exist are better off - the advantage of doing it in Kagi is primarily that you don't need any extensions / its syncronized across devices, and in a few cases it helps us infer how we can make the search in advance. Also our rules implementations work without JS, since we do it server-side. But otherwise, its very similar to if you just did it on your client.
Or, if we identify patterns in upstream sources that are consistently giving us these bad results, we can try to work with them, or simply stop using them if it is that rampant.
So that brings us around to having to manage reporting. Building a workflow for that that doesn't take human resources on our end to verify or allow for malicious biasing is not as simple as writing some code.
It would be a different story if Kagi completely owned our full, general search index stack, but unfortunately we don't.
