231–240 of 398 posts
Earlier quoted context omitted.
Its not like html5 has all of the features required to replace flash cross platform. These changes force developers, especially those that work in video publishing to implement a variety of implementations for each device whereas flash gave us one platform that technically works on everything but is now disabled intentionally.
I can't wait for HLS support http://www.jwplayer.com/html5/hls/
Earlier quoted context omitted.
Hello is just few (hundred?) lines of Javascript giving UI to WebRTC. Unless you want to remove WebRTC and that's just stupid.
Removing registration on Hello servers and WebRTC altogether is not stupid if you give a shit about your privacy, look at the leaks WebRTC provides, local IPs which are great for fingerprinting, real IPs from behind VPN, etc. It's one big gaping privacy nightmare so far, so it's pretty reasonable to have it disabled, until this gets sorted out at least. Fortunately it can be toggled off in about:config easily. Set lo…
Off should be default. Let those that want to use these features turn them on if they want. Or better yet, ship a damn extension.
Earlier quoted context omitted.
The final act of HTML5 delusion - it becomes "ready" because we say it's "ready". It's just someone forgot to ask Flash (game) developers' opinion. Not that it matters, right?
I did the "click to activate" option for flash in firefox. I like it. (Safari and chrome can do this too). This way if flash is activated when really needed. https://support.mozilla.org/en-US/kb/set-adobe-flash-click-p... I feel your pain. The university site I'm working on has flash protein visualizations. We're finally moving visualizations to js. We'll get there, but with flash being kinda turned off, users will h…
To quote a Chrome developer: "Click to play is not actually a security boundary. In particular, it has always been subject to click-jacking."
Mark from Mozilla here. To be clear, by "blocked" Flash we really mean enforced click-to-activate. User choice is always a #1 priority at Mozilla. We regularly block vulnerable plugins. What made this block different was that we did it before Adobe made an update available. Now that Adobe has released an update, it is no longer true that every version of Flash Player is blocked in Firefox. However, we're glad to see…
Do you have any interest an organizing an effort, along with Facebook's Alex Stamos and other folks, to plan a formal EOL for Flash? Of course, the steps Mozilla and others have taken help, but perhaps a more organized movement could get other thought and market leaders on board, trigger higher rates of HTML5 adoption and foster the bits of remaining innovation that are needed to fully replace Flash on the web.
Also, does Firefox plan to address the concerns brought up about Hello, and, more importantly, Pocket?
Bugs are always bad (and security bugs even more so) - but I've always felt that Flash gets a disproportional amount of hate/hype in the media. To some degree it should be normal that the more widespread a technology is - the more it gets targeted for security exploits. If you run the popular browsers/plugins against the National Vulnerability Database, you'd get the following results (as of January 2014): - Internet…
> If you run the popular browsers/plugins against the National Vulnerability Database... That's misusing statistics, you can't determine how secure something is by just summing up the number of vulnerabilities - equally weighing/comparing browsers with a plugin etc. By the way, Apple's opinion on Flash in 2010: Third, there’s reliability, security and performance. Symantec recently highlighted Flash for having one of…
Mark from Mozilla here. To be clear, by "blocked" Flash we really mean enforced click-to-activate. User choice is always a #1 priority at Mozilla. We regularly block vulnerable plugins. What made this block different was that we did it before Adobe made an update available. Now that Adobe has released an update, it is no longer true that every version of Flash Player is blocked in Firefox. However, we're glad to see…
Earlier quoted context omitted.
Removing registration on Hello servers and WebRTC altogether is not stupid if you give a shit about your privacy, look at the leaks WebRTC provides, local IPs which are great for fingerprinting, real IPs from behind VPN, etc. It's one big gaping privacy nightmare so far, so it's pretty reasonable to have it disabled, until this gets sorted out at least. Fortunately it can be toggled off in about:config easily. Set lo…
It is getting annoying to have to go into about:config with every release to turn things I don't want off. Off should be default. Let those that want to use these features turn them on if they want. Or better yet, ship a damn extension.
I'm a Pocket user, but I have no idea why that needed to be integrated into the browser, seems like an insane decision to me. I hope they got a good pay day out of that.
Same as the history based advertising tiles. Sure, it's checked locally, it still seems creepy and annoying... but again, browser.newtabpage.enhanced = false.
Unless we lose this level of user choice, I don't see a better alternative. It would be nice if someone would ship some tool to automatically update a user.js file, however, I think many of us have different opinions about what feature we do and do not want enabled in our browsers.
Earlier quoted context omitted.
Hello is just few (hundred?) lines of Javascript giving UI to WebRTC. Unless you want to remove WebRTC and that's just stupid.
Removing registration on Hello servers and WebRTC altogether is not stupid if you give a shit about your privacy, look at the leaks WebRTC provides, local IPs which are great for fingerprinting, real IPs from behind VPN, etc. It's one big gaping privacy nightmare so far, so it's pretty reasonable to have it disabled, until this gets sorted out at least. Fortunately it can be toggled off in about:config easily. Set lo…
Edit: Ah, looks like I needed to update Chrome with the fix.
Earlier quoted context omitted.
Firefox can actually use ffmpeg as a decoder. It would be a great option for supporting a lot of these formats. However, Mozilla can't ship it enabled, because the patent problem is very real. See, for example, all of the Play Store apps that got C&D letters from Dolby for using ffmpeg's implementation of AC3. Firefox does ship a lot of other video and audio codecs though, such as vorbis, opus, theora, vp8, and vp9.…
> However, Mozilla can't ship it enabled Just a minor nitpick: Under Linux, people don't download from Mozilla but have it installed by default. If not, they install via package manager and not via download from Mozilla. So it's not Mozilla making that decision, but the respective Linux distros. But of course they have the same problem. I believe a good compromise would be to check if ffmpeg is installed on the syste…