I want to use SearxNG as my daily driver, and I added three instances to my browser’s search engines list. However, I find that all three are down whenever I try to use it, and I inevitably have to look at the list of instances and click the top one just to perform one search. Is there a way to “auto-route” my search through the most reliable instance or something?

      • cyborg@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        I self-host my own SearXNG instance and haven’t had any errors like that in the ~6 months it’s been running. It’s just anecdotal evidence, but I would imagine any such low-traffic instance would be able to avoid the blocking and other issues that high-traffic instances run into.

        • eric@lemmy.ca
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          1 year ago

          I’ve never thought of it like that. Another service for the homelab to run.

      • Awwab@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I still have some issues with Bing from time to time but as far as I can tell that’s because they are changing stuff and the SearXNG devs just need to push a fix.

  • cyborg@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Mobile or desktop? Libredirect on desktop allows you to enable a ton of pre-populated Searx instances in the Search category, so it will use any of the enabled instances in your list.

    I don’t believe it picks based on reliability but it at least saves you the time of manually picking/editing your instances. If one is troublesome, just remove it from the list.

  • eight_byte@feddit.de
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Problem is that this kind of alternative web interfaces for Google are just going web scraping of the regular www.google.com page. They are not using the Google Search API (which is paid and requires an API key). However, Google says scraping of their search results is not allowed. And they are actually preventing it by blocking IPs doing too many search request in certain amount of time. That is the main reason a lot of Searx or SearxNG instances stop working after a certain time.

  • 1000knives@beehaw.org
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    i feel this too, i tried using searx for a while and found it really nice but frequently down or broken :/ i’ll try some of the instances suggested here.

  • pinkfloyd@lemm.ee
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I’m pretty sure the instance I use (searx.org) still works (at least for me it does) but it does result in empty search result pages most of the time due to this bug (I think)