Deployed 54b79e0 with MkDocs version: 1.6.1

Author: github-actions[bot]

Protocol Specifications/core/index.html

@@ -1291,21 +1291,6 @@
     </span>
   </a>
 
-    <nav class="md-nav" aria-label="7.3 Moving data">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#731-content-addressing-with-relative-roots" class="md-nav__link">
-    <span class="md-ellipsis">
-      7.3.1 Content Addressing with relative roots
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
 
           <li class="md-nav__item">
@@ -2585,21 +2570,6 @@
     </span>
   </a>
 
-    <nav class="md-nav" aria-label="7.3 Moving data">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#731-content-addressing-with-relative-roots" class="md-nav__link">
-    <span class="md-ellipsis">
-      7.3.1 Content Addressing with relative roots
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
 
           <li class="md-nav__item">
@@ -2806,7 +2776,6 @@ <h1 id="polyproto-specification">polyproto Specification<a class="headerlink" hr
 </ul>
 </li>
 <li><a href="#73-moving-data">7.3 Moving data</a></li>
-<li><a href="#731-content-addressing-with-relative-roots">7.3.1 Content Addressing with relative roots</a></li>
 <li><a href="#74-challenges-and-trust">7.4 Challenges and trust</a></li>
 </ul>
 </li>
@@ -3385,9 +3354,6 @@ <h4 id="614-early-revocation-of-id-certs">6.1.4 Early revocation of ID-Certs<a c
 <p>The above paragraph is true for both foreign and home servers. The API routes associated with
 revoking an ID-Cert are the same regardless of the server type.</p>
 </div>
-<p>TODO: Write about identifier changing and how to handle that across servers
-TODO: Perhaps recommend never using more than a specified number of certificates at once to make
-      re-signing easier</p>
 <h3 id="62-actor-identity-keys-and-message-signing">6.2 Actor identity keys and message signing<a class="headerlink" href="#62-actor-identity-keys-and-message-signing" title="Permanent link">&para;</a></h3>
 <p>As briefly mentioned section <a href="#4-federated-identity">#4</a>, users must hold on to an identity key pair
 at all times. This key pair is used to represent an actor's identity and to verify
@@ -3831,35 +3797,6 @@ <h3 id="73-moving-data">7.3 Moving data<a class="headerlink" href="#73-moving-da
 <p><em>Fig. 8: Sequence diagram depicting the data moving process.</em></p>
 <p>How this process is implemented is up to P2 extensions to define. The above steps are only a
 guideline. The API routes for data export and import are documented in the API documentation.</p>
-<h4 id="731-content-addressing-with-relative-roots">7.3.1 Content Addressing with relative roots<a class="headerlink" href="#731-content-addressing-with-relative-roots" title="Permanent link">&para;</a></h4>
-<p>Moving data from one server to another might break references to this data. To prevent this as much
-as possible, content addressing with relative roots is recommended for data behind an additional
-layer of indirection.</p>
-<div class="admonition example">
-<p class="admonition-title">Example</p>
-<p>In a chat service, a user might have posted a message containing a picture. In this example, the
-picture is stored on the user's home server, which is not necessarily the same server as the
-chat service. If the user moves their account to another server, the picture might not be
-accessible anymore.</p>
-</div>
-<p>Content addressing with relative roots aids in preventing this issue. Instead of referring to
-the absolute URL of the content, the server processing the content generates a unique identifier.
-This identifier can be used to retrieve the content from the server. Most importantly, this
-identifier does not change when the content is moved to another server. If the base domain of the
-new server is known, the identifier can be used to retrieve the content from the new server.
-The "relative root" is the base domain of the server, which is used to retrieve the content.</p>
-<p>The uniqueness constraint of the identifier is important. If a collision occurs when trying to
-move the content to another server, the content cannot be migrated in a way that preserves the
-references to it. One way to ensure the uniqueness of the identifier is to use a hash function on the
-content itself. Combining this has with a cryptographically strong nonce, then hashing the result of
-concatenating the nonce and the hash of the content should yield a unique identifier.</p>
-<p>The API route for content addressing with relative roots is formatted as follows:</p>
-<p><code>&lt;server_url&gt;/.p2/core/content/&lt;content_id&gt;</code></p>
-<p>The API route for content addressing with relative roots is documented more thoroughly in the API
-documentation.</p>
-<p>Servers with no need for content addressing with relative roots can select to not implement this
-feature. Servers not implementing this feature should return a <code>404 Not Found</code> status code when
-the API route is accessed. Clients should expect finding servers not implementing this feature.</p>
 <h3 id="74-challenges-and-trust">7.4 Challenges and trust<a class="headerlink" href="#74-challenges-and-trust" title="Permanent link">&para;</a></h3>
 <p>Changing the publicly visible ownership of actor data requires the chain of trust to be maintained.
 If an "old" account wants to change the publicly visible ownership of its data, the "old"
