Hacker News new | ask | show | jobs
by joshuamorton 2568 days ago
This is an interesting, and relatively fair, article. There are two big issues with it's reasoning though.

First, chrome isn't yet close to IEs peak dominance. Ie peaked at over 90% market share.

Second, DRM isn't necessary for watching video, it's needed for watching certain liscenced video. In practice, this means Netflix and streamed televison. You can still watch YouTube just fine, minus YouTube red originals, without widevine. Is a browser that keeps you off Netflix so bad for google?

3 comments

> First, chrome isn't yet close to IEs peak dominance. Ie peaked at over 90% market share.

Waiting until it hits that to do something about it would be pretty ridiculous. Based on some random stats website, Chrome is currently at 70% share, and Chromium-based browsers are at 77%

further, you can dominate and control a market with a minority share of that market (depending on market characteristics). google's many anti-consumer actions with chrome show that 70%+ market share is more than enough already.
It's pretty much all the paid media on the internet. Spotify, Hulu, netflix, cable providers, amazon, etc.

I guess if you literally only watch free YouTube videos it's not a problem? Totally not an anti-trust issue...

Is Spotify, or Hulu, or Netflix, or any of the others you mentioned owned by Google? No.

So... why would it cause any antitrust violation?

Widevine was not the first DRM for videos, it was already common practice for the big paid video websites to require DRM before it was created.

Imagine we're 20 years into the future and Ford has just successfully managed to lobby (with quite some industry support, mind you) for mandatory Vehicle-to-Vehicle/Infrastructure comms, where every car has to be able to talk to every set of traffic lights, speed sign, and other vehicle.

Now imagine that the V2X standard which just got enshrined in law states that every vehicle has to be compatible with every other vehicle etc. And Ford sat down with GM, Chrysler, Toyota, Honda and Hyundai, and offered them a proprietary component which just so happens to do all this V2X stuff without any hassle. And they all agree to use it.

It only be legally built by Ford, but they're the V2X experts so that's OK, right, I mean they're doing a public service, right? Ford is pretty happy selling this component to GM, Toyota, Honda, etc. for a very reasonable fee, so how can there be an issue?

Now imagine some new car company wants to build cars which compete with Ford's cars, and Ford says 'nope, you can't buy our V2X component.' And booyah, Ford now controls who can and can't enter the market.

Hmm.

> Imagine we're 20 years into the future and Ford has just successfully managed to lobby (with quite some industry support, mind you) for mandatory Vehicle-to-Vehicle/Infrastructure comms, where every car has to be able to talk to every set of traffic lights, speed sign, and other vehicle.

Right, but this is where the analogy breaks down. Its more like "some municipalities decided that cars on their streets had to be specially registered or they wouldn't let you drive. Some people like those municipalities, but they aren't the majority, and you aren't, at all, forced to go near them.

OK, then how about instead of it being a national legal requirement, 90% of roads were privately owned toll roads and Ford convinced a consortium of toll road owners to standardize on their V2X component. So you can build a car without it but that car can't drive to anywhere you want to go.
But again, that still doesn't work, because it's not 90% of toll roads. Like, keep in mind, in this analogy, Ford owns a bunch of roads, and they're all free to travel on. And of course there's also Honda (Microsoft: PlayRead) and BMW (Apple: FairPlay) with their own exclusive components that serve the same purpose, and some municipalities choose to use those instead, or to allow vehicles that use any. Or, most of the municipalities (in concrete terms, the vast majority), don't pass any laws at all.

For your analogy to make sense, the following would need to be true:

1. Apple and Microsoft didn't have competing (and fairly widely used) alternate DRM solutions

2. The average website required DRM to access it.

Without those, this is nothing more than dystopian fanfiction.

I guess the questions are whether:

1. copyright owners forced Google to implement DRM

2. Or, Google welcomed DRM (with the intention of lock-in)

3. Or, Google should have kept Chrome DRM free and fought the copyright owners...

I don’t think those questions matter at all. Regardless of how the current situation arose, it enables strong lock-in to Chrome vs. Chromium.
Amp. Amp is what really scares me about the future of web browsing in chrome.
Pardon my ignorance, but could you elaborate?

What is Amp, and why is it so scary?

Here's an amp page (although it will redirect to regular reddit if you're not on a mobile device):

https://www.google.com/amp/s/amp.reddit.com/r/explainlikeimf...

Basically it's a way for google to promote web pages that are better formatted for mobile devices that use a limited subset of html and restrict use of javascript. The pages are hosted on google.com as additional assurance that they will load quickly.

I do believe it's scary to some because it seems like it's giving google a lot of power and control over content on the web.

More direct AMP link: https://amp.reddit.com/r/explainlikeimfive/comments/5d4x2h/e...

The original page is hosted on the original domain. What other hosts provide are AMP caches to display them faster. For example, Microsoft Bing:

- https://blogs.bing.com/search/September-2016/bing-app-joins-...

- https://blogs.bing.com/Webmaster-Blog/September-2018/Introdu...

- https://www.bing-amp.com/c/s/amp.reddit.com/r/explainlikeimf...

JavaScript disabled? Please stare at our Google-sponsored white screen for eight seconds.
AMP is like the bogeyman here on HN, when it is really just another web framework.

>The pages are hosted on google.com

Anyone can roll their own AMP pages and host it on their domains. For example: https://amp.reddit.com/r/AskReddit/comments/6yj6iw/what_did_...

This includes getting your own amp lightning icon in search results when you host with certified CDNs.

AMP's HTML validator has a hard dependency on cdn.ampproject.org [0]. So the hosting requirements aren't fully isolated, and entirely under your control.

Also, I could not find a list of certified CDNs.

[0]: https://github.com/ampproject/amphtml/blob/master/validator/...

https://github.com/ampproject/amphtml/blob/master/caches.jso...

Google, Bing, Cloudflare are the three official caches, which is what I think they mean.

Not true, you can validate AMP from localhost. The AMP.js packages comes bundled with it's own validator:

https://amp.dev/documentation/guides-and-tutorials/learn/val...

Even then it's quite a stretch to go from saying Google controls AMP to saying the validator has an online requirement. Also, as the other commenter said, Google, Bing, and Cloudflare are currently the certified CDNs to get the icon in search results.