Fix unshown messages when pubkey key arrives after them. Fix docs

docs/_includes/feature_row

@@ -11,8 +11,10 @@
       <div class="archive__item">
         {% if f.image_path %}
           <div class="archive__item-teaser">
-            <img src="{{ f.image_path | relative_url }}"
+            <a href="{{ f.url | relative_url }}">
-                 alt="{% if f.alt %}{{ f.alt }}{% endif %}">
+              <img src="{{ f.image_path | relative_url }}"
+                  alt="{% if f.alt %}{{ f.alt }}{% endif %}">
+            </a>
             {% if f.image_caption %}
               <span class="archive__item-caption">{{ f.image_caption | markdownify | remove: "<p>" | remove: "</p>" }}</span>
             {% endif %}

docs/_pages/docs/00-quick-start/03-access.md

@@ -46,6 +46,16 @@ Or unsafely on the testnet clearnet bridge.
 
 > [unsafe.testnet.robosats.com](http://unsafe.testnet.robosats.com)
 
+### Onion Mirrors
+
+It is possible to access the **testnet** platform on the port 8001 of the mainnet onion
+
+> [robosats6tkf3eva7x2voqso3a5wcorsnw34j<br/>veyxfqi2fu7oyheasid.onion:8001](http://robosats6tkf3eva7x2voqso3a5wcorsnw34jveyxfqi2fu7oyheasid.onion:8001)
+
+It is also possible to access the **mainnet** platform on the port 8001 of the testnet onion
+
+> [robotestagw3dcxmd66r4rgksb4nmmr43fh7<br/>7bzn2ia2eucduyeafnyd.onion:8001](http://robotestagw3dcxmd66r4rgksb4nmmr43fh77bzn2ia2eucduyeafnyd.onion:8001)
+
 ### Clearnet Mirrors
 There are several tor2web services that serve as mirrors in case one of them is unavailable
 
@@ -55,4 +65,5 @@ There are several tor2web services that serve as mirrors in case one of them is
 > [unsafe.testnet.robosats.com](http://unsafe.testnet.robosats.com/) <br/>
 > [unsafe2.testnet.robosats.com](http://unsafe2.testnet.robosats.com/) 
 
+
 {% include improve %}

docs/_pages/docs/02-features/01-private.md

@@ -13,12 +13,12 @@ src: "_pages/docs/02-features/01-private.md"
 <!-- TODO: explain TOR, high entropy avatar, no registration, no identity reuse, lightning onion routing, no logs policy, etc. -->
 RoboSats is absolutely private by default. The main four ingredients are:
 
-1. **No registration at all.** With a single click you will generate a robot avatar: that's all you need. Since no email, phone, username or any sort of input from the user is needed, there is no possible way for the user to make a mistake and doxx himself. Your Robot avatars cannot be linked to you.
+1. **No registration at all.** With a single click you will generate a robot avatar: that's all you need. Since no email, phone, username or any input from the user is needed, there is no possible way to make a mistake and doxx yourself. Your Robot avatars cannot be linked to you.
-2. **Auditable PGP encrypted communication** Every robot has a pair of PGP keys to encrypt your communicaiton end-to-end. RoboSats makes it very easy for you to export your keys and verify for yourself that your communication is private with any other third party app implementing the OpenPGP standard.
+2. **Auditable PGP encrypted communication.** Every robot has a pair of PGP keys to encrypt the communication end-to-end. RoboSats makes it very easy for you to export your keys and [<b>verify for yourself</b>](/docs/pgp-encryption) that your communication is private with any other third party app implementing the OpenPGP standard.
-3. **Tor Network Only.** Your location or IP is never known by the node or your trading peers.
+3. **Tor Network Only.** Your location or IP address is never known to the node or your trading peers.
-4. **One identity -> one trade.** You can (and you are advised to) trade with a different identity every single time, it is convenient and easy. No other exchange has this feature and it is critical for privacy! In RoboSats there is no way for observers to know that several trades have been made by the same user if he used different robot avatars.
+4. **One identity -> one trade.** You can (and you are advised to) trade with a different identity every single time. It is convenient and easy. No other exchange has this feature and **it is critical for privacy!** In RoboSats there is no way for observers to know that several trades have been made by the same user if he used different robot avatars.
 
-The combination of these features makes RoboSats absolutely private, period.
+The combination of these features makes trading in RoboSats as private as it can get.
 
 ## Robot Avatar Generation Pipeline
 <div align="center">

frontend/src/components/EncryptedChat.js

@@ -86,6 +86,13 @@ class Chat extends Component {
           }
           console.log("PEER PUBKEY RECEIVED!!")
           this.setState({peer_pub_key:dataFromServer.message})
+
+          // After receiving the peer pubkey we ask the server for the historic messages if any
+          this.rws.send(JSON.stringify({
+              type: "message",
+              message: `-----SERVE HISTORY-----`,
+              nick: this.props.ur_nick,
+            }))
         } else
 
         // If we receive an encrypted message
@@ -110,7 +117,10 @@ class Chat extends Component {
                 validSignature: decryptedData.validSignature,           
                 userNick: dataFromServer.user_nick,
                 time: dataFromServer.time
-              }],
+              }].sort(function(a,b) {
+                // order the message array by their index (increasing)
+                return a.index - b.index
+              }),
             })
           ));
         }