- From: Charles 'chaals' (McCathie) Nevile <chaals@yandex.ru>
- Date: Tue, 12 Feb 2019 11:35:50 +0100
- To: public-privacy@w3.org
Assuming CH == Client Hints, I think the repo you want to file issues in is https://github.com/httpwg/http-extensions/labels/client-hints Otherwise write to the HTTPWG with your feedback - or I can introduce you to one of the chairs who can probably help you out further. cheers Chaals On Tue, 12 Feb 2019 01:35:24 +0100, Pete Snyder <psnyder@brave.com> wrote: > Hey folks, > > Just following up on discussed items from last week. This will be my > first time opening issues against a proposed standard, so would > appreciate some mild handholding :) > > TODO #1 > — > Open issues regarding privacy implications of moving JS features to CH > headers (screen size, color depth, etc.) related to logging. > > I’m having difficulty finding the right place to open these issues, as > they’re mentioned in the IETF spec[1], but no similar place in GH. The > closest I can find is Chromium people talking to Chromium people in > fetch here [2]. > > Done anyone have any suggestion / advice on the best place to formally > bring these comments. FWIW Brave is pretty 100% in the c > > > TODO #2 > — > Ask the CH folks for data that shows there are broad use cases for the > headers? > > Again, I would greatly appreciate any suggestions on the most fruitful > place to add these, as currently it seems to be in a dozen places. If > others have suggestion, I would greatly appreciate it :) > > > Refs > --- > 1: > https://tools.ietf.org/html/draft-ietf-httpbis-client-hints-06#section-6.4 > 2: https://github.com/whatwg/fetch/pull/725 -- Using Opera's mail client: http://www.opera.com/mail/
Received on Tuesday, 12 February 2019 10:36:23 UTC