316 karma · joined October 16, 2009
Neat idea, but wouldn't this still be exposed to ISP-level attacks? Since the user is still loading the page initially in plain HTTP, so the ISP could still inject code, remove the JS redirect, etc.
https://www.crunchbase.com/organization/digitalocean/investo...
> There is no formal definition on what constitutes a "surgical stainless steel", so product manufacturers and distributors apply the term to refer to any grade of corrosion resistant steel.
Also if you look at the dev branch [2], they have been making sweeping changes to the codebase; most recently it appears they have been removing "old" JavaScript libraries like Bower, presumably to move everything to an NPM setup.
If my impression was correct, then Firefox Send supports different use cases than IPFS.
Presumably Basecamp has set up business entities abroad.
https://travel.stackexchange.com/questions/2272/about-differ...
However its full potential is not ready yet, since Firefox has been migrating to WebExtensions, and this has not fully stabilized yet. Long term I think the WebExtensions move also makes sense, since it gives extension authors a stable API to work with, instead of XUL which can break with each Firefox update. And the architecture makes it easier to optimize threading performance and some form of security sandboxing.
So the point is, I think more UI experimentation is on Firefox's horizon, but they have to first stabilize the technical architecture before they can go full throttle on that.
I mean, how could CloudFlare, or anyone, possibly differentiate this from normal scraping/polling/ manual F5 refresh behavior? This sounds like a PhD thesis.
I guess you are asking CloudFlare to quantify the amount of distinct bytes of unauthorized data sent to any particular user agent? But then, any sophisticated attacker would rotate IPs, UA identifiers, and probably even between vulnerable websites, if they had known about this vulnerability.
I don't think it's reasonably possible to rule this out, even with a massive dedication of investigative resources. Like the other commenter said, it's wisest to assume it happened.
The current administration is businesspeople. They know $130k sounds too high, it's anchoring for negotiations. It'll go lower.
But also it's kind of the point of the reform being pushed, right? If somehow $130k is passed, it will obviously disqualify most foreign workers from acquiring these visas, and maybe the current quota of visas wouldn't be met. Then the quota may be lowered in the future, further limiting the visa program.
The point is that by removing the flawed argument, and keeping the legitimate arguments, the overall message becomes stronger.
Your accusation "But you don't care the workers are being abused and working in unsafe conditions." is inventing and attacking something that cjensen never said or implied.
https://cloud.google.com/products/machine-learning/
It's a mistake to just compare Google with AWS, thinking in terms of basic storage and computing. That's boring and obviously there are tons of alternatives, including Snap Inc. building it themselves, for the amount of money cited.
When it comes to cutting edge AI and related, Google's offerings clearly stand out among other cloud services.
This badly needs a source.
This article from 2013 [1] says the opposite, that shorter telomeres are associated with cancer:
In recent years, shorter telomeres have become associated with a broad range of aging-related diseases, including many forms of cancer, stroke, vascular dementia, cardiovascular disease, obesity, osteoporosis and diabetes.
And another [2]:
"Telomere shortening is common in cancer, but the degree of shortening varies from one cancer cell to another within each patient, and this variability may give us a better idea of how prostate cancers behave."
[1]: https://www.ucsf.edu/news/2013/09/108886/lifestyle-changes-m...
[2]: http://www.hopkinsmedicine.org/news/media/releases/in_prosta...
https://web.archive.org/web/*/https://www2.deloitte.com/glob...
They've added https://github.com/naptha/tesseract.js/blob/c26cae7ee956c399...
Echo.js (https://github.com/toddmotto/echo) is another small no-dependency library (1.89 KB minified), which detects elements appearing on screen, and goes a step further to swap the "src" attribute with a placeholder for lazy loading and unloading.
Disclosure: I've submitted a pull request to it.
http://www.cnet.com/news/oauth-2-0-leader-resigns-says-stand...
OP just spells out one way to take advantage of OAuth 2, and tacks on a sensational title.
YeahKIA's comment: Plugins is an interesting approach. But I wonder how friendly it is to non expert users. Same with the writing your own part.
Your comment is only comparing LXDE with other desktop managers, instead of comparing different versions of Lubuntu.
EDIT: It occurs to me you may have mistaken "LTS" for the desktop manager name (LXDE) when you replied. LTS means "Long Term Support".
Also it assumes the OpenSSL team are the first to know about vulnerabilities. Heartbleed has shown that's not always the case.
Manpage for Maps: http://www.erlang.org/doc/man/maps.html
Older documentation for Maps (EEP): http://www.erlang.org/eeps/eep-0043.html
Important note found on the reference manual page:
Maps are considered experimental during OTP 17 and may be subject to change.
The documentation below describes it being possible to use arbitrary expressions or variables as keys, this is NOT implemented in the current version of Erlang/OTP.
Exceptions returns badarg instead of badmap, this will change in the future releases.
Multipeer and WiFi Direct are not compatible. Stackoverflow user @barbazoo hypothesizes Multipeer is using Bluetooth Classic.
iOS Bluetooth Classic is known the be under the Apple MFA Accessory API tight control and lockdown, including the MFA authentication challenge-reposne. Apple controls the MFA encryption keys (either in software or by the accessory authentication chips). It makes it inaccessible to other platforms.