gimmeasearx
gimmeasearx copied to clipboard
demostanis
Improvement suggestions
Hey, I've been using your tool for a few weeks and I have a lot to thank you for. It really is something very useful! I have some suggestions that can help improve the project, especially for those who used searx.neocities.org before.
- Filter by version More than half of the instances available today are in an old version. So the chance that one of them will be used is very high.
- Exclusion list for countries At least for the US 🤣
- List of allowed instances It is currently possible to use an exclusion list, but the instances are very dynamic, so excluding some does not guarantee that if a new instance is not used
- Delete doubtful instances Searx.neocities.org uses the following filter
network: Does not contain "googleusercontent" http headers: Does not contain "CloudFlare" or "googleusercontent"
- TLS and CSP This is as important as the filter that currently exists for HTML and JS
Hey, thanks for your suggestions and sorry for the late reply. I will try to implement them in the following days!
About the allowlist, should it completly replace the blacklist or should there be an option to toggle between them?
Wait did he delete his account?
it seems so
I think each one can be useful for many different users. maybe an option to select between both?
Personally, what bothers me most is using instances with old versions
Added support for filtering by version in master. For the exclusion list by country, I am not sure how this could be implemented in our UI, as it mustn't use JavaScript. Should it list flags with checkboxes for the ones to keep? It would also depend on an API to fetch searx instances' IP addresses information, which may get the public instance rate limited after some time.
Removing of instances using Cloudflare is in master too. I don't think it should be an option, who the fuck wants instances using Cloudflare? Imma go play Red Dead Redemption 2.
List of allowed instances can be done by blacklisting * (everything) and putting wanted instances in Custom instances.
It might be a little harder to filter by country as the UI cannot use JS, and that knowing where the instance is located would require dependence to an API providing this information (how would it be possible otherwise?). I'd need opinion of whomever's reading this.
For TLS and CSP, it is in my list of things to be done. Pull requests are much appreciated.
List of allowed instances can be done by blacklisting
*(everything) and putting wanted instances inCustom instances. It might be a little harder to filter by country as the UI cannot use JS, and that knowing where the instance is located would require dependence to an API providing this information (how would it be possible otherwise?). I'd need opinion of whomever's reading this. For TLS and CSP, it is in my list of things to be done. Pull requests are much appreciated.
if I put * into the blacklist and instances into custom instances and save it, the custom instances are just reset. If manually add the instances into the url they are still ignored
Oops, my bad. You need to blacklist .*, as the blacklist is composed of regexes.