3 ms·
The danger from a dearth of independent implementations revolves mostly around programming errors; i.e. if everyone uses Chromium code, and it has a bug with so
by kmeisthax 6y ago
The danger from a dearth of independent implementations revolves mostly around programming errors; i.e. if everyone uses Chromium code, and it has a bug with some particular CSS property, it will inevitably become web standard behavior anyway since content will be written to rely upon the bug. (See also: Adobe Flash)
It does not foreclose downstream Chromium users' ability to strip out or restrict features they believe to be harmful to user privacy; as all the code is provided under a variety of Free licenses that are specifically designed to allow removing unwanted functionality.
- Daho0n 6y agoPrivacy is as much about adding features as removing them. Rewriting APIs that no one else have the manpower to reimplement and update for decades is a bigger problem than adding privacy invasive features. Google could easily make changes big enough that it would break for example Brave's ability to add the features it wants. Like a new API that cannot be used by adblockers as effective as the old one..
- spideymans 6y ago>Privacy is as much about adding features as removing them This is a perspective that's often missing from discussions surrounding web APIs. These APIs aren't just about what cool new things legitimate developers can do with them. They're also about what they'll enable bad actors to do. APIs must be designed defensively, otherwise we risk users feeling [even more] unsafe on the web.
- deleted 6y ago[deleted]