> Just because you can't get a license for "my personal open source browser" doesn't mean there's a barrier to serious competitors here. (At least, not at present.)
There is no way to know if not one of those "personal open source browsers" they blocked would have become the new chrome. The shared video playback experience of the one they sabotaged sounded neat.
It's not about adblocking, the article gets that wrong. If Chrome limits adblocking there are a bunch of alternatives that allow it. But the DRM control position they lobbied themselves into is in my eyes a barrier of entry to a relevant part of technological projects and something an antitrust case could address.
Yes, there are a few other browsers that can do the same, play DRMed videos. That makes the case harder. But why should Google have the power to control who can build browsers that support streaming sites? All while having economic interests to limit the competition? I think that's still a trust issue.
But I'm absolutely biased. I hated the DRM decision and would love it if it has dire consequences.
There is no way to know if not one of those "personal open source browsers" they blocked would have become the new chrome. The shared video playback experience of the one they sabotaged sounded neat.
It's not about adblocking, the article gets that wrong. If Chrome limits adblocking there are a bunch of alternatives that allow it. But the DRM control position they lobbied themselves into is in my eyes a barrier of entry to a relevant part of technological projects and something an antitrust case could address.
Yes, there are a few other browsers that can do the same, play DRMed videos. That makes the case harder. But why should Google have the power to control who can build browsers that support streaming sites? All while having economic interests to limit the competition? I think that's still a trust issue.
But I'm absolutely biased. I hated the DRM decision and would love it if it has dire consequences.