3 ms·
Last I checked, Google still adheres to w3c standards on these things. And they haven't captured the w3c process itself... We need to be holding the w3c account
by shadowgovt 4y ago
Last I checked, Google still adheres to w3c standards on these things. And they haven't captured the w3c process itself... We need to be holding the w3c accountable for considering privacy as they refine new rfcs for apis.
- dmitriid 4y ago> Last I checked, Google still adheres to w3c standards on these things. It adheres to web standards that it primarily writes and pushes through. > We need to be holding the w3c accountable for considering privacy as they refine new rfcs for apis. You know, when w3c does that HN is ablaze with "Safari is the new IE" and "Firefox is irrelevant". See all of hardware APIs (Bluetooth, Serial, HID etc.) that are rejected by both Safari and Firefox primarily on privacy issues.
- MomoXenosaga 4y agoHow did that saying go? It Is Difficult to Get a Man to Understand Something When His Salary Depends Upon His Not Understanding It Follow the money, people in tech get their paychecks from companies that do not respect privacy. And I don't mean that as an accusation: in capitalism it is your duty to do whatever you can get away with.
- satao 4y agoWho do you think proposose the standards?
- pmoriarty 4y ago"We need to be holding the w3c accountable for considering privacy as they refine new rfcs for apis." How do we do that?
- losingom 4y agoIt's actually the WHATWG you need to watch[0], not the W3C. The latter has had basically no power for some time now and only endorses what the WHATWG propose[1]. [0] https://github.com/whatwg/sg https://github.com/whatwg/sg [1] https://www.w3.org/2019/04/WHATWG-W3C-MOU.html https://www.w3.org/2019/04/WHATWG-W3C-MOU.html
- 0xy 4y agoYou know Google literally writes the specifications that are subsequently used by advertisers to fingerprint users, right? For example, the AudioContext API allows websites with zero audio to query sensitive personalized information about your audio equipment, with no permission. It was written by a Google employee, and implemented first in Chrome, then abused throughout DoubleClick's (owned by Google) display advertising network.
- shadowgovt 4y agoThat's what I mean by "holding them accountable." So Safari and Firefox should implement that API behind a privacy-check flag (same as we get for location services, etc.). If Google complains it's not to spec, tell Google to fix the spec. Don't rubber stamp specs that aren't privacy-conscious; Apple, Mozilla, and Microsoft are WHATWG standards members too.