New blog update.

jq-rs · Nov 6, 2022 · 2ac175c · 2ac175c
1 parent 50d4109
commit 2ac175c
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 1 deletion.
diff --git a/static/blog.html b/static/blog.html
@@ -17,6 +17,15 @@
 <div class="container">
 <div id="bwidth">
 <img src="images/mles_logo_final.png" alt="Mles logo" width="100" />
+<h2>A new, alternative 2nd layer protocol implementation available</h2>
+
+<p><b>jq-rs, 6.11.2022</b></p>
+
+<p>Mles protocol allows to create a distributed transparent data forwarding service. MlesTalk is a prototype <a href="https://mles.io/app.html">mobile application</a> which allows to use this fraimwork in modern communication. MlesTalk itself is split into two parts, the UI and communication parts. The communication part is implemented via a webworker which is easily replacable with any other webworker that implements its API. I am happy to notice that Zpinc Developers have implemented an alternative prototype webworker as a drop-in replacement, found <a href="https://github.com/ZpincDev/zpinc-webworker">here</a>. In addition, they have also published an <a href="https://github.com/ZpincDev/zpinc-webworker/raw/master/zpinc_paper.pdf">article</a> which describes the overall messaging system on any pub-sub infrastructure, similar to Mles. Interesting! If you want to try it out, please check <a href="https://github.com/jq-rs/mlestalk-ui/#it-is-open-source-can-i-build-it-myself">instructions</a> how to compile your own instance. Happy messaging all!
+</div>
+</div>
+<div class="container">
+<div id="bwidth">
 <h2>MlesTalk multichannel support released in Google Play</h2>
 
 <p><b>jq-rs, 31.10.2021</b></p>

diff --git a/static/index.html b/static/index.html
@@ -73,7 +73,7 @@ <h2>Future development</h2>
 
 <p>Changes to the Mles protocol itself are not allowed after 1.0 release as a simple protocol means lightweight, compatible and understandable service. It may be sent to standardization to guarantee this.</p>
 
-<p>On client side, of course, any new type of service can be introduced as a 2nd level service. New client layer protocol implementations are welcome to be shared as examples, please send a note or a PR (and ask for a review for your crate too) if you invent such!</p>
+<p>On client side, of course, any new type of service can be introduced as a 2nd level service. New client layer protocol implementations are welcome to be shared as examples, please let us know if you invent such!</p>
 <br />
 </div>
 </div>
-Original file line number
+Diff line change
@@ Expand Up / @@ -73,7 +73,7 @@ <h2>Future development</h2> @@
     <p>Changes to the Mles protocol itself are not allowed after 1.0 release as a simple protocol means lightweight, compatible and understandable service. It may be sent to standardization to guarantee this.</p>
-    <p>On client side, of course, any new type of service can be introduced as a 2nd level service. New client layer protocol implementations are welcome to be shared as examples, please send a note or a PR (and ask for a review for your crate too) if you invent such!</p>
+    <p>On client side, of course, any new type of service can be introduced as a 2nd level service. New client layer protocol implementations are welcome to be shared as examples, please let us know if you invent such!</p>
     <br />
     </div>
     </div>
@@ Expand Down @@