<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Components on freetheinter.net</title>
    <link>https://freetheinter.net/posts/components/</link>
    <description>Recent content in Components on freetheinter.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 05 Dec 2022 15:38:56 -0500</lastBuildDate><atom:link href="https://freetheinter.net/posts/components/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Project Bootstrap</title>
      <link>https://freetheinter.net/posts/components/bootstrap/</link>
      <pubDate>Sun, 11 Dec 2022 00:00:00 +0000</pubDate>
      
      <guid>https://freetheinter.net/posts/components/bootstrap/</guid>
      <description>To get started, we need to decide what tools we will use. The first experiments will be focused on particular parts of the system to prove that current plans are viable.
 simulate node discovery - now many, and of what type of nodes are required for normal communication to be feasible mock up consensus method creation: format, interface, sharing. it might be fun to see if LLM agents can talk to each other using various consensus methods and get good results.</description>
    </item>
    
    <item>
      <title>Clustering</title>
      <link>https://freetheinter.net/posts/components/clustering/</link>
      <pubDate>Sun, 11 Dec 2022 00:00:00 +0000</pubDate>
      
      <guid>https://freetheinter.net/posts/components/clustering/</guid>
      <description>Functional goals:
 Given a list of IP addresses, maintain communicative cluster capable of sending and receiving messages between members Maximize ability to maintain cluster with various commonplace network conditions:  dynamic IP address periodic temporary connection loss long term connection loss hardware failure   Ensure attack surface is minimized to third parties  nodes must allow connection from the internet due to changing IP addresses randomly calculated rendezvous windows    </description>
    </item>
    
    <item>
      <title>Key Management</title>
      <link>https://freetheinter.net/posts/components/key-management/</link>
      <pubDate>Fri, 09 Dec 2022 00:00:00 +0000</pubDate>
      
      <guid>https://freetheinter.net/posts/components/key-management/</guid>
      <description>Cryptographic keys are used at every interface - between nodes to establish identities, to decrypt received data, to encrypt data before transmission, to encrypt data before storage, to decrypt data read from storage, etc.
It&amp;rsquo;s critical that all other components are properly structured around safe key management, so this will be one of the first components developed.
Key generation Every user generates a root key that serves as the ultimate recovery key, which is used to bootstrap their cluster.</description>
    </item>
    
    <item>
      <title>Messaging</title>
      <link>https://freetheinter.net/posts/components/messaging/</link>
      <pubDate>Sun, 11 Dec 2022 00:00:00 +0000</pubDate>
      
      <guid>https://freetheinter.net/posts/components/messaging/</guid>
      <description>Simple messaging layer, which can be built upon for more complex communication schemes.
 sharing of simple messages, with references to other messages creation of conversation groups group message exchange between clusters  </description>
    </item>
    
    <item>
      <title>Data</title>
      <link>https://freetheinter.net/posts/components/data/</link>
      <pubDate>Sun, 11 Dec 2022 00:00:00 +0000</pubDate>
      
      <guid>https://freetheinter.net/posts/components/data/</guid>
      <description>Data layer - persistent storage duplicated between one&amp;rsquo;s own nodes and some nodes of trusted friends.
 stores messages always encrypted at rest combinatoric streaming engine requires compromise of multiple nodes to access archived data. combine stream of two remote nodes to construct messages in memory locally redundant - any two nodes can be used to recover all data relay, sender, receiver roles trusted friends can serve relay role only one sender at a time fully encrypted on nodes of trusted people you know  </description>
    </item>
    
    <item>
      <title>Consensus Engine</title>
      <link>https://freetheinter.net/posts/components/consensus/</link>
      <pubDate>Fri, 01 Jul 2022 00:00:00 +0000</pubDate>
      
      <guid>https://freetheinter.net/posts/components/consensus/</guid>
      <description>&lt;p&gt;If we&amp;rsquo;re not going to rely on third parties to tell us what to think, we
need to build a system to help us arrive at consensus without them.&lt;/p&gt;
&lt;p&gt;The overall approach here is for small groups of individuals to participate
in a process that allows them to achieve local consensus. With so many
independent consensus decisions being made, and with no ability to know the
results from any of them, mass propaganda will become much less effective.&lt;/p&gt;
&lt;p&gt;Over time people will accumulate a wealth of consensus results that distill
the careful thoughts and discussions of those that they trust the most.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
