I’m currently working on re-evaluating our search engine selection (reading privacy policies and all that good stuff), to see what to keep, remove, maybe add. I figured I might use some input from lemmy.

  • what do you use out of the ones we include? is anyone actually using search engines like qwant and metager?
  • do you add any search engine to librewolf?

if you’re curious bout my notes on this -> https://gitlab.com/librewolf-community/settings/-/issues/111

  • BXM1X9UyZ588Yb7Ebgv@lemmy.ml
    1·
    3 years ago

    Maybe(to add): https://searx.neocities.org

    Policies:

    • Redirects users directly to a random selection of any known running server after entering query.
    • Requires Javascript.
    • Excludes servers with user tracking and analytics or are proxied through Cloudflare.

    I found this random Searx/SearXNG search engine redirector at https://searx.space under the About tab.

    To use it, I save the search redirector as a bookmark at https://searx.neocities.org/#q=%s&category_general=on

    I also turn on javascript on at searx.neocities.org because otherwise I have to type in my search query manually into a specific search instance.

    However if your threat model requires it, you can also go to the no-javascript version of searx.neocities.org. You will not be automatically redirected to a random Searx instance when using no-JS version.

    I type in a keyword in the url bar and then the service redirects me to a random Searx/SearXNG instance. For load balancing purposes, it seems great since no single server will be stressed significantly. The searches are spread across multiple instances.

    Sometimes the redirected Searx/SearXNG instances output bad results(e.g. errors). In that case, just use the Searx redirector again to have new random Searx/SearXNG instance.