This is pretty concerning to me from a fingerprinting POV. The spec currently rounds up to one of the following values:
0.25, 0.5, 0.75, 1, 1.5, 2, 3, 4, 6, 8, 12, 16, 24, 32, 48, 64, 96, 128 Steam's hardware survey shows the following distribution percentages. Less than 512 MB 0.00% 512 Mb to 999 MB 0.03% 1 GB 0.52% 2 GB 3.30% 3 GB 6.27% 4 GB 14.96% 5 GB 0.66% 6 GB 3.23% 7 GB 2.33% 8 GB 42.77% 9 GB 0.04% 10 GB 0.29% 11 GB 0.18% 12 GB and higher 25.39% The low end is extremely small buckets, and the high end isn't even fleshed out but I'm certain that's becomes small buckets too >16GB too. (Obviously this doesn't take into account mobile, and I couldn't find any reports on distribution of android devices by RAM.) I'm not thrilled about including this at all, but if we did I would strongly recommend significantly reducing the number of buckets reported. Ideally to 2. I haven't seen anything in this that indicates people want to use such nuanced data; they just want to know whether to serve the 'light' or the 'normal' mode. This is reminiscent of NetworkInformaiton API where it was designed to expose a ton of information but really people just wanted to know "Will this cost the user money or not". Is there any reason it can't just report that: 'Low Memory' or 'Not Low Memory'. -tom On Tue, Sep 5, 2017 at 12:13 PM, Shubhie Panicker via dev-platform <dev-platform@lists.mozilla.org> wrote: > Hi, > I work on Chrome Web Platform and we just shipped an API for detecting > Device Memory: > header > <https://groups.google.com/a/chromium.org/d/msg/blink-dev/8qlTjzRY9Mc/BYCuqWJXBwAJ> > and JS API > <https://groups.google.com/a/chromium.org/d/msg/blink-dev/MFBsNZCkotU/heK7JapxAgAJ> > . > Boris expressed privacy concern with the API and suggested starting a > thread here to get some concrete feedback. We would love to get this > feedback and are open to updating the header and API as it would be great > to get FF behind this API. > (It's not too late to update this, larger adoption is gated on > Accept-CH-Lifetime > header > <https://groups.google.com/a/chromium.org/d/msg/blink-dev/QHI3sio6--Q/v_zWX1O6AAAJ> > which would enable sending the CH header on the first request) > > Sincerely, > Shubhie > > PS: As an aside, we discussed the API in the Web Perf WG but unfortunately > Mozilla is not currently participating in the WG and we'd love to address > that going forward. > _______________________________________________ > 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
