I don't really buy it.
I mean Chrome controls HTML not through the committee, they control HTML because everyone uses Chrome (except iOS, where Apple outright forbids it).

Also MS using Chrome engine doesn't mean they have no say at all, if Google pushes out a feature MS doesn't like, they can just disable it in their version.

Point is, standards aren't made by committee, they're made by pushing out "experimental" features, land-grabbing market share, then documenting them ex-post.

Risk is that they'll create a "DRM webpage" feature where ad-blocking is impossible. Then web developers will use this so they can monetize websites easier. But even with overwhelming market share there are still a million things that can go wrong with such a plan as that.


@cjd @khm I don't know if you're referencing "Web Bundles", but in case you aren't: It's the latest Google thing to block the blockers.



Previously, Google's WebExtensions Manifest v3 causes problems with uBlock Origin and all other tracker blockers: bleepingcomputer.com/news/secu

· · Web · 1 · 1 · 2

@garrett @khm
Thing is, a Googler with a spec sheet and a deadline is no Tim Berners-Lee, or dare I say, Theodore Nelson. While he's desperately trying to convince himself that his overlords will NOT just bolt DRM to his creation the moment it gets traction, he's not going to do amazing work.

Which gets to the heart of Google's problem, they're creatively uninspired.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!