The instances that give the best results seem to also get throttled pretty often on the source search engines, to the point of near uselessness.

Thinking of hosting my own, but the maintenance seems pretty involved according to the docs.

What’s your experience been like?

  • root@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    ·
    9 hours ago

    Self hosting and the maintenance is painless, but the results have been pretty terrible lately

      • root@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        Lol, thanks. I think it’s still worth it if you want more ownership over your searches, but just expect some rough edges

      • root@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 hours ago

        Recently I’ll often get results that aren’t at all related to what I searched for. I also get a lot of timeouts from the upstream search engines, and sometimes I get results that are in Chinese for some reason

        • Engywook@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          23 minutes ago

          IIRC these are related to Bing misbehaving. There should be an ooen issue about that. Try deactivating it in preferences flash a workaround.

        • fizzle@quokk.au
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 hour ago

          There’s an open issue about this on github. It’s the remote API is only recognising the first word of your query.

          This has been bugging me too.

          The timeouts are because the engines are presenting captchas. There’s a work around whereby you use your instance as a proxy, navigate to that remote engine, and do the captcha.

          These two issues are a real pain in the ass so while I do presently have a searxng instance I’ve been using qwant the last few weeks because I’m just over it.