2,011 karma · joined March 19, 2012
2.5 days is feasible. 10,000 years is not feasible.
>We argue that an ideal simulation of the same task can be performed on a classical system in 2.5 days and with far greater fidelity.
and therefore
>Because the original meaning of the term “quantum supremacy,” as proposed by John Preskill in 2012, was to describe the point where quantum computers can do things that classical computers can’t, this threshold has not been met.
Consider the libsodium example: https://libsodium.gitbook.io/doc/public-key_cryptography/aut.... The crypto implementation parameters are handled under the hood.
If you're interested or skeptical, I would highly recommend this book. It's from the "Sleep Loss and the Cardiovascular System" section of Chapter 8. He includes chapter endnotes discussing sources.
The evidence suggests that this extends far beyond cognitive and psychological health impacts. For example, the author notes that there is a 24% increase in heart attacks the day after we lose an hour of sleep during daylight savings. This is just the tip of the iceberg, in my opinion.
Given these mental and physical risks, it is insane that we allow physicians to routinely work shifts that endanger themselves and lead to measurable drops in their performance.
Both Worldview and GIBS are open source. [3] [4]
Finally, if you're interested in this, also check out https://search.earthdata.nasa.gov, which is a search client on top of NASA's metadata holdings index (CMR). It's not quite as beginner friendly -- it expects that you're somewhat familiar with remote sensing products and geospatial searching -- but it's a good front end into EOSDIS' data.
[1] https://earthdata.nasa.gov/about/science-system-description/...
[2] https://wiki.earthdata.nasa.gov/display/GIBS/GIBS+API+for+De...
That might seem like a ton per week, but consider a PaaS (example-123.herokuapp.com) or a blog platform (example-diary.someblogapp.com).
Personally I'd prefer a wildcard cert there, but at organizations where certificate inventory is a requirement (where they need to track, procure, and invalidate on a per-subdomain basis) Let's Encrypt is a solid option.
> Has this ever actually happened?
Yes. For example: https://krebsonsecurity.com/2018/05/t-mobile-employee-made-u...
That being said, I know they have a blacklist of certain domains. I've seen it once with amazonaws.com [3], and it's possible they have similar entries for azure.com, heroku, etc. They don't publicly release their blacklist.
[1] https://letsencrypt.org/how-it-works/
[2] https://ietf-wg-acme.github.io/acme/draft-ietf-acme-acme.txt
[3] As in "my-loadbalancer-1234567890.us-west-2.elb.amazonaws.com"
Latest image: http://earth.apawl.com
Video of the previous 24 hours at: http://earth.apawl.com/recently
Bonus: Video of the eclipse earlier this week. http://earth.apawl.com/eclipse
It's interesting you mention that, as Smedley Butler was the alleger of the Business Plot -- what he claimed to be a planned coup d'etat on FDR by wealthy businessmen. [1]
As cool as these are, most papers indicate the difficulty of pulling these attacks off -- especially given the easier vectors out there.
"The easiest way for us to protect your data and data about you is to not have that data in the first place. You may be noticing a theme by now: we can’t reveal or abuse data that we don’t have.
We do not have your 1Password data. We do not know your 1Password Master Password. We don’t even know if you use 1Password. We do not know how many items you have in your vault or their type."
https://support.1password.com/private-by-design/#what-we-cou...
I don't want to drag this out, but where do you see the language constraint? You need an MPI binding, sure, but what else?
By codes they mean -- at the minimum -- pretty much anything that requires frequent communication between any or all nodes as a necessary part of computation. (For example, simulations across a large 3D space, where the changing states of particles on node A directly impacts the states of particles on adjacent nodes.)
Scaling-wise? Distributed Elasticsearch doesn't have a Zookeeper dependency, which is nice. But Solr has more sharding flexibility and partition tolerance.
Like everything else, depends on your needs.