I2Ps don't need any LGTMs. Was there specific feedback you were looking for?
On Wed, Aug 18, 2021 at 10:10 AM Mike Taylor <[email protected]> wrote: > This I2P seems to have fallen through the cracks (understandably lots of > vacation happening this month). > Any thoughts from API owners? > > On 8/9/21 2:20 PM, Ari Chivukula wrote: > > > > > > > > > * Contact emails [email protected] <[email protected]>, > [email protected] <[email protected]>, [email protected] > <[email protected]> Design Doc > https://docs.google.com/document/d/1yhVLyEIpDhhDQf698WkvXBiPcLwxEgCBI4o1FjvXwfM/edit > <https://docs.google.com/document/d/1yhVLyEIpDhhDQf698WkvXBiPcLwxEgCBI4o1FjvXwfM/edit> > Specification https://wicg.github.io/client-hints-infrastructure/ > <https://wicg.github.io/client-hints-infrastructure/> > https://wicg.github.io/responsive-image-client-hints/ > <https://wicg.github.io/responsive-image-client-hints/> > https://wicg.github.io/savedata/#save-data-request-header-field > <https://wicg.github.io/savedata/#save-data-request-header-field> > https://wicg.github.io/netinfo/#networkinformation-interface > <https://wicg.github.io/netinfo/#networkinformation-interface> Summary This > proposal seeks to align our implementation with the Client Hint proposal > <https://wicg.github.io/client-hints-infrastructure/> by adding the > `sec-ch-` prefix where it’s missing. Blink component Privacy>Fingerprinting > <https://bugs.chromium.org/p/chromium/issues/list?q=component%3APrivacy%3EFingerprinting> > Motivation Client Hints > <https://www.chromestatus.com/feature/5995832180473856>, a method to > request information about the user's device or conditions, have been > implemented in Chrome, but since the initial implementation the naming > scheme has changed. If implemented, this proposal would add new client > hints with a `sec-ch-` prefix to re-implement the following: `dpr`, > `width`, `viewport-width`, `device-memory`, `rtt`, `downlink`, and `ect`. > TAG review Not needed * Risks > > * Only Blink implements client hints and we are not (yet) removing any > current ones, just re-implementing existing ones under the correct name. If > usage permits, we will remove the legacy names in the future. * > Interoperability > and Compatibility > > Gecko: Client hints not implemented > > WebKit: Client hints not implemented > > Web developers: Positive interest from Cloudinary > <https://discourse.wicg.io/t/responsive-image-client-hints-call-for-review/5470> > > Is this feature fully tested by web-platform-tests? > > Yes > <https://chromium.googlesource.com/chromium/src/+/refs/heads/main/third_party/blink/web_tests/external/wpt/client-hints/> > > Tracking bug > > https://crbug.com/1227043 > > Link to entry on the Chrome Platform Status > > https://www.chromestatus.com/feature/6658223894429696 > > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7162dcb1-279f-b0f6-4502-6ceb1013980d%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7162dcb1-279f-b0f6-4502-6ceb1013980d%40chromium.org?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAD649j7BodGF%3Dy1Eye-op7wVV-sjhhgKCmVoTKN3MHVAiNBW6w%40mail.gmail.com.
