Minimal? My understanding is someone was able to pull ETH out at near zero DAI. Nothing the contract didn't allow, but unforseen use of it which caused some people who had invested that ETH to essentially lose their life savings!
I am not a lawyer first of all but this is my understanding: If you buy a greeting card with Banksy art on it do you think you are getting an official licensed print? The greeting card company here says no, you aren't confused, because Banksy doesn't sell official merch. By selling official stuff he is fighting back saying he certainly is selling official stuff (now) and the card company selling cards with his art can be confused for something he endorses.
I like serverless for my own use cases, but I don't usually comment about it. People would probably not be interested. I have an HTTP call happen once every five minutes or so and just record the response. Thats it. About 100 ms of time. I would be paying more if I just had an always-on server doing this type of work. The sentiment we normally hear on HN is from people who really love or really hate something. I appreciate the option, but other than that I'm not going to be telling the world about my simple use case.
Someone make a service that I can submit my email and you'll generate tons of fake passwords for me, then "accidentally" leak them all. When my email and password make their way into the big password lists I want to dilute the real one with thousands of fake ones. If it became the norm that password lists are suddenly full of junk the demand for them would proboably evaporate.
Probably true, but I know some upper level math through programming, and I associate "monoid" with Haskell and an abstract concept, but "tensor" with tensorflow and a more concrete idea.
I got a deep racer at Re:invent but I'm still waiting to get into the preview to play with it. Anyone from AWS cruising the comments here who might be able to enable it for my account?
It's not so much how much CPU each takes up, but that 'make' will waste some time recompiling stuff that doesn't need to be recompiled. Ninja is better about reusing stuff compiled the first time to make the second compilation faster but still accurate.
I think he was trying to show that the TLA+ approach led to easier proofs of the base case and inductive case. I don't think he's arguing that your gcd program is bad. That's what I'd use. But TLA+ might be a good tool to break out when you need to have a solid proof that the code you wrote will always end up getting you the right answer. We probably don't need it for side projects, but it's nice to know that AWS has some proofs around that the services I use there can't end up in an inconsistent state as a result of any coding logic.
I see people already picking apart what you said, but I see where you're coming from. If course lung cancer is not fake cancer, because it's treated at the same places as other types of cancer. We have hospitals for physical illness though, and you usually see mental illness treated at a separate place. The mental health therapists in my town work out of unremarkable buildings behind some restaurants, while the major hospital has a block to itself with flashy signs identifying what it is. I think that is that leads me to see the "illness" in "mental illness" with a different connotation.
Something I've only read up on so far but has me optimistic: http://www.pachyderm.io it will do data versioning and keep track of how intermediate results get produced.
It feels to me like more of a spark competitor, aiming for the people who want more flexibility than Spark and not needing as much cluster setup (a redis cluster is the hardest part). It might even be able to use Yarn to do some of the resource management.
Keras did make it into tf.contrib now (with the release candidate for 1.1). I don't see it going away any time soon. TF-Slim though I'm not sure about. Never really used it myself.
Yes VPN is a good answer here, but another idea to make the data they collect and sell less useful would be something like https://github.com/WhiteBeachStudios/cyberflare to hide your real usage habits among a bunch of artificially generated traffic.
So everyone gets a text-to-speech victim, listens to the conversation, but at gun point writes down something and makes their victim actually say it. Nobody talking on the phones is part of the conspiracy.
As far as I can tell, this may not be faster than theano/torch, but it doesn't sound like it'll be slower. It takes a similar approach of sending all the big computation stuff out to efficient implementations. The "slow" language code is simply building up a graph of work to be done by the efficient implementations.
I'm playing around with this now. Very slick. I don't claim to know how to optimize the heck out of Neo4j but watching txns/sec tells me the bottleneck easily is the neo4j server in my little test.
Yay. I sort of do that. Take things that people like, make them into docker containers, get bored, and move on to the next thing that people like. For anyone reading this, github.com/maccam912 projects are all available to be played with. Obviously forked, but if you want to submit a pull request I'll more than likely accept it. I'm one of those average people who has a lot to learn about programming. Your pull requests will educate me a bit.
Hey early adopters: you have no doubt heard how easy it is to de-anonymize bitcoin transactions. If someone demands 1000 btc to stop them from "swatting" your house, why not let the police know, send a very small amount to the address they no doubt want the money sent to, and let police take it form there?
"FBI now has enough information to conclude that the North Korean government is responsible for these actions"
Their reasons were along the lines of "attacks that look very similar were from North Korea" but were those attacks conclusively linked? I'm also curious how they decided it was the government there, not a rogue group of people.
Correct. He has done time and decided to move on with his life. Stopped being involved with TPB in 2009 except for occasionally blogging about it like he did here.