silentOpen

To ensure that drivers are insured, Uber has responsibility.

This doesn't make it any less of an asshole behavior, though. Also, it should not be the onus of each target of your gaze to constantly be saying "stop it". That's called "opt-out" and is pretty globally regarded as completely obnoxious.

Despite "Like" only subscribing you, Facebook has given that action a connotation of endorsement by naming the action "Like" which suggests agreeableness, enjoyment, or satisfaction.

Also, if a given, well-known resource could be pinned to a specific hash and third-parties could easily certify that specific hash, would that ameliorate the primary concerns with JS cryptosystems?

Thanks for your time.

Consumer mobile telecom in the US is fundamentally broken.

Is security important to US military or not? Both having lax security at the time of breach and then severely punishing a leaker for using trivial tools does not inspire confidence in the competence of our military security.

I see now that Scala can encode GADTs in case classes. What mechanism is available to encode polymorphic variants? Particularly, I am interested in writing matches over unions of polymorphic variant types.

I disagree that 2 and 3 are the same (structural module subtyping, nesting, inclusion differs from applicative functors). I believe you can achieve mixins with OCaml through the object system but it's not clear to me that this addresses functor signature checking.

Another Scala bonus: 5. Objects can implicitly be null.

1. Tail call elimination 2. A full-featured module system 3. Functors (functions at the module level) 4. First-class modules 5. GADTs 6. Polymorphic variants 7. A decidable type system 8. ... more?

Things OCaml lacks which Scala has:

1. Traits 2. Implicits 3. Trivial Java FFI 4. Seamless syntactic macros (c.f. camlp4) 5. ... more?

If the FBI wants carriers to install software on their network devices, the FBI is implementing regulatory law as code in the network substrate. The source and its build and development process must be public. They have no magic tricks and there is no unknown capability that this could compromise. It's simply a requirement for a country governed by the law. It's how we watch the watchers.

Seeing as how we can't even get voting machine source code released, I have little faith that the spy state will cede its code in the near future. Given this, it's now time for all able-minded hackers to build tools for personal liberty and spread them far and wide. Godspeed.

... over here, too < https://www.mtholyoke.edu/acad/intrel/orwell46.htm >

If you have only pure objects, you can still perform open recursion and leverage structural polymorphism (including row variables). Additionally, your objects are just values and, because they aren't mutable, can be held for backtracking.

For instance:

```ocaml class virtual biggable x = object val x = x method x : int = x method virtual embiggen : biggable end

let o = object (self) inherit biggable 0 method embiggen = {< x = x + 1 >} end

let q f o = object (self) val x = o#x method x = x method embiggen = f {< x = x * 2 >} end

let a = q (q (fun x -> object inherit biggable x#x method embiggen = {< >} end)) o#embiggen

;; # a#x;; - : int = 1 # a#embiggen#x;; - : int = 2 # a#embiggen#embiggen#x;; - : int = 4 # a#embiggen#embiggen#embiggen#x;; - : int = 4 ```

It's not quite as smooth, as far as I know, but it will soon include C header consumption and C stub generation to both improve binding accuracy/safety and remove dynamic paths for performance.

I always know when I have been shot by a police officer.

I do not always know when my data has been copied even with your assertion of Google's good will. Your conditional of "when Google is legally permitted..." is quite telling (information is fluid and ephemeral) and makes your contradiction, "False.", laughable.

The case of personal data privacy and control is categorically different than the case of physical violence.

You don't know when Google exports your records.