This is AFTER debloating all the MS bs as much as I can.

The amount of MS telemetry is just mindboggling.

  • Ciryamo@feddit.de
    link
    fedilink
    English
    arrow-up
    297
    arrow-down
    2
    ·
    1 year ago

    While telemetry is bad the problem here is probably that this windows service pings the server but doesn’t get a response because it got stuck in your pihole. So it tries to pings again and again and again and again…

      • cheery_coffee@lemmy.ca
        link
        fedilink
        English
        arrow-up
        24
        ·
        1 year ago

        Is that user unfriendly? In the desired path where the resource isn’t blocked the options are display an error or try again.

        When a request goes to PiHole it just gets redirected to a bad address, so the application hasn’t got any idea why it isn’t working. In most cases a programmer just adds a retry with exponential back off and goes on with their work, because there’s no real cost to doing that for analytics or advertising code.

    • Knocturnal@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      1
      ·
      1 year ago

      The best solution would be to disable telemetry to the capacity you are capable or is possible without breaking something and block pings as backup to when it’s enabled again with updates and repeat.

      • Stumblinbear@pawb.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Sure but if they’re trying to send new requests while the others are still retrying, then it will result in the same thing