Filter results by adblocking lists

danieljomphe

Your implementation of Lenses for the Family plan got me thinking: what if we crossed this feature with e.g. our NextDNS or adblocking filters, such that Kagi knew how to filter out any search result that wouldn't anyway be allowed by these blocking filters?

Let me put it another way. For the Family Plan, how would that look like?

My kids browse a website that I profoundly dislike...
Realizing that, I filter it out at the network level so that no device can ever browse it anymore...
And Kagi automatically picks that up and stops showing it in search results.

Isn't this superb?

You could either:

Allow us to configure some popular Blocklists as a starting point.
Real payoff: Integrate with NextDNS' API to load our network's Blocklists and Denylist (if there is such an API; or if they're willing to develop it for you!)
Real payoff: Create your own DNS filtering solution, tightly integrating it with Kagi and Orion!?

Having this level of integration would certainly put Kagi and Orion in an uncharted field of very powerful feature possibilities, right? The sync could go both ways. Ban a site from Kagi or Orion and be offered to sync the ban up to the network-level Denylist. 🙂 This would give the most usable filtering solution.

We're still hesitating about the Family Plan. That's a lot of yearly money to shell out... But... with this kind of integration... it would be a no-brainer for us, and I suspect, for many, many families around the world.

Dad, Google shows me all these sites that I can't browse, why is that?

Son, we block them. We want to keep you away from this kind of material.

Ok Dad, but can't you see it's annoying to click on results and end up on blocked sites?

You're right, son! I suggest you try again the Kagi search engine I showed you the other day. It's as good as Google and it will give you the most coherent experience: it won't ever list any result that you can't browse because of what we block in this family.

Oh, let me try it again, Dad!!

Vlad

danieljomphe Interesting chain of thought.

For practical purposes implementing Blocklist support is already on our roadmap (ublackist file format? ) and is on this site somewhere.

Integrating with NextDNS and other APIs is a bit out of reach because there is no standard, and people use all sorts of firewalls out there.

There is also a third problem of discoverability. Where do you put info like this even if we had it? It is a farily technical thing that should probably not be on the pricing page as it would confuse many non technical families.

danieljomphe

Vlad After thinking about it for some time: great responses!

Re: the sync with e.g. NextDNS (and its discoverability), I've come to agree with you, it's impractical for Kagi to focus on this. I still hope some day integrating things like this will become a no-brainer, and I realize it shouldn't be on Kagi's shoulders to lead the way in this particular case.

And, you've already given us the ability to Block domains! I could totally use that to manually "sync" with my NextDNS setup from time to time.

So the only part that might remain of my original request is to have search results automatically filtered out when they match any implemented blocklist. And I suppose only some blocklists make sense in this context, e.g. "I want Kagi to filter out everything matched by the (no-porn or whatever) blocklist". And this might be better covered by another request like this one, so you might want to close my post to clean up this site.