Removed the identicon/'Visual Versioning' idea for updates from README,

- may cause more confusion than is worth,
 - best to have Unsender sign updates,
 - if DFCA ever gets stale, it can just be replaced completely.
 - alternate antitrust implementations are of course welcomed, however
     end user should probably pick one implementation to avoid issues.

README.md

@@ -1,6 +1,6 @@
 
 
-<img src="img/dfca_v1-profile_tiny.jpg" width="24"> Digital Feudalism Counter Action (DFCA <img src="identicons/0.2.0.png" width="24" alt="SHA-256 identicon of DFCA 0.2.0"> 0.2.0 beta)
+<img src="img/dfca_v1-profile_tiny.jpg" width="24"> Digital Feudalism Counter Action (DFCA 0.2.0 beta)
 =======================================
 
 We can no longer wait for politicians to enforce antitrust law. Enforce it yourself by blocking the *digital feudalists* and importantly __get a little popup notification__ when a program attempts to contact them (pictured). Also, with a few minor customizations you can see *__which__* program attempted to contact said feudalist. See below image.
@@ -42,7 +42,7 @@ It also, importantly, __tells you when it blocks via a popup message__; vital fo
 
 1. Ensure __[Tor Browser](https://torproject.org)__ and `torsocks` are installed and working.
 
-2. Get the <a href="dfca/raw/branch/master/dfca_0.2.0.tar"><img src="img/dfca_v1-profile_tiny.jpg" width="17">  __DFCA 0.2.0__ <img src="identicons/0.2.0.png" width="17" alt="SHA-256 identicon of DFCA 0.2.0"> __(beta)__</a> package, plus its <a href="dfca/raw/branch/master/dfca_0.2.0.tar.asc">__PGP signature__</a> and <a href="dfca/raw/branch/master/unsender-pubkey.asc">__Unsender's public key__</a> to verify its authenticity using cryptography. If this is your first install go to '[First install](#first-install-beginner-friendly)' section below. Otherwise, check the update is signed by Unsender, or a key you know. The update should be as easy to read and follow as the original install and/or other updates.
+2. Get the <a href="dfca/raw/branch/master/dfca_0.2.0.tar"><img src="img/dfca_v1-profile_tiny.jpg" width="17">  __DFCA 0.2.0 (beta)__</a> package, plus its <a href="dfca/raw/branch/master/dfca_0.2.0.tar.asc">__PGP signature__</a> and <a href="dfca/raw/branch/master/unsender-pubkey.asc">__Unsender's public key__</a> to verify its authenticity using cryptography. If this is your first install go to '[First install](#first-install-beginner-friendly)' section below. Otherwise, check the update is signed by Unsender, or a key you know. The update should be as easy to read and follow as the original install and/or other updates.
 
 3. __Spend 15 minutes or so to enter the well-documented commands__ (if updating, the process may be automated and take less time). Yes, during setup you'll see well-documented bash-script and maybe learn some GNU/linux computer tricks! Double win!!
 
@@ -94,30 +94,12 @@ Removing yourself from their system and rebuilding is not going to be the most e
 
 ## Future development
 
-- __Two-click updates harnessing decentralized method of distribution (eg. torrent, IPFS).__ If not signed by expected key(s) issue warning. Options being; <small>*Download proposed update...*</small> (or <small>*View proposed update...*</small>), <small>*Not now*</small>, <small>*Remind me in a few days*</small>, and if the update has been downloaded <small>*Ignore proposed update*</small>. Use random jitter in all time delays. Starting from DFCA 0.2.0 <img src="identicons/0.2.0.png" width="17" alt="SHA-256 identicon of DFCA 0.2.0"> each update/version should display an __identicon__ (see [Visual Versions](#visual-versioning)) to distinguish between potential updates.
+- __Two-click updates harnessing decentralized method of distribution (eg. torrent, IPFS).__ If not signed by expected key(s) issue warning. Options being; <small>*Download proposed update...*</small> (or <small>*View proposed update...*</small>), <small>*Not now*</small>, <small>*Remind me in a few days*</small>, and if the update has been downloaded <small>*Ignore proposed update*</small>. Use random jitter in all time delays.
 - __Making the 'txt' file a bash script that is still human-readable__... hopefully moreso! And,
 - __Automate creation of 'app isolation groups'__ by finding all `.desktop` files on system, asking user which applications they want to isolate (with an 'All Applications' option?), making individual DFCA groups for them (noting limit to groupname length, a mapping system completely distinct from the current setup may need to be developed 😑?) and then produce the custom desktop files to run applications inside said groups (may be tricky to automate wrapping of complex launch scripts but ultimately a good thing to automate). At the same time implement pre and post-install hooks that would seek to re-produce new and custom, updated`.desktop` files, and likely group-mappings(?), asking user with respect to newly installed applications whether they would like to produce an isolation group for it (not asked if 'All applications' option was selected), and also automatically discarding subsequently unused DFCA groups on install <small>(feedback welcomed. Doing the 'isolation' automatically is expected to be difficult, incl. difficult to read code of, which is a priority of this project).</small>.
 
 
 
-## Visual Versioning
-
-If we imagine that __DFCA Antitrust Law__ becomes so popular that there are multiple versions or forks vying for your attention. By displaying '__identicon__' alongside each potential update/version/fork it becomes easier to distinguish between them. 'Identicons' would be difficult to spoof because they would be based on the SHA-256 hash of a file. Here are some identicons.
-
-![Image of green checked identicon](identicons/example1.png) ![Brown fan identicon](identicons/example2.png) ![White squares on purple identicon](identicons/example3.png) ![Another yellowish-green identicon](identicons/example4.png) ![Dashed outline](identicons/example5.png) ![Sunburst](identicons/example6.png) ![...and finally a white diamond icon](identicons/example7.png) 
-
-In the below script we generate a random but distinct 'identicon' using the version of that is [included with]((http://127.0.0.1:7657/imagegen/)) __i2prouter__. It is the one you see for the latest version, <a href="dfca/raw/branch/master/dfca_0.2.0.tar"><img src="img/dfca_v1-profile_tiny.jpg" width="17">&nbsp;__DFCA&nbsp;0.2.0__&nbsp;<img src="identicons/0.2.0.png" width="17" alt="SHA-256 identicon of DFCA 0.2.0"> __(beta)__</a>. Generating such requires `i2prouter` be running:
-
-```bash
- ##   Store SHA256 of file...
-hash256=$(shasum -a 256 'dfca_0.2.0.tar' | cut --delimiter=' ' --field=1) \
- ##   Generate from locally hosted I2P the 'identicon' image, (s)ize 64 pixels, (O)utput as PNG.
-wget "http://localhost:7657/imagegen/id?c=${hash256}&s=64" -O "identicons/0.2.0.png"
-```
-By changing the input file above that is hashed with `shasum`, its possible to create an 'identicon' for *__any__* file!
-
-
-
 ## List of mirrors (incomplete)
 
 - via [torrent](torrents/DigitalFeudalismCounterAction_0.2.0+(Antitrust+law+by+CYPHERPUNKS).torrent) (torrent file also available from [tracker2.postman.i2p](http://tracker2.postman.i2p/?view=TorrentDetail&id=69969))