Earlier quoted context omitted.
> The blame for this sits squarely on the w3c for their efforts in trying to replace flash by letting the content companies dictate standards for encrypted playback. The blame for this sits squarely on the users for their tolerance of malware (which DRM is) in the browsers that they use.
This is a truly out-of-touch comment. People want their content first and foremost. Besides, any kind of large-scale user revolt that isn't basically just a mob-like reaction is usually the result of a top-down, coordinated campaign. See the protests against SOPA/PIPA for an example - big websites had to throw their weight behind the idea for it to take hold. The web is simply too diverse and quick moving of a place…
I tried creating a web browser, and Google blocked me
131–140 of 632 posts
Re: I tried creating a web browser, and Google blocked me
#132Re: I tried creating a web browser, and Google blocked me
#133The blame for this sits squarely on the w3c for their efforts in trying to replace flash by letting the content companies dictate standards for encrypted playback. If they had held fast, we could have forced the companies to do their key management in something like WebAssembly and avoided this gatekeeping mess.
Blame Google and Microsoft. They were the people who created the specification, and pushed for it, when Netflix came begging for a solution to their DRM conundrum. Even if the W3C hadn't approved it, that's two of the big four browser vendors who are committing to implementing it anyways, which is enough to guarantee a de facto standard anyways.
Re: I tried creating a web browser, and Google blocked me
#134Re: I tried creating a web browser, and Google blocked me
#135I wont use browsers with widevine. I refused to include widevine in any browser I worked on. Widevine is clearly a backdoor and chrome is often installed setuid root
out of curiosity, which browser(s) do you use?
Re: I tried creating a web browser, and Google blocked me
#136Earlier quoted context omitted.
I hope Kodi makes some decent progress. I installed it a few weeks back and it is a rough experience. The docs on how to do simple things seem to be nonexistant because they don't want to be sued and shutdown entirely.
I think Kodi has made amazing progress. I've not had issues getting it installed on different devices since the 15.x days. Currently run it on 4 different dedicated devices in my apartment as well as some mobile and media devices. > The docs on how to do simple things seem to be nonexistant because they don't want to be sued and shutdown entirely. What docs are you looking for? They have a very extensive wiki as well…
Re: I tried creating a web browser, and Google blocked me
#137The blame for this sits squarely on the w3c for their efforts in trying to replace flash by letting the content companies dictate standards for encrypted playback. If they had held fast, we could have forced the companies to do their key management in something like WebAssembly and avoided this gatekeeping mess.
No, if the Director had overridden the majority of the membership, the browser vendors would've shipped something anyway, and the YouTubes and Netflixes of the world would be using it anyway.
Re: I tried creating a web browser, and Google blocked me
#138This is why I break DRM when I can, treating its presence as advisory at best. From a balancing test standpoint, if you want a technological solution to people copying your work then I think you should not be allowed to claim copyright protection of your work. Pick a legal or technical solution to unauthorized copying, not both.
That said, the media industry as a whole has pushed more than what's necessary to protect its content (eg. DMCA, extending the copyright window) and a more fruitful course of action is to get Congress to change those laws.
Re: I tried creating a web browser, and Google blocked me
#139Earlier quoted context omitted.
How would that have improved the current situation? The videos that Metastream wants to play would still have been DRM'd and would still be playable in the mainstream browsers. What would the benefit have been? What burden is being placed on people now that wouldn't be placed on people in that scenario?
Making the user experience of DRM worse is better because then fewer people will use it. If the platforms all made it so that you have to solder a new chip into your phone before you can play DRM content, there would be a lot less DRM. The argument that platforms have to do this for competitive reasons is doublethink. If the experience is worse and that will cause customers to flee, how is it that they would only fle…
The DRM module would still ship with Chrome and Edge (and likely Safari too, given Apple became involved pretty quickly), you'd still need multiple different streaming formats (in the form of different DRM formats) as you do today, and maybe you'd need slightly different JS codepath per-browser too (but that's not a big difference to today with the different DRM formats).
It's very unclear to me that the W3C refusing to be involved from day one would've led to any outcome very more than subtly different than the one we ended at. At the point that the specification went to Recommendation, there were already multiple interoperable implementations, so objecting at that point was purely a matter of principle, it literally wouldn't have affected the outcome in any way.
Re: I tried creating a web browser, and Google blocked me
#140Earlier quoted context omitted.
This is a truly out-of-touch comment. People want their content first and foremost. Besides, any kind of large-scale user revolt that isn't basically just a mob-like reaction is usually the result of a top-down, coordinated campaign. See the protests against SOPA/PIPA for an example - big websites had to throw their weight behind the idea for it to take hold. The web is simply too diverse and quick moving of a place…
I can't speak for the person you're responding to, but it doesn't seem like much of a mystery why non-techies don't know about the specific details of why they can't save a streamed movie to watch it offline, or in a non-approved open source video player. That glib attitude of captive audiences is exactly what DRM vendors prey upon. They know exactly how much they can get away with at this point.
To me, the mystery is not that the people don't know about these details (these details are indeed somewhat complicated - I agree), but how much they don't care.