|
42 | 42 | <a href="#" onclick="hide('popup1')">✖</a> |
43 | 43 | </section> |
44 | 44 | <section id="popup-text"> |
45 | | - <p>A personal CubeSat project, more info in the GitHub repo (it's private for now, though).</p> |
| 45 | + <p> |
| 46 | + A personal CubeSat project, more info in the GitHub repo (it's private for |
| 47 | + now, though). |
| 48 | + </p> |
46 | 49 | </section> |
47 | 50 | </div> |
48 | 51 |
|
|
52 | 55 | <a href="#" onclick="hide('popup2')">✖</a> |
53 | 56 | </section> |
54 | 57 | <section id="popup-text"> |
55 | | - <p>My own OS, not fully from scratch, it's made with an existing bootloader and kernel, but the rest is me.</p> |
| 58 | + <p> |
| 59 | + My own OS, not fully from scratch, it's made with an existing bootloader |
| 60 | + and kernel, but the rest is me. |
| 61 | + </p> |
56 | 62 | </section> |
57 | 63 | </div> |
58 | 64 |
|
59 | 65 | <div class="popup" id="popup3"> |
60 | 66 | <section id="heading"> |
61 | | - <h2>EchoMesh.md</h2> |
| 67 | + <h2>GENESIS.md</h2> |
62 | 68 | <a href="#" onclick="hide('popup3')">✖</a> |
63 | 69 | </section> |
64 | 70 | <section id="popup-text"> |
65 | | - <p>This project is dedicated to helping you build your own true private communication system. It creates a LoRa mesh node system that relays messages privately and securely accross the whole network. It is limited to local communication only, since the LoRa transceivers are of limited range. It utilizes a secure element chip (the ATECC608A) on the user end devices for encryption/decryption and key storage. The nodes in the mesh networks (acting as message relays) do not decrypt or read the messages sent through them, since they don't have a secure element onboard and are specifically designed for only relaying messages.</p> |
| 71 | + <p> |
| 72 | + GENESIS is an autonomous, adaptive, and self-healing AI framework capable |
| 73 | + of dynamically scaling across heterogeneous hardware, self-generating |
| 74 | + functional code, and reconstructing itself after partial system failure. |
| 75 | + It acts as a persistent intelligence capable of operating anywhere from |
| 76 | + massive server clusters to single embedded devices, maintaining identity, |
| 77 | + functionality, and adaptability throughout. |
| 78 | + </p> |
66 | 79 | </section> |
67 | 80 | </div> |
68 | 81 |
|
|
72 | 85 | <a href="#" onclick="hide('popup4')">✖</a> |
73 | 86 | </section> |
74 | 87 | <section id="popup-text"> |
75 | | - <p>Yet another private communication project by me. This one utilizes the existing infrastructure of internet and cell towers, limiting range to cell tower coverage. How this worsk: you take a Cipherlink module that uses NFC and USB for communication with your phone or computer, it also has a secure element onboard (the ATECC608A) used for encryption/decryption & key storage. When you write a message, you tap your module to your phone to encrypt the message, which is then sent to an API server that holds the encrypted messages along with recepient userIDs. The next time the recepient opens the Cipherlink app on their phone, it will fetch the incoming messages from the API server, prompting the user to tap their module to decrypt. Once read, the message gets destroyed and removed from the API server's database. The point is, the decrypted message never touches the internet. It only stays on your device as long as you want it to.</p> |
| 88 | + <p> |
| 89 | + Yet another private communication project by me. This one utilizes the |
| 90 | + existing infrastructure of internet and cell towers, limiting range to |
| 91 | + cell tower coverage. How this worsk: you take a Cipherlink module that |
| 92 | + uses NFC and USB for communication with your phone or computer, it also |
| 93 | + has a secure element onboard (the ATECC608A) used for |
| 94 | + encryption/decryption & key storage. When you write a message, you tap |
| 95 | + your module to your phone to encrypt the message, which is then sent to an |
| 96 | + API server that holds the encrypted messages along with recepient userIDs. |
| 97 | + The next time the recepient opens the Cipherlink app on their phone, it |
| 98 | + will fetch the incoming messages from the API server, prompting the user |
| 99 | + to tap their module to decrypt. Once read, the message gets destroyed and |
| 100 | + removed from the API server's database. The point is, the decrypted |
| 101 | + message never touches the internet. It only stays on your device as long |
| 102 | + as you want it to. |
| 103 | + </p> |
76 | 104 | </section> |
77 | 105 | </div> |
0 commit comments