Adam Tauber

> It is harder to trust this awesome service if there is no way to contact the maintainer(s). I'm not saying that this feature isn't useful, but the point of...

Providing contact data doesn't mean anything. They can still use logging or do something malicious, whatever they say. Also, providing contact data doesn't imply that you can contact with them,...

@mrchrisadams thanks for the contribution, great feature. Using an sqlite db isn't a viable solution, because most of the searx instances use multiple workers and all of those try to...

> Because we're only doing a very simple SELECT query, and we don't write to the data, I figured this was a fairly valid use case. You are right, great....

@mokulus This sounds like a good plan. > compile the the regexes and save them in settings (might not be the best place), so we don't read the file every...

> Personally, this is what I'm hoping for, a user controllable blocklist. It can be problematic to save big lists, because we don't persist any user settings, we just store...

Great suggestion. We should remove the engine selection query parts from the category buttons, I think, this way we can achieve the mentioned behavior.

Ohi! Thanks for the contribution. It is a useful and highly requested feature, however the implementation has some flaws. First, it doesn't support properly multiple languages currently, second it introduces...

@Pofilo we can release a new version (0.13.2), but as I see these fixes don't solve the problem permanently for everybody.

@haasn please remove `category: general` from settings.yml then I can merge it.