Seek privacy-protecting solutions

[samuelweiler]

I would like to see the IG exploring - and pushing for - solutions that minimize fingerprinting surface or make the fingerprinting more detectable, where possible.

Examples include:

• using Client Hints rather than JS APIs to make information exposure detectable. (which might be used for "exposure of specialized services")
• Reporting "aggregated web metrics" (the fourth bullet under scope) using a telemetry scheme such as Prio

Specifically I propose expanding the "Identify opportunities" task to include the above text (or some reasonable variant), or perhaps add a new bullet item under tasks. In any case, the IG should have the task to seek privacy-protecting solutions.

"Exposure of aggregated web metrics" could be quite problematic - using a person's browser for "troubleshooting and monitoring" of a web application is arguably is a misappropriation of the person's resources. As I said when reviewing the Web Performance WG charter, such functions should not be enabled by default - they should be exclusively for use in test farms or when enabled for a specific debugging session. Accordingly, I would prefer to see this item either limited to "things that can be reported through a privacy-preserving system such as Prio" or removed from the IG's scope. If it is left in as-is, it needs to be with the understanding that there will be pushback on standardizing such functionality. @pes10k in case he has further comment.

[sudeepdi]

Thanks @samuelweiler for the inputs. Very pertinent information to include in the draft. Just to add, some of this was discussed a bit at TPAC 2019, where we put together some guiding principles for the IG as we explore new solutions. Adding a link to that here for reference https://www.w3.org/2019/07/31-web-networks-PrinciplesForWebNetworks.pdf

[dontcallmedom]

#35 highlights the need for taking privacy into account when looking at network metrics - @samuelweiler does it address your concern?

[dontcallmedom]

haven't heard back anything, closing

[samuelweiler]

#35 highlights the need for taking privacy into account when looking at network metrics - @samuelweiler does it address your concern?

Partially, maybe? As above "the IG should have the task to seek privacy-protecting solutions", and I'd like to see that be more explicit in the charter.

[dontcallmedom]

@samuelweiler the charter has been under AC review for the past 4 weeks now, so I don't think we're in a position to bring further changes at this stage.