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?

  • N0x0n@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    9 hours ago

    I host my own locally and set it to restart the docker every hour like they mentioned in their guide.

    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 :)

    • Cris16228@lemmy.today
      link
      fedilink
      arrow-up
      1
      ·
      5 hours ago

      Invidious is a great project and the restart is not a biggie unless you’re watching something. Can you host your own piped instance?

      • N0x0n@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        3 hours ago

        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.

        • Cris16228@lemmy.today
          link
          fedilink
          arrow-up
          1
          ·
          17 minutes ago

          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

          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.

          Because of various issues, Invidious must be restarted often, at least once a day, ideally every hour.

          It is, no idea why