-
Notifications
You must be signed in to change notification settings - Fork 2.3k
[feat] engine: implementation of yandex (web, images) #3733
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
Conversation
It's set to inactive in settings.yml because of CAPTCHA. You need to remove that from the settings.yml to get in use. Closes: searxng#961
return42
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for devoting yourself to the topic again. Even if we can't prevent the CAPTCHA yet, I think it's OK if we add the engines as "inactive". Maybe someone will see this code and find a solution to avoid the CAPTCHA.
I squashed your two commits into one and fixed a nit / diff
|
Any updates in 2025? And Why is it taking so longer than 4 months to add Yandex into The open-source search engine? |
It is in .. but
Maintainers can activate the engine in their settings. @ikkqqstudio Once you show us how to avoid the CAPTCHA, we can enable Yandex by default ... We are just waiting for your cooperation ;-) |
|
There is a Yandex search API, but it requires Paid Cloud subscription |
What does this PR do?
adds yandex engine for web and image results.
Why is this change important?
it's about time we have yandex in searxng again.
How to test this PR locally?
it's set to inactive in settings.yml because of captcha. you need to remove that from the settings.yml.
then you can use: make run
Author's checklist
my old draft: #3201
engine request: #961
Related issues
Closes #961