feat: added latex generation

content/articles/hyperconnect/a4.tex.yml

@@ -0,0 +1,3 @@
+data: 
+  structure: ./index.yml
+generator: article

content/articles/hyperconnect/authentication.md

@@ -0,0 +1,10 @@
+we will need a way for our devices to identify with one and another, and since we might not have access to any particular node in the system at the time of authentication, this needs to work without a trusted third party at the time of connection.
+
+The best way I can think of here is to use a signing authority.
+
+Our authentication will consist of two main concept; a passport and a passport authority.
+
+Each device will create a passport, which contains some various information but most important is a public key coresponding to a private key stored on the device. A device then has to go through a "claim process" where a user assign it as their device. this happens by that uses passport authority uses a private key to sign the device's passport, and giving it the authorities public key.
+
+Now our device has a signed passport, and the oublic key of the authority, so when two devices needs to connect they can now go through an authentication process to verify each others passport. If both devices verifies the other device's passport as valid the connection can be established.
+

content/articles/hyperconnect/definition.md

@@ -0,0 +1,6 @@
+What does hyper-connectivity mean? Well, a common interpretation is to be available on multiple different channels. We al know that one guy whom you contact on text message only to get a reply on Signal, just to get a follow up using email.
+
+Then what does it mean for devices to be hyper connected? In this case it means using all available forms of communication in order to get data from one place to another, which is what this article is about.
+
+Today, when a developer want a system to send data from one place to another he needs to pick a transport protocol such as http. Then connect
+

content/articles/hyperconnect/index.yml

@@ -0,0 +1,25 @@
+title: Creating a hyper connectivity framework
+parts:
+  - title: definition
+    file: definition.md
+  - title: reason
+  - title: target
+  - title: design
+    notes: |
+      onion based stream
+      4 way streams
+  - title: connection
+    notes: |
+      peerjs, tcp, ble(?)
+      session id
+  - title: reconnection
+  - title: authentication
+    file: authentication.md
+    notes: |
+      passport service
+  - title: security
+    notes: |
+      diff-hellman
+  - title: transport-nodes
+  - title: proof-of-concept
+  - title: conclusion