I say we request that businesses and government agencies (especially ones we know they've gone after) set up poorly secured areas with misinformation about "important" projects and such. Not only do we get them with misinformation, but try to bury them with gobs of data in the form of poorly scanned (un-OCRable) image files.
(Yes, I know the plan probably has flaws, but a boy can dream.)
Mozilla & Epic worked together on this together. They used Emscripten, which Mozilla developed, to compile to asm.js, which Mozilla developed and put an optimized module in Firefox's Javascript engine. So I'd say it's little more than Epic choosing Firefox.
FxOS only runs open web standards (HTML, CSS, JS, etc.) - C/C++ not being one of them. Any web apps should then be able to run on Android (via Firefox) and in the future Chrome OS, Ubuntu Touch, etc. I say "in the future" because I don't know that everyone has yet settled on an app packaging standard. If Firefox OS included C code in apps, among other implications, those apps would not be usable everywhere.
Currently though, C/C++ code can be compiled via Emscripten to asm.js, a Javascript subset. It will run in any browser, but Firefox is including an optimized module for asm code which gets closer to native compiled speeds than previously seen. It looks as though Chrome may be including their own asm module as well.
From what I've seen (the non-profit) Mozilla is probably one of the most trustworthy organizations on the net. Protecting users is a part of their mission and they've historically gone out of their way to make sure user info is protected and is not monetized. As an example, Firefox Sync (which is actually open & could be implemented on any device or browser) encrypts bookmarks and passwords with extremely high encryption on your device before sending it to the server. The key is only stored on your device such that even if a governing body forced Mozilla to give up your data they still could not decrypt it. Recently they've become very unpopular in some circles (ok, just one primarily) by choosing to block third-party cookies from sites you've never visited. This prevents tracking cookies from ad companies (following you and your activities around the net).
So as far as phone makers, I'd put them at the bottom of the list of folks I'm concerned about tracking me.
That is the whole point of FirefoxOS, get rid of all the extra layers and pretty much only run a rendering engine on top of a Linux kernel (exceptions are things like: wpasupplicant).
FirefoxOS runs *on top of* Android, it *adds* layers, not removes them. And the very few "layers" that are actually removed (dalvik) are replaced with *slower* layers (JavaScript)
Why are you correcting him when he was right? Did you bother to look it up? FxOS is running on a Linux kernel the same as Android. It is not running on top of Android. You said that it does not remove layers and then immediately cited a layer that was removed. Here is an overview of the Android architecture, can you tell me which layers *didn't* get removed? (I'll give you a hint, there's only one) http://en.wikipedia.org/wiki/File:Android-System-Architecture.svg
Indeed, if mere destruction was their aim, they succeeded. But beyond taking out the vulnerable machines, if this attack has left enough of a cultural impact, it may have instilled a greater vigilance among South Koreans, such that not only will the [presumably] reinstalled machines be fully patched and secured, but the defenses of the still-standing machines will be shored up higher in the future.
If a large enough amount of computers in my city were wiped, it would make the news, people would be talking about it, people would be asking how to protect themselves, installing antivirus, grandmas calling grandsons, etc, etc.
North Korea may have just made it much more difficult to cyber-attack South Korea in the future.
"Hi, yeah, could I get a number 2 with a coke? Oh, and large fries. And can you reduce the complexity on that? By how much? I don't know, 100%? Oh, you can only do 97? Ok fine, I'll take that. Oh, and a chocolate shake."
...capable of obliterating small boats and unmanned aerial vehicles...
Could it not also obliterate *manned* aerial vehicles? Also, if it can take out a small boat, what about aiming it at the bridge of a large boat? That seems like it could have a potent effect.
Maybe it's crazy, but would it be possible to inject something into the water to turn it into a solid or pseudo solid? Whether jello-like, plastic, or glue, something that keeps the water from leaving the containers and/or getting into the groundwater.
First thoughts that come to mind would be substances that solidify with time after having a chance to permeate or a combination of substances, one which permeates and the other which acts as a catalyst for solidifying.
Sure, you might need a lot of it, but it's a really bad problem and there will surely be more cracks in the future. Heck, maybe some day you could haul it off in blocks to a more appropriate location/facility.
If such a substance doesn't exist yet, now seems like a good time to invent it.:)
Firefox devs have contracted a severe case of "me-too-itis" from Chrome.
Yes, it can't have been that it's obviously more convenient not to scrap your current browsing session in order to open a private window, or that users actually wanted this.
Correct. All Private Browsing windows share the same session. Once the last Private Browsing window has been closed, though, the session is discarded. Open a new private window and you'll have to log in again.
The TSA has had almost free range to infringe on US citizen's rights without consequence (increasingly so since the terror-pocalypse). Publicizing these type of stories is good, but how can we best see their powers reigned in and actually enforce respecting our rights?
Perhaps equally exciting to me is that asm is going to be used to speed up Firefox's Ionmonkey JIT. Devs will compile asm code and compare it to native to find inefficiencies, thereby learning where to optimize the compiler. So even if you don't use asm.js, we all get faster Javascript.
The more interesting (though not entirely surprising) bit from this news is that MPEG LA might not actually own all the patents required for H.264 to work.
In which case it might be in MPEG LA's interest to work to invalidate the patents.
Slashdot Mirror
I say we request that businesses and government agencies (especially ones we know they've gone after) set up poorly secured areas with misinformation about "important" projects and such.
Not only do we get them with misinformation, but try to bury them with gobs of data in the form of poorly scanned (un-OCRable) image files.
(Yes, I know the plan probably has flaws, but a boy can dream.)
Mozilla & Epic worked together on this together.
They used Emscripten, which Mozilla developed, to compile to asm.js, which Mozilla developed and put an optimized module in Firefox's Javascript engine.
So I'd say it's little more than Epic choosing Firefox.
Unfortunately they think blinking == attention getting, whereas we think blinking == f*cking irritating.
Admittedly, they're right. Fortunately, we're righter.
FxOS only runs open web standards (HTML, CSS, JS, etc.) - C/C++ not being one of them.
Any web apps should then be able to run on Android (via Firefox) and in the future Chrome OS, Ubuntu Touch, etc. I say "in the future" because I don't know that everyone has yet settled on an app packaging standard.
If Firefox OS included C code in apps, among other implications, those apps would not be usable everywhere.
Currently though, C/C++ code can be compiled via Emscripten to asm.js, a Javascript subset. It will run in any browser, but Firefox is including an optimized module for asm code which gets closer to native compiled speeds than previously seen. It looks as though Chrome may be including their own asm module as well.
From what I've seen (the non-profit) Mozilla is probably one of the most trustworthy organizations on the net. Protecting users is a part of their mission and they've historically gone out of their way to make sure user info is protected and is not monetized.
As an example, Firefox Sync (which is actually open & could be implemented on any device or browser) encrypts bookmarks and passwords with extremely high encryption on your device before sending it to the server. The key is only stored on your device such that even if a governing body forced Mozilla to give up your data they still could not decrypt it.
Recently they've become very unpopular in some circles (ok, just one primarily) by choosing to block third-party cookies from sites you've never visited. This prevents tracking cookies from ad companies (following you and your activities around the net).
So as far as phone makers, I'd put them at the bottom of the list of folks I'm concerned about tracking me.
That is the whole point of FirefoxOS, get rid of all the extra layers and pretty much only run a rendering engine on top of a Linux kernel (exceptions are things like: wpasupplicant).
FirefoxOS runs *on top of* Android, it *adds* layers, not removes them. And the very few "layers" that are actually removed (dalvik) are replaced with *slower* layers (JavaScript)
Why are you correcting him when he was right? Did you bother to look it up? FxOS is running on a Linux kernel the same as Android. It is not running on top of Android. You said that it does not remove layers and then immediately cited a layer that was removed.
Here is an overview of the Android architecture, can you tell me which layers *didn't* get removed? (I'll give you a hint, there's only one)
http://en.wikipedia.org/wiki/File:Android-System-Architecture.svg
They haven't started legal action.
It's been said before: The one's most responsible for Microsoft's demise will be Microsoft.
...for the screen cleaner & cloth that comes with it.
Creating Nazi/Anarchist/pro-baby torture groups on Facebook and adding public officials to them.
Wee!
Indeed, if mere destruction was their aim, they succeeded. But beyond taking out the vulnerable machines, if this attack has left enough of a cultural impact, it may have instilled a greater vigilance among South Koreans, such that not only will the [presumably] reinstalled machines be fully patched and secured, but the defenses of the still-standing machines will be shored up higher in the future.
If a large enough amount of computers in my city were wiped, it would make the news, people would be talking about it, people would be asking how to protect themselves, installing antivirus, grandmas calling grandsons, etc, etc.
North Korea may have just made it much more difficult to cyber-attack South Korea in the future.
"Hi, yeah, could I get a number 2 with a coke? Oh, and large fries. And can you reduce the complexity on that? By how much? I don't know, 100%? Oh, you can only do 97? Ok fine, I'll take that. Oh, and a chocolate shake."
...capable of obliterating small boats and unmanned aerial vehicles...
Could it not also obliterate *manned* aerial vehicles?
Also, if it can take out a small boat, what about aiming it at the bridge of a large boat? That seems like it could have a potent effect.
How did a purportedly non-partisan story like this get on slashdot?
How did Doctor Who know??
(See Gridlock, season 3, ep 3, for reference of giant crabs created by excessive vehicle emissions.)
They spelled "Center" wrong...
Someone should tell them.
Maybe it's crazy, but would it be possible to inject something into the water to turn it into a solid or pseudo solid? Whether jello-like, plastic, or glue, something that keeps the water from leaving the containers and/or getting into the groundwater.
First thoughts that come to mind would be substances that solidify with time after having a chance to permeate or a combination of substances, one which permeates and the other which acts as a catalyst for solidifying.
Sure, you might need a lot of it, but it's a really bad problem and there will surely be more cracks in the future. Heck, maybe some day you could haul it off in blocks to a more appropriate location/facility.
If such a substance doesn't exist yet, now seems like a good time to invent it. :)
i.e. the comments and variables are simply too full of expletives and racial slurs to bother cleaning up.
Even though the transducer is tiny, it can reach volumes of up to 120 decibels.
We've found our next form of torture.
Firefox devs have contracted a severe case of "me-too-itis" from Chrome.
Yes, it can't have been that it's obviously more convenient not to scrap your current browsing session in order to open a private window, or that users actually wanted this.
Correct. All Private Browsing windows share the same session. Once the last Private Browsing window has been closed, though, the session is discarded. Open a new private window and you'll have to log in again.
The TSA has had almost free range to infringe on US citizen's rights without consequence (increasingly so since the terror-pocalypse).
Publicizing these type of stories is good, but how can we best see their powers reigned in and actually enforce respecting our rights?
Perhaps equally exciting to me is that asm is going to be used to speed up Firefox's Ionmonkey JIT.
Devs will compile asm code and compare it to native to find inefficiencies, thereby learning where to optimize the compiler.
So even if you don't use asm.js, we all get faster Javascript.
Another reason for WebRTC to take off.
The more interesting (though not entirely surprising) bit from this news is that MPEG LA might not actually own all the patents required for H.264 to work.
In which case it might be in MPEG LA's interest to work to invalidate the patents.