Randomly delay sending of request reporter messages #149
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
philipp-classen
added a commit
to ghostery/ghostery-extension
that referenced
this pull request
Dec 17, 2024
philipp-classen
added a commit
to ghostery/ghostery-extension
that referenced
this pull request
Dec 17, 2024
…eduler. It is intended to smooth out the traffic during peaks like the begin of a new day, where all clients generate keysv2/tokensv2 messages. Also, having randomized client-side delays for tp_events introduces the possibility of message reordering, which is intended.
philipp-classen
force-pushed
the
send_antitracking_via_jobscheduler
branch
from
7064f8d to
4d02093
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Provide a function to send anti-tracking messages through the job scheduler.
It is intended to smooth out the traffic during peaks like the begin of a new day, where all clients generate keysv2/tokensv2 messages. Also, having randomized client-side delays for tp_events introduces the possibility of message reordering, which is intended.