Live data from Hacker News

Firefox 38 released

mozilla.org

31–40 of 133 posts

Re: Firefox 38 released

#31
post #13
post #7

> Mac OS X: Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube HTML5 > Implemented Encrypted Media Extensions (EME) API to support encrypted HTML5 video/audio playback (Windows Vista or later only) HTML5 > Automatically download Adobe Primetime Content Decryption Module (CDM) for DRM playback through EME (Windows Vista or later only) :( Notice which OSes are left o…

What video could you watch before that you cannot watch now? I also wish we lived in a world which didn't need EME but it's not like the status quo was video which played for everyone. It just meant that everyone had to download monthly updates to avoid security problems with the massive plugin they used to play video and Linux, etc. users were largely still screwed.

Honestly, I'd rather developers move their DRM-encumbered video services to native apps and leave the web alone.

Re: Firefox 38 released

#32

> CRITICAL Vulnerability can be used to run attacker code and install software, requiring no user interaction beyond normal browsing. Uh, glad they fixed this one, but it sounds pretty bad. I'd kinda like to see the actual CVE/bug report.

[deleted]

Re: Firefox 38 released

#33
What happened to opportunistic encryption? I loved that feature but it was disabled because of a bug. I hoped it would be enabled again in the next major release, but no mention of it. Can someone from Mozilla tell me more?

Re: Firefox 38 released

#34

Earlier quoted context omitted.

Don't do it. I've been using the non-silverlight Netflix in Safari and it's such a nightmare I switched back. Constantly fails to load content.

Really? I had some issues with the very first release of HTML5 Netflix, but it is pretty solid now.

Might need to look at it again. I used it throughout the last OS X beta and then it still had issues in the first release so I moved away from it.

Re: Firefox 38 released

#36
post #13

Earlier quoted context omitted.

What video could you watch before that you cannot watch now? I also wish we lived in a world which didn't need EME but it's not like the status quo was video which played for everyone. It just meant that everyone had to download monthly updates to avoid security problems with the massive plugin they used to play video and Linux, etc. users were largely still screwed.

There's a big difference - before these moves, DRM delivery of video had to be done using shitty nonstandard plugins or native apps, right? Whenever this happens, usability suffers as well. And we had a real opportunity here to give users an open and non-broken standard as an alternative, on top of which alternative platforms for content delivery could be built, alternatives that could have won simply because of the…

I understand your frustration, but I think you're complaining that you didn't get an option that was never realistically on the table in the first place. Your respect for the W3C matters a lot less to them than millions of people being able to watch content produced by a billion dollar industry, which much of that industry simply isn't willing to make available without DRM-style safeguards at the present time.

Yes, we used to use plug-ins for video. This worked reasonably well for quite a long time. I do think calling those plug-ins non-standard is a bit of a joke, given that Flash had 90+% market penetration for years and ran acceptably well almost everywhere, putting it far ahead of any browser in terms of portability and compatibility. By any reasonable definition, it was the de facto standard for on-line video streaming.

Then Apple decided not to follow that standard and broke the Web for their users. For those users, a lot of major sites still "don't work properly" today because of Apple's arrogance. Browser makers are playing along anyway, so now we have an HTML5 video ecosystem where the closest thing to a universally supported video format is patent-encumbered anyway. It is still supported on fewer systems than video using Flash players used to be. And instead of security flaws with your "non-standard" plug-ins like Flash, you're inevitably going to see security flaws with whatever media extensions you install instead (unless you think low-level, natively executed code written in error-prone programming languages and provided by the same kinds of organisations who used to provide the plug-ins is somehow magically going to be secure this time around, in which case I know a Nigerian prince who has a great deal to offer you).

This isn't progress. In what is becoming a serious and recurring problem with the modern web, issues other than what gives the best experience to users and makes things easiest for content providers to provide content are dominating the discussions. Many of the proposals are advocated by other parties with vested interests. And in the end, the result is that less stuff works, and stuff works less well, than the "legacy", "insecure" standards that have actually done the required job pretty well for a decade or two.

Re: Firefox 38 released

#37
post #7

> Mac OS X: Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube HTML5 > Implemented Encrypted Media Extensions (EME) API to support encrypted HTML5 video/audio playback (Windows Vista or later only) HTML5 > Automatically download Adobe Primetime Content Decryption Module (CDM) for DRM playback through EME (Windows Vista or later only) :( Notice which OSes are left o…

Well ... I have found that thepiratebay works flawlessly to deliver videos on any platform. It is sad that we are moving backwards. Right now I WANT to give netflix money for Daredevil ... and there is no legal way for me to do so ...

Re: Firefox 38 released

#39
post #11

Earlier quoted context omitted.

the syntax is really confusing though. Duplicating characters? I thought it was hard to follow what would end up where https://hacks.mozilla.org/2015/03/ruby-support-in-firefox-de...

The syntax isn't that bad. It's written in a style that gracefully degrades: strip out the HTML tags, and it's perfectly readable, but the furigana shows up inline rather than above. Portions are duplicated to ensure graceful degradation. You type 振り仮名(ふりがな) (with tags demarcating the sections, of course), repeating the り, so it'll show up properly if the browser lacks ruby text support. But if the browser does have…

On iPad the り is only visible in the furigana. On top of that, the furigana is displayed below the text.
Post reply on HN