mbirth 🇬🇧

Collector of social media accounts. Speaks 🇬🇧 and 🇩🇪.

  • 1 Post
  • 188 Comments
Joined 2 years ago
cake
Cake day: June 1st, 2023

help-circle



  • The important bit is -v /opt/podman/searxng/config:/etc/searxng:Z in the podman call. This will mount your local directory (i.e. on the host the container is running on) /opt/podman/searxng/config into the container as /etc/searxng (which is where SearXNG is searching for its config). Make sure that the local directory exists and is writeable by your user account before starting the container. This way your config will persist even when the container gets replaced by an updated version.

    IIRC, after running the container for the first time, SearXNG should put a settings.yml and uwsgi.ini there. You can edit them and restart the container for the changes to take.

    On later container updates, SearXNG will put the latest versions of the default configs as settings.yml.new and uwsgi.ini.new. This way it doesn’t overwrite your config and allows you to manually merge the new defaults into your running config. (If you only see the *.new files after starting the container for the first time, rename them and remove the .new part.)




  • Because

    A) Solving Captchas isn’t protecting from abuse/spam anymore. People in countries with cheap labour costs are being paid (or forced) to solve these for spam networks. And nowadays, LLMs can solve them almost better than any human. Manual approval is completely infeasible once you have a somewhat larger following.

    Tying comments to some form of account is at least somewhat of a hurdle for spammers.

    and

    B) Some people want to keep ownership of their data. As long as the comment is tied to my account, I can easily find, edit or even delete it. Try that with some comment you made on some obscure blog 5 years ago; which address you don’t remember and with an email address you no longer have.