Thanks everybody for the comments submitted so far on the WG rechartering
process, please keep them coming!

I would like to make two requests, if I may:
- feedback on specs and not on the recharter should be submitted to the
GitHub issue tracker for the spec (ping me if you can't find it)
- if you have any feedback that you would like me to voice in the WG calls,
please send me a note with the specifics.

Also, if anybody is interested in participating in the WG calls and
actively shaping the conversations, please let me know! I would very much
appreciate the help.

Thanks,
Panos


On Wed, Jul 11, 2018 at 11:30 PM Randell Jesup <rjesup.n...@jesup.org>
wrote:

> >Adding to what Tom said...
> >
> >1. "Web developers want the ability to observe the performance
> >characteristics of their applications" - they want to do so, but
> >*should* they be allowed to do so? The API would give access to deep
> >performance data that could be used for all sorts of nefarious purposes
> >(profiling, fingerprinting, probing for vulnerabilities, etc.).
>
> The extreme version of this is what Vlad and Benoit (Facebook) have
> proposed in WICG, which is an interface to profiling data for the page
> (origin): https://github.com/vdjeric/js-self-profiling
> Discussion (mozilla) here:
> https://github.com/mozilla/standards-positions/issues/92
>
> One can understand why they'd *want* to be able to profile their code
> in-the-field.
>
> Exposing this today would be have serious same-origin and Spectre
> impacts; in a Fission world these problematic impacts would be (more)
> limited though perhaps not "safe".  (Implied in the current Gecko
> Profiler impl is that other processes could affect how fast your
> origin's process runs, and thus how much progress is made between
> profiler 'ticks',leading to some leakage of information cross-orgin
> between processes.  How large an impact this is I'm not 100% sure at
> this point. If we changed sampling to be runtime-based instead of
> wallclock-based, this (mostly) hides the impact of other processes,
> though secondary effects still exist (cache impacts, etc).
>
> Making it runtime-based would be a largish change...
>
> --
> Randell Jesup, Mozilla Corp
> remove "news" for personal email
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to