summaryrefslogtreecommitdiff
path: root/searx/settings_defaults.py
diff options
context:
space:
mode:
authorMarkus Heiser <markus.heiser@darmarIT.de>2026-02-22 14:44:21 +0100
committerGitHub <noreply@github.com>2026-02-22 14:44:21 +0100
commit191818b865b19270c8c38d905141356a6ba01d9a (patch)
treeb42ba81cc63263258688a124459dd08ecfa84e99 /searx/settings_defaults.py
parent5054e69844cbedfa0f5184955d662d944bcd35c1 (diff)
[mod] drop SearXNG's checker (#5767)
To date, there is no analysis for the checker that could be evaluated in any meaningful way. - https://github.com/searxng/searxng/issues/3407 - https://github.com/searxng/searxng/pull/3312 The checker would need to be completely redesigned, but even then, its usefulness and the maintenance required for it would be disproportionate. TBH: In its current form, it is useless and only consumes resources and causes the engines to be blocked, because these tests (query terms) come from *hundreds* of instances and could be interpreted as bot attacks. Related issues: [search.checker](https://github.com/searxng/searxng/issues?q=label%3A%22search.checker%22) Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to 'searx/settings_defaults.py')
-rw-r--r--searx/settings_defaults.py4
1 files changed, 0 insertions, 4 deletions
diff --git a/searx/settings_defaults.py b/searx/settings_defaults.py
index 5c17b248e..2b82dce14 100644
--- a/searx/settings_defaults.py
+++ b/searx/settings_defaults.py
@@ -267,10 +267,6 @@ SCHEMA: dict[str, t.Any] = {
'networks': {},
},
'plugins': SettingsValue(dict, {}),
- 'checker': {
- 'off_when_debug': SettingsValue(bool, True, None),
- 'scheduling': SettingsValue((None, dict), None, None),
- },
'categories_as_tabs': SettingsValue(dict, CATEGORIES_AS_TABS),
'engines': SettingsValue(list, []),
'doi_resolvers': {},