Kryptor

The text of the resolution is very short, it simply says the FCC rule is repealed. You can read the rule here:

https://www.federalregister.gov/documents/2016/12/02/2016-28...

At 73 pages, it's a doozy. I don't know exactly what the effects would have been, but one important thing to note that I did not see mentioned once in any of the reporting about this is that the rule has only been in effect for 84 days. So I wouldn't expect any changes to be too noticeable.

Also worth noting is that whatever restrictions on ISPs are removed by this, it doesn't guarantee that ISPs will start doing that thing immediately, if at all. I also haven't seen reporting on what past behavior ISPs have already engaged in that this rule would have stopped.

This theorem only applies to ordinal voting systems. Cardinal voting algorithms like score and approval voting escape this predicament.

http://rangevoting.org/ArrowThm.html

>Our kids are homeschooled,

Now it all makes sense. You're fitting right into the home-schooling parent stereotype.

Checking for encrypted packets wouldn't tell you anything about the binaries' trustworthiness. A back door might just encrypt the data with a second key, or more specifically, encrypt the key that encrypts the data with another key. A reliable way of testing binaries doesn't seem very feasible to me. It's like antivirus vendors trying to find new viruses: the malware authors can always obfuscate their code just a little more, do it just a little bit differently, and now it does the same thing while escaping detection.

Authors of open source software who want to distribute trustable binaries should include instructions for how to reproduce the binary exactly from the source. A third party verifier could reproduce the binary, then publish a digital signature affirming that they reproduced it, allowing anyone who doesn't want to compile it to check with a trusted third party.

But all of that is a moot point if the source code isn't being very carefully checked.