Markus Heiser

🤔 We could do that too ... but I wonder if it makes sense to give the user this option at all ... in case of doubt, the user will...

> I've found that it can cause issues with the CSP on a lot of the public instances. Sure? .. do you have an example for me? .. could it...

`content_safety` .. why not using the existing `safesearch` safesearch = [filter|save|unsave]

ATM the meaning of `safesearch` attribute is; - `True` : engine (aka module) supports a SafeSearch filter - `False`: engine (aka module) does not support a SafeSearch filter In the...

> I like `content_safety: safe | unsafe | configurable`. Is OK for me, just thought `safesearch = [filter|save|unsave]` is simpler ;) If we add new _SafeSearch_ options, we should document...

> `content_safety` replace `safesearch` IMO. Then I do not understand whats wrong with the name `safesearch` .. as you said: renaming the attribute will cause a bigger patch. > When...

> That allow forks to upgrade without break. When a fork merges patches from SearXNG, the fork has to solve conflict .. Forks with additions and modification are not in...

Disable in the properties or if you host a SearXNG instance, disable it in your `/etc/searxng/settings.yml`

> > how many /search requests the searxng instance has received from users and how many of these were successful/failed and their HTTP error codes? > > That should both...

> /stats is public anyways, so people can scrape the stats no matter if you disable or enable Open Metrics? Yeah, but I had the request from https://github.com/searxng/searxng/pull/3835#issuecomment-2363810790 in mind...