@@ -4091,7 +4028,7 @@ <h3 id="911-changing-a-primary-service-provider">9.1.1 Changing a primary servic
     <span class="md-icon" title="Last update">
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg>
     </span>
-    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-timeago"><span class="timeago" datetime="2024-09-25T20:33:59+00:00" locale="en"></span></span><span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_date">2024-09-25</span>
+    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-timeago"><span class="timeago" datetime="2024-08-15T22:03:45+00:00" locale="en"></span></span><span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_date">2024-08-15</span>
   </span>
 
 

feed_rss_created.xml

@@ -1 +1 @@
-<?xml version="1.0" encoding="UTF-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel><title>Polyphony</title><docs>https://github.com/polyphony-chat/docs</docs><language>en</language> <pubDate>Wed, 25 Sep 2024 20:34:19 -0000</pubDate> <lastBuildDate>Wed, 25 Sep 2024 20:34:19 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.15.0</generator> <item> <title>polyproto extensions</title> <author>bitfl0wer</author> <category>polyproto</category> <description>&lt;h1&gt;polyproto extensions.&lt;/h1&gt;&lt;p&gt;polyproto is a new federation protocol. Its main focus is enabling seamless participation of oneactor on many different servers. The core specification lacks routes for sending any sort of usergenerated data anywhere, though. What is up with that?&lt;/p&gt;</description> <pubDate>Sat, 01 Jun 2024 00:00:00 +0000</pubDate> </item> <item> <title>Work on polyproto and a &#34;vacation&#34; ⛱️</title> <author>bitfl0wer</author> <category>polyproto</category> <category>updates</category> <description>&lt;h1&gt;Work on polyproto and taking a break&lt;/h1&gt;&lt;p&gt;In this little update post I write about what I&#39;ve done in the last couple of weeks alongside talking about taking just a little break(don&#39;t worry, y&#39;all are not getting rid of me!)&lt;/p&gt;</description> <pubDate>Wed, 06 Mar 2024 00:00:00 +0000</pubDate> </item> <item> <title>X.509 in polyproto</title> <author>bitfl0wer</author> <category>X.509</category> <category>polyproto</category> <description>&lt;h1&gt;Certificates, please: X.509 in polyproto&lt;/h1&gt;&lt;p&gt;This blog post covers a bit about how and why X.509 is used in polyproto, and how we try to makethe process of implementing your own server and incorporating it into an existing network a littleeasier.&lt;/p&gt;</description> <pubDate>Mon, 19 Feb 2024 00:00:00 +0000</pubDate> </item> <item> <title>Account migration in polyproto</title> <author>bitfl0wer</author> <category>polyproto</category> <description>&lt;p&gt;Account migration is an important and difficult thing to get right in federated systems. In this blogpost, I will outline how I imagine account migration to work in polyproto, and what benefits thisapproach brings.&lt;/p&gt;</description> <pubDate>Wed, 07 Feb 2024 00:00:00 +0000</pubDate> </item> <item> <title>Porting chorus to WebAssembly + Client Update</title> <author>bitfl0wer</author> <category>chorus</category> <category>polyphony</category> <category>updates</category> <description>&lt;h1&gt;Porting chorus to WebAssembly + Client Update&lt;/h1&gt;&lt;p&gt;What the current state of GUI libraries in Rust means for Polyphony and chorus, and why we are porting chorus to WebAssembly.&lt;/p&gt;</description> <pubDate>Thu, 23 Nov 2023 00:00:00 +0000</pubDate> </item> <item> <title>Getting started with the Polyphony Client</title> <author>bitfl0wer</author> <category>polyphony</category> <category>updates</category> <description>&lt;h1&gt;Getting started with the Polyphony Client&lt;/h1&gt;</description> <pubDate>Sat, 02 Sep 2023 00:00:00 +0000</pubDate> </item> <item> <title>chorus Alpha 0.1.0</title> <author>bitfl0wer</author> <category>chorus</category> <category>updates</category> <description>&lt;h1&gt;chorus Alpha 0.1.0&lt;/h1&gt;&lt;p&gt;We are alpha now! As of 2 days ago, the first Alpha of Chorus, Version 0.1.0, has been released for everyone to look at and use on crates.io!&lt;/p&gt;</description> <pubDate>Tue, 29 Aug 2023 00:00:00 +0000</pubDate> </item> <item> <title>Self-updating structs, moving blog posts to GitHub, and more!</title> <author>bitfl0wer</author> <category>chorus</category> <category>updates</category> <description>&lt;h1&gt;Self-updating structs, moving blog posts to GitHub, and more!&lt;/h1&gt;&lt;p&gt;Introducing self-updating structs, explaining how they work, and what they are good for. Also, moving blog posts to GitHub, and other improvements.&lt;/p&gt;</description> <pubDate>Thu, 17 Aug 2023 00:00:00 +0000</pubDate> </item> </channel></rss>
+<?xml version="1.0" encoding="UTF-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel><title>Polyphony</title><docs>https://github.com/polyphony-chat/docs</docs><language>en</language> <pubDate>Thu, 26 Sep 2024 08:34:43 -0000</pubDate> <lastBuildDate>Thu, 26 Sep 2024 08:34:43 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.15.0</generator> <item> <title>polyproto extensions</title> <author>bitfl0wer</author> <category>polyproto</category> <description>&lt;h1&gt;polyproto extensions.&lt;/h1&gt;&lt;p&gt;polyproto is a new federation protocol. Its main focus is enabling seamless participation of oneactor on many different servers. The core specification lacks routes for sending any sort of usergenerated data anywhere, though. What is up with that?&lt;/p&gt;</description> <pubDate>Sat, 01 Jun 2024 00:00:00 +0000</pubDate> </item> <item> <title>Work on polyproto and a &#34;vacation&#34; ⛱️</title> <author>bitfl0wer</author> <category>polyproto</category> <category>updates</category> <description>&lt;h1&gt;Work on polyproto and taking a break&lt;/h1&gt;&lt;p&gt;In this little update post I write about what I&#39;ve done in the last couple of weeks alongside talking about taking just a little break(don&#39;t worry, y&#39;all are not getting rid of me!)&lt;/p&gt;</description> <pubDate>Wed, 06 Mar 2024 00:00:00 +0000</pubDate> </item> <item> <title>X.509 in polyproto</title> <author>bitfl0wer</author> <category>X.509</category> <category>polyproto</category> <description>&lt;h1&gt;Certificates, please: X.509 in polyproto&lt;/h1&gt;&lt;p&gt;This blog post covers a bit about how and why X.509 is used in polyproto, and how we try to makethe process of implementing your own server and incorporating it into an existing network a littleeasier.&lt;/p&gt;</description> <pubDate>Mon, 19 Feb 2024 00:00:00 +0000</pubDate> </item> <item> <title>Account migration in polyproto</title> <author>bitfl0wer</author> <category>polyproto</category> <description>&lt;p&gt;Account migration is an important and difficult thing to get right in federated systems. In this blogpost, I will outline how I imagine account migration to work in polyproto, and what benefits thisapproach brings.&lt;/p&gt;</description> <pubDate>Wed, 07 Feb 2024 00:00:00 +0000</pubDate> </item> <item> <title>Porting chorus to WebAssembly + Client Update</title> <author>bitfl0wer</author> <category>chorus</category> <category>polyphony</category> <category>updates</category> <description>&lt;h1&gt;Porting chorus to WebAssembly + Client Update&lt;/h1&gt;&lt;p&gt;What the current state of GUI libraries in Rust means for Polyphony and chorus, and why we are porting chorus to WebAssembly.&lt;/p&gt;</description> <pubDate>Thu, 23 Nov 2023 00:00:00 +0000</pubDate> </item> <item> <title>Getting started with the Polyphony Client</title> <author>bitfl0wer</author> <category>polyphony</category> <category>updates</category> <description>&lt;h1&gt;Getting started with the Polyphony Client&lt;/h1&gt;</description> <pubDate>Sat, 02 Sep 2023 00:00:00 +0000</pubDate> </item> <item> <title>chorus Alpha 0.1.0</title> <author>bitfl0wer</author> <category>chorus</category> <category>updates</category> <description>&lt;h1&gt;chorus Alpha 0.1.0&lt;/h1&gt;&lt;p&gt;We are alpha now! As of 2 days ago, the first Alpha of Chorus, Version 0.1.0, has been released for everyone to look at and use on crates.io!&lt;/p&gt;</description> <pubDate>Tue, 29 Aug 2023 00:00:00 +0000</pubDate> </item> <item> <title>Self-updating structs, moving blog posts to GitHub, and more!</title> <author>bitfl0wer</author> <category>chorus</category> <category>updates</category> <description>&lt;h1&gt;Self-updating structs, moving blog posts to GitHub, and more!&lt;/h1&gt;&lt;p&gt;Introducing self-updating structs, explaining how they work, and what they are good for. Also, moving blog posts to GitHub, and other improvements.&lt;/p&gt;</description> <pubDate>Thu, 17 Aug 2023 00:00:00 +0000</pubDate> </item> </channel></rss>