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

Rework ranking of SearXNG instances. #99

Open
mrpaulblack opened this issue Feb 20, 2022 · 2 comments
Open

Rework ranking of SearXNG instances. #99

mrpaulblack opened this issue Feb 20, 2022 · 2 comments

Comments

@mrpaulblack
Copy link
Member

Currently we rank instances by TLS grade from cryptcheck, CSP grade from mozilla observatory and then the response time for a query measured by searx.space.

This does not guarantee that the best possible instance is at the top and we should think about reworking the ranking system. Since SearXNG is a fork we can completely redo this list and do for example a list with instances and not rank them at all. Also we can require more things for an instance to do, for example to not use analytics and have a constant uptime or to somehow filter instances by the quality of results.

This is just an idea, comments are welcome...

@return42
Copy link
Member

return42 commented Mar 3, 2022

IMO it is better not rank the instances / sort engines by their location makes more sense.

The ranking has absolutely no meaning in practice, by example: a bad TLS grade (from cryptocheck, what is questionable strict) weights more than a manipulated SearXNG engine with analytics or (and this is funny) a SearXNG running on Cloudflare ..

We have users who do not know what TLS or cloudflare is, they just want to have an up-to-date running instance in their neighborhood .. with the ranking we have, we give a wrong illusion of privacy to our users.

@return42
Copy link
Member

I want to rebreathe this issue .. are there any opinions on this ... should we rework the ranking or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Triage
Development

No branches or pull requests

2 participants