• mad_lentil@lemmy.ca
    link
    fedilink
    English
    arrow-up
    17
    ·
    2 days ago

    So Google uses something called “federated learning” which is not as fun as it sounds. It’s where they load a small model onto your device, train it on all your data, then send the resulting training data back to headquarters.

    So it’s totally cool! Because your actual PII never leaves your device! Just everything about you statistically that might be useful to advertisers or governments! Really, whoever can pay!

  • Darkassassin07@lemmy.ca
    link
    fedilink
    English
    arrow-up
    79
    ·
    3 days ago

    When I setup pihole, the google home speakers I had were making dns requests something like 20k times a day. More than pretty much every other device on my network.

    I removed them all after that.

    • zarathustrad@lemmy.world
      link
      fedilink
      English
      arrow-up
      22
      ·
      3 days ago

      Same for Roku, and worse now that they were bought out. Sorry grandma, the Roku is getting cut off. Lol

    • ninja@lemmy.world
      link
      fedilink
      English
      arrow-up
      17
      ·
      3 days ago

      I’m surprised it didn’t just have google’s DNS hardcoded to bypass your pihole.

      • grue@lemmy.world
        link
        fedilink
        English
        arrow-up
        19
        arrow-down
        2
        ·
        edit-2
        3 days ago

        That ought to be illegal.

        (No, seriously: disobeying DNS the owner set by DHCP ought to count as “exceeding authorized access” under the CFAA.)

        • molehill_siesta@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          17
          ·
          3 days ago

          Unfortunately the monkey’s paw would curl here and using DNS other than that provided by your ISP would become illegal.

          (I know there’s a difference between your devices using their network to access the internet and your “purchased” (licensed software running on) your device using your network to access the internet - but the monkey doesn’t care)

          • grue@lemmy.world
            link
            fedilink
            English
            arrow-up
            5
            arrow-down
            1
            ·
            3 days ago

            No, because the law cares about intent, not technical details. Having my property do DNS over HTTPS because that’s what I, the owner, wanted is fine; having my property do DNS over HTTPS because that’s what some non-owner entity wanted against my will as the owner is not.

            • aksdb@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              3 days ago

              Rather: they are free to do protocol negotiation with the DNS server I supply. If it speaks DoH, go for it.

        • shalafi@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 days ago

          Neat! Trying this in a few minutes. Be lovely having everything go through my local Pihole VM.

          • lemming741@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 days ago

            There are several DoH IP lists on github. Find one that is staying updated and use it as an alias to block them all

      • randombullet@programming.dev
        link
        fedilink
        English
        arrow-up
        5
        ·
        3 days ago

        I redirect all out going dns requests to my self hosted DNS server.

        Only one I can’t block is DoH. DoT is easily blocked and my firewall picks up on it.

        • bamboo@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          Could you block DoH entirely on the network level and cause it to fallback? I guess you’d have to have a list of common DoH IP addresses to block.

          • towerful@programming.dev
            link
            fedilink
            English
            arrow-up
            4
            ·
            2 days ago

            You have the destination IP to work with, thats it. Otherwise it just looks like any other HTTPS traffic.

            I guess if you uplpaded your own root CA cert tgen you could man-in-the-middle for deeper packet inspection.
            Or, i guess, try using eMudhra’s compromised private keys and hope the clients havent been updated yet

            • bamboo@lemmy.blahaj.zone
              link
              fedilink
              English
              arrow-up
              2
              ·
              2 days ago

              Right, I guess as more DoH servers become available, it’ll be harder to track, but you could intercept and blackhole any HTTPS traffic to one.one.one.one and other popular servers to have them fallback.

              • towerful@programming.dev
                link
                fedilink
                English
                arrow-up
                1
                ·
                edit-2
                2 days ago

                Yeh, exactly. “You have the ip to work with”

                one.one.one.one isnt an http/ request, its a dns lookup.
                If it was an http/s request to 1.1.1.1 then it could be blocked. Also, super cheap/easy to proxy

    • Wispy2891@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 days ago

      Similar for my Google nest, it’s the #1 host in number of daily requests in my network, around one every 500ms

      Now it’s on it’s own vlan so there’s nothing that they can report on my network, but it’s really concerning that a thermostat calls home this often. It should be enough to do it once an hour to check the outside temperature and only if it’s enabled.v

  • Treczoks@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    3 days ago

    They do this outrageous download numbers just to hide the amount they upload at the same type.

  • m-p{3}@lemmy.ca
    link
    fedilink
    English
    arrow-up
    24
    ·
    3 days ago

    I took mine out when I discovered from the log that it would randomly cause massive deauth and noise on my wireless network. All my stability issues vanished since.

    • BrianTheeBiscuiteer@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      3 days ago

      I unplugged mine when it kept coming to life after hearing “Hey <any other fucking word under the sun>”. If all it did was act as an internet radio and set timers I’d still be using it.