Changes To Project Risks
Not logged in

Changes to "Project Risks" between 2016-06-22 15:49:59 and 2016-07-04 21:16:41

     1      1   <p></p>
            2  +
            3  +<div>Encryption is not
            4  +<a href="http://archive.softf1.com/2015/2015_xx_xx_British_Prime_Minister_David_Cameron_Wants_to_ban_Proper_Cryptography.webm">outlawed</a>,
            5  +but P2P technology is outlawed and the encrypted P2P data streams are
            6  +blocked/banned.</div>
            7  +
            8  +<div><br>
            9  +</div>
           10  +
           11  +<div><b>Countermeasures: create private physical networks that do not depend on
           12  +traditional Internet Service Providers (ISP-s). As those will also probably be
           13  +outlawed or bugged by law, just like the 2016 traditional ISP-s are bugged, the
           14  +private physical networks have to be made very mobile and dynamic, so that they
           15  +can quickly launch and disappear "without a trace" and the connectivity is
           16  +provided by a probabilistic connection. The more private networks there are,
           17  +the greater the uptime of the probabilistic connection.</b><br>
           18  +</div>
           19  +
           20  +<div><br>
           21  +</div>
     2     22   
     3     23   <div><br>
     4     24   </div>
     5     25   
     6     26   <div>
     7     27   
     8     28   <div>Computers of developers are compromised, so that the project deliverables