Earlier quoted context omitted.
I make this mistake too, but we need to stop calling it an open standard unless it's handed over to a neutral standards-making body. AMP's solution to the URL problem involves another Google-pushed web standard, webpackage. But the big difference is that webpackage is part of the WICG, a community group under the W3C. That's a real standard, this is not. If AMP not handed over to the W3C, I don't think we can or shou…
I'm not at all up on my tech politics, but I'm curious about your implication that the W3C is neutral. Is that something we can take for granted, given the way they went forward with EME[0]? Otherwise, though, I'm inclined to agree. [0] https://www.eff.org/deeplinks/2017/07/amid-unprecedented-con...
I don't think Mozilla was super fond of EME either, but couldn't afford to be "the web browser that can't watch Netflix".
I definitely do remain wary of these groups being forced to rubber stamp things, I do feel Google exerts way too much control even in that space, because due to their monopolies, they can just implement what they want, and sometimes the W3C has to accept it or be irrelevant.