Alex RussellAug 6, 2023

Don't know who needs to hear this, but the recent explainer about "Web Environment Integrity":

- will not ship in current form (I'll block it; and yes, I can do that)
- was not an "official" Google propsoal. Individuals with @google.com (and @microsoft.com, etc.) addrs do dumb stuff all the time (ask me how I know!)
- is very much worth worrying about as a direction of travel, but not without context

Show threadFabrice DesréAug 6, 2023
@slightlyoff so you're saying 4 google employees spent time by themselves to publish that proposal and to get an implementation landed in blink, but that's not an official Google project? That looks hard to believe.
Show threadAlex RussellAug 6, 2023

@fabrice I'm saying that implications you'd naturally draw of 4 webkit.org, or mozilla.org, folks doing something similar are absolutely not what you can expect here, in large part because the process is both more open (by design) and more responsive to input (by design).

Blink is used to adjudicating risks from leadership, so the usual "go fever" of other projects, rather than a public exploratory phase, aren't comprable.

Show threadFabrice DesréAug 6, 2023
@slightlyoff sorry but I can't believe that was not vetted by chrome leadership
Show threadAlex RussellAug 6, 2023
@fabrice I used to run Standards for Chrome. Trust me when I say that there's literally no cap on this particular vent.
Show threadocdtrekkieAug 6, 2023
@slightlyoff @fabrice The fact you used to run Standards for Chrome is exactly why we cannot trust you. This is only the *most recent* user hostile proposal by Chrome.
Show threadocdtrekkieAug 6, 2023
@slightlyoff @fabrice If Google wants to portray this as a rogue proposal, Google should clearly indicate that by firing everyone involved. That would engender trust. Actions, not words.
Show threaddango🍡
@ocdtrekkie @slightlyoff @fabrice if you fire everyone who's ever had a bad idea you'll very quickly find yourself with no people left...
Aug 6, 2023 at 8:31pmWeb