Over the past few months, we’ve had some productive conversations with the JPEG-XL team at Google Research around the future of the format in Firefox. Our primary concern has long been the increase...
Well Google can still lock Mozilla out of the features and cooperation if they do something Google doesn’t like. It’s just one example. Nobody should ever trust Google.
Google currently allows Mozilla (and others) to distribute this within Firefox, allowing Netflix, Disney+, and various other video streaming services to work within Firefox without any technical work performed by the user
I don’t believe Google would ever willingly take this away from Mozilla, but it’s entirely possible that the movie and music industries pressure Google to reduce access to Widevine (the same way they pressured Netflix into adopting DRM)
yeah, that could indeed happen I suppose, didn’t think of that. Though I wonder if because of EME, an alternative drm solution could be viably implemented.
Well Google can still lock Mozilla out of the features and cooperation if they do something Google doesn’t like. It’s just one example. Nobody should ever trust Google.
like what? I can kinda understand them not cooperating but how on earth could they lock them out of features?
One example I can think of is Widevine DRM, which is owned by Google and is closed source: https://en.wikipedia.org/wiki/Widevine
Google currently allows Mozilla (and others) to distribute this within Firefox, allowing Netflix, Disney+, and various other video streaming services to work within Firefox without any technical work performed by the user
I don’t believe Google would ever willingly take this away from Mozilla, but it’s entirely possible that the movie and music industries pressure Google to reduce access to Widevine (the same way they pressured Netflix into adopting DRM)
yeah, that could indeed happen I suppose, didn’t think of that. Though I wonder if because of EME, an alternative drm solution could be viably implemented.