So right now im kind of doing option 1, but .local (I’ll switch to .internal) and not using * ( which I will change and see if it let’s me use the subdomains I configured in caddy that werent working before)

Option 2 it what I considered switching too, I have adguard running on my router, but was testing option 1 when I decided that I might want to skip ahead to something more advanced. I really dont want to have to install certs on each device to get past the warning for https.

Option 3 is on my backlog, I have a vps I planned on setting up pangolin on later down the road after I got some of my services spun up, but maybe I should take care of that now instead.

Option 4 is something I briefly looked into before realizing its way over my head, and im also pretty risk adverse.

Sumarry: so maybe option 3, and possible option 2 if its still needed when on my local network without having a client running.

Why is it USB 2.0? This would have been a great chance to undo the downgrade when they released the base version.

It scraps results to the extent that Google scraps results from websites. Google doesnt pay me for including my personal blog in someone’s search results, so why would I pay Google for including them in my SearXNG results.

Some countries have gone after Google for search summaries, but SearXNG doesnt do that, and they haven’t gone after the other search engines that are closer to being a household name. So I think its safe, legally.