Not sure, how long Google is at it, it may just be new to me, but today the wife googled for something, and she couldn’t get there as the response was “can not connect”. “Fix the internet NOW!”, was my order.
Analysing the link on Google’s page, it displayed the link as https://www.example.com/, but it actually goes to https://googleadservices.com/?blabla, which is blocked by our DNS, therefore the error.
Displaying one link, but going to another is misleading, lying, tactics of phishers and scammers, IMO.
Is this new, or is it just me, who never clicks on the first result of a Google search?
Actually it’s not that hard and it’s even probably possible to even host SearXNG on the same hardware, or kind of hardware, that you’ve hosted your Pi-Hole or DNS server on.
I actually self-host my own SearXNG and Invidious instances and customize the settings on both, and it’s super useful. (Example: My SearXNG instance is aware of my Invidious instance on my network and will use it to load videos when Invidious is queried via the !iv bang. By doing this I’m not relying on public invidious instances so much; which oftentimes experience downtimes…because youtube hates those more, and frequently bans the public instances.)
This is all doable with a little bit of Docker or Podman action and a bit of editing the appropriate YAML files prior to composing the containers.
So you might be able to spin up a SearXNG instance locally on your network for her to use and configure it to use Google and any other search engines she might prefer. Then use something like LibRedirect (Firefox and Chrome plugin) to redirect her to the local SearXNG instance. (instead of using Google)
A video about setting up SearXNG: https://www.youtube.com/watch?v=UBLypfM9U-g
I wish I could use invidious without problems. I host my own locally and set it to restart the docker every hour like they mentioned in their guide, what makes me say “fuck it” is the fact that some videos play normally, then they stop for whatever reason (docker restarts OR NOT) and from then it loads the video, refreshes a few times and then the video is unplayable because of some “error decoding the video” or whatever it says (image below) and restarting docker or reloading the page does nothing and that video becomes unplayable
That’s the part why I stay away from Invidious. Why would you need to restart every hour? How inconvenient :/.
Piped has other issues right now but fixes are underway :)
Invidious is a great project and the restart is not a biggie unless you’re watching something. Can you host your own piped instance?
Yeah :) piped self-hosting !
However, we have to wait until they merge the poToken and visitor data issue. Something invidious has already implemented.
Still it’s very strange you have to restart your container every hour :/ I’m sure I’m to stupid to understand the backend/code to make any sense out of it, but piped instances never had to restart anything.
Cool!
Ooh yeah, I know about that and NewPipe has this issue but I don’t understand if is app only or web browser too but I’ll see when I try it
It is, no idea why
Yeah, I have my own SearXNG too, albeit hosted on a VPS. However, the difficulty I was talking about was in convincing other people to switch.