{"id":447,"date":"2022-06-01T09:59:46","date_gmt":"2022-06-01T16:59:46","guid":{"rendered":"https:\/\/jasonsblog.access.ly\/?p=447"},"modified":"2022-11-07T14:15:30","modified_gmt":"2022-11-07T21:15:30","slug":"install-search-engine-proxy-searxng","status":"publish","type":"post","link":"https:\/\/jasonsblog.ddns.net\/index.php\/2022\/06\/01\/install-search-engine-proxy-searxng\/","title":{"rendered":"Install Search Engine Proxy SearXNG"},"content":{"rendered":"\n

In my last post on installing Whoogle<\/a>, I went over why you would want to take control of your privacy from other search engine privacy proxies. Now Whoogle was a proxy for just Google, but enter in the SearX<\/a> project and the forked project SearXNG<\/a>. From their site:<\/p>\n\n\n\n

SearXNG protects the privacy of its users in multiple ways regardless of the type\nof the instance (private, public). Removal of private data from search requests\ncomes in three forms:<\/p>

    \n

  1. removal of private data from requests going to search services<\/p><\/li>\n

  2. not forwarding anything from a third party services through search services\n(e.g. advertisement)<\/p><\/li>\n

  3. removal of private data from requests going to the result pages<\/p><\/li>\n<\/ol>\n<\/div><\/blockquote>

    Removing private data means not sending cookies to external search engines and\ngenerating a random browser profile for every request. Thus, it does not matter\nif a public or private instance handles the request, because it is anonymized in\nboth cases. IP addresses will be the IP of the instance. But SearXNG can be\nconfigured to use proxy or Tor. Result proxy<\/a> is supported, too.<\/p>

    SearXNG does not serve ads or tracking content unlike most search services. So\nprivate data is not forwarded to third parties who might monetize it. Besides\nprotecting users from search services, both referring page and search query are\nhidden from visited result pages.<\/p><\/blockquote>\n\n\n\n

    To install SearXNG with docker:<\/p>\n\n\n\n

    docker run -d --name searxng -p 8080:8080 searxng\/searxng<\/code><\/pre>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Now you can access SearXNG from ip:8080.<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    From here if you’re in Firefox, you can right click on the address bar and add the search engine. And you can go into settings and make it your default if you wish. If you’re on another browser or Firefox mobile you’ll need to manually set it up with the following:<\/p>\n\n\n\n
    http://ip:8080\/search?q=%s<\/code><\/pre>\n\n\n\n
    If you click the top right configuration gear, you can go into the engine page and enable\/disable search engines as desired. I was getting errors with wikidata, possibly an API issue, so I disabled that one pending further review (not that I use it).<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    And then you’re ready to use your own private search engine privacy proxy only giving the search engines the IP and search terms. They also have Tor available if you need extra privacy as well as support of result proxy<\/a>.<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Unfortunately, there is no really usable opensource distributed search system ready for use. I have played with Yacy<\/a>, but it wasn’t capable of replacing the established search engines quite yet. But at least with these search engine privacy proxies you can limit their ability to track and spy on you while eliminating the need to trust other third parties. <\/p>\n","protected":false},"excerpt":{"rendered":"
    In my last post on installing Whoogle, I went over why you would want to take control of your privacy from other search engine privacy proxies. Now Whoogle was a proxy for just Google, but enter in the SearX project and the forked project SearXNG. From their site: SearXNG protects the privacy of its users […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-447","post","type-post","status-publish","format-standard","hentry","category-tech"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":6}},"featured_image_src":null,"author_info":{"display_name":"Jason","author_link":"https:\/\/jasonsblog.ddns.net\/index.php\/author\/jturning\/"},"_links":{"self":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/447","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/comments?post=447"}],"version-history":[{"count":6,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/447\/revisions"}],"predecessor-version":[{"id":2109,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/447\/revisions\/2109"}],"wp:attachment":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/media?parent=447"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/categories?post=447"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/tags?post=447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}