Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed wording of advanced blocking with wildcards #635

Merged
merged 2 commits into from
Dec 23, 2024

Conversation

thibaultmol
Copy link
Contributor

Noticed both me and DubbaThony on the discord ran into the problem that we misread this part of the docs. So figured it might be worth rewriting it.

Thx @DubbaThony on discord for helping with determining which rewrite was best

@thibaultmol
Copy link
Contributor Author

I don't think there are kagifeedback links in the docs. but is it something we start doing?
So in this case we could add is a url over the text that says kagi can't do it atm

@z64
Copy link
Member

z64 commented Dec 23, 2024

Linking to the feedback forum is generally fine. But in this instance I don't see it happening anytime soon, or ever - fundmentally it doesn't make any sense with how Kagi works. The only thing that made sense would of been literally reimplementing what uBlacklist etc. does on the client, we decided to just add support for them instead.

@z64 z64 merged commit 4b47755 into kagisearch:main Dec 23, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants