-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup P3A clent code / get rid of PROCHLO ? #14408
Comments
looking forward for resurrecting PROCHLO, reopen if PROCHLO is not in production in 2022 :) |
My understanding is that this is just changing internal code paths for P3A message generation, so observable behaviour should be the same, or at least similar. Helpful QA might be:
|
Labelling |
Unblocking and setting |
Performed a spot check on the client-side and ensured things are working as expected and nothing is regressed. |
Initially, the P3A system was designed to utilise PROCHLO for additional privacy, however PROCHLO backend seems abandoned and P3A flies as is. We should consider removing PROCHLO bits from the client side to drop unused legacy and craft better pings (e.g. drop ascii string -> protobuf -> base64 conversion).
The text was updated successfully, but these errors were encountered: