Shield function is not working on kagi.com.

BattleHawk

In Orion 0.99.134.1rc and Orion 1.3.26(5), the shield function is not working on kagi.com.

In Orion 0.99.134.1rc and Orion 1.3.26(5), the shield function work on kagi.com.

Thibaultmol

have you tried opening an incognito window with Orion (or whatever it's called on there) to see what happens if you don't have any extensions possibly interfering.

do you have any custom css setup? maybe disable it temporarily to check (it's in the control panel on the right top of kagi.com)

BattleHawk

Thanks to suggest Thibaultmol.

But, Understood!
I've apparently exceeded my ban limit on rubbish sites.
Should I upgrade to the ultimate plan?

It's troubling because we're not using AI at all, though.

Thibaultmol

Upgrading to Ultimate won't increase the amount of domains.

https://kagifeedback.org/d/2140-raise-the-maximum-number-of-ranked-domains

These 1000 websites, are they because of bad content or ai slop? if they're ai slop, feel free to list them on here and they will normally be used to kagi's builtin ranking down the line
https://kagifeedback.org/d/7555-report-ai-slop-phising-malicious-domains-here/

BattleHawk

Thibaultmol

bad content sites.

I've been using uBlacklist (a Firefox extension) to filter out ad-revenue-driven, low-quality content sites from my search results. However, due to its unstable performance, I now intend to achieve this goal using Kagi.com's rating system.

Frankly, I wish you'd just let us import our own custom filters.
https://github.com/Chamiu/Search-Block-Parasiticide

RoxyRoxyRoxy

BattleHawk If you're interested in filter importing, would you mind making a separate post on the subject? I'm going to close this one as nofix as we don't have plans to expand the 1000 site limit due to technical constraints.

BattleHawk

I suspect that the technical issues stem from server-side load.
Therefore, what if we decoupled this functionality and implemented it as a browser extension?

As it operates within the browser, it would impose no additional overhead on the server side.
Since it would function specifically for kagi.com, we could optimise it according to kagi.com's specifications, potentially serving as an incentive to join the platform.
Users could opt-in to provide evaluations of content quality, which could then be reflected in the search results.

I use kagi Translate at This post from Japanese to English.

RoxyRoxyRoxy

BattleHawk It's honestly been a while since I've touched any issues around this; I can't quite remember where the limitation lies. Let me reach out to the devs and see if that's viable.

正直、この件に触れてからしばらく経っていて、どこに制約があったのかはっきり思い出せません。開発チームに連絡して、実現可能か確認してみます。
ちなみに、今回はKagi Translateも使いました 🙂

BattleHawk

RoxyRoxyRoxy 実に自然な日本語です♪
意図的に日本語のままです。

z64

We'll increase the limit to 10k in our next update.

I will add that we make open source contributions to the ublacklist extension for native Kagi support, so that you can have as many rules as you like client-side. We figured this would be best instead of effectively duplicating the extension with our own.

BattleHawk

z64
Achoo... (My cedar pollen allergy has made its debut

Yeah, I know.
https://kagifeedback.org/d/262-add-ublacklist-support-advanced-blocking-rules-regex-matching

I just can't forget that the developer explicitly stated in ver. 9.0 that they "won't support kagi.com because it's a paid service."

Services that appear to be free collect user privacy and make money by selling it to advertising companies and the like.
In contrast, I believe that since kagi.com provides its service for a fee, it won't sell any user privacy it might collect.
That's why I specifically started asking for kagi.com to offer this as their own service.

This post was translated from Japanese to English using Kagi Translate.