- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Mar 2020 02:10:41 +0000
- To: public-device-apis-log@w3.org
I think we should reconsider what is feasible in adopting the netinfo API. The API is overly ambitious in that goes beyond the original [use cases and requirements](https://www.w3.org/TR/netinfo-usecases/), and I think that's a problem for adoption because of all the privacy concerns: it adds a large fingerprinting area. The primary use cases are well understood (again, see the use cases and requirements). If we could just solve for "is this a metered connection?" that would be a huge win. Secondary case of "don't download large files" might be handled by other APIs... for example, in theory Fetch could intercept a response, check the expected size, and ask the user if they really want to download such a big file. Anyway, I don't mean to get into the details here, just want to caution that Mozilla will object to taking the Netinfo API as is. We'd probably want some assurance that the scope of that API will be reduced to something less ambitious (specially in light of other recent API additions to the platform that serve a similar purpose). -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/78#issuecomment-596300407 using your GitHub account
Received on Monday, 9 March 2020 02:10:43 UTC