For understanding: this proof makes sense if you (incorrectly) assume that any two horses are the same color, because then you can take any pair of horses in an n-sized group and split it into intersecting pairs to show that theyre all the same color. With this assumption, this inductive proof would work as well.
>My favorite part of the photographic process was watching prints come to life. I loved starting with a blank sheet of paper and applying various photographic methods to bring the image to life.
>I found that building websites was similarly satisfying. For example, click the "Reveal Image" button to watch an image fade in to the blank canvas!
I think a lot about why I went into computer science and this is the same conclusion I came to. There's something really cool about starting with a blank page and coding in elements that appear one by one and adapting the code to be what you want. Maybe there's other ways to do it but programming seemed to be the most powerful.
Just to be clear, it was video games, not photography that kinda nudged me into programming, but same idea with a blank canvas and having control of it.
Yeah, there's a lot of crypto that's specifically tailored to minimizing the effect of mistakes like IV-reuse and it's not solved, the primitives can't do everything, so it's good to know these pitfalls. This book is more theoretical than that though and there's probably better sources idk.
For most use cases, you should also add a local bind, "-Llocalhost:5900:localhost:5900" or else everyone at the coffee shop will be able to access your insecure Vnc server
We spend a ton of time locking down OS API/ABIs to prevent sandbox violations and I wouldn't trust a shared server with sensitive data unless I had an IT team working on it. JS seems to be a lot better with sandboxing though. You still have to really worry about CSRF though. I use multiple profiles to ensure sketchy sites can't get at my data.
I think JS gets a bad name when people use it to make crazy modal popups or inline video ads or change the way the page scrolls. Beyond that it's cool that devs can get really creative with a website and I love coding in JS. But also you're adding a lot of complexity for that. HTML/css are fine for creating a website that communicates information and maybe even looks nice. And they aren't actually a programming language, they're just data. JS is a full programming language and gives you enough rope you hang yourself and I think developers kinda go off the rails messing with their sites and ruin the user experience.
It is cool that I can have whoever execute code on my machine without worrying if it will get privileged access to it. That is a pretty amazing feature of JS/browsers.
If you know the g's of vibration (force) and the hertz they needed to use on the screen, can't you calculate it? Maybe you also need to know the weight of the passenger as well as the details of their strobe method.
I only skimmed the paper, but I think the title extracts and confuses a small part of the paper:
"Google collects around 20 times more handset data than Apple"
They didn't intend to say that google collects 20x more data than apple in total, which is what the use of the term "devices" kinda leads us to think. The paper seemed to be equally critical of both and this article made it into an attack on google.
Idk which device is worse, but this article title is a bit misleading. Why not just quote the paper directly?
>My computer just does what I tell it to do, and nothing changes unless I want it to.
>whenever I do have to boot into Windows to run some specific application, it's like I've invited a corporate representative from Microsoft into my home. Things are changed for me on updates
Yeah, it is really nice to have a consistent interface. But there is a flip side. Sometimes, people have to change in light of new security problems, and these sometimes need to be done quickly. The most obnoxious of these updates are interface changes (both UI and API). I think Windows does this too much and maybe for non-security related issues. The only real example I can think of is how OpenSSL uses envelope functions because ppl would abuse the primitives [Source: Alexandra Boldyreva, Christopher Patton, Thomas Shrimpton:
Hedging Public-Key Encryption in the Real World].
A bit easier than a ruby script