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.
Comment on POV) You use Windows 11 and set up Pihole for the first time.
Ciryamo@feddit.de 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…
Knocturnal@lemmy.world 1 year ago
lambda@programming.dev 1 year ago
Yeah, that’s what I was thinking…
dingleberry@discuss.tchncs.de 1 year ago
Exponential backoff is baked in most libraries. So probably not.
Stumblinbear@pawb.social 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
MonkderZweite@feddit.ch 1 year ago
Is there a service whit which you can automatially send fake answers to certain events?
possiblylinux127@lemmy.zip 1 year ago
Teams no linger does that. It just goes to an error page if it fails to load twice
BaardFigur@lemmy.world 1 year ago
Same thing with ublock. It’s an annoying user-unfriendly practice. Google does the same thing
cheery_coffee@lemmy.ca 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.
SorteKanin@feddit.dk 1 year ago
Retry with exponential back off would not produce a large number of requests.