From 3929aff9a2ebe0dc4d3a56d13638732fdfdef6f1 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Mon, 26 Aug 2024 10:14:34 +0000
Subject: [PATCH] Deployed 8475069 with MkDocs version: 1.6.0

---
 feed_rss_created.xml | 2 +-
 feed_rss_updated.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/feed_rss_created.xml b/feed_rss_created.xml
index af4eb4e3..852ab7ba 100644
--- a/feed_rss_created.xml
+++ b/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>Mon, 26 Aug 2024 10:14:10 -0000</pubDate> <lastBuildDate>Mon, 26 Aug 2024 10:14:10 -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>
\ No newline at end of file
+<?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>Mon, 26 Aug 2024 10:14:32 -0000</pubDate> <lastBuildDate>Mon, 26 Aug 2024 10:14:32 -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>
\ No newline at end of file
diff --git a/feed_rss_updated.xml b/feed_rss_updated.xml
index 60266f36..16493944 100644
--- a/feed_rss_updated.xml
+++ b/feed_rss_updated.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>Mon, 26 Aug 2024 10:14:10 -0000</pubDate> <lastBuildDate>Mon, 26 Aug 2024 10:14:10 -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 09:17:57 +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>Thu, 07 Mar 2024 21:36:03 +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>Wed, 06 Mar 2024 22:42:28 +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>Wed, 06 Mar 2024 22:42:28 +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>Wed, 06 Mar 2024 22:42:28 +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>Wed, 06 Mar 2024 22:42:28 +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>Tue, 20 Feb 2024 10:10:12 +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>Thu, 08 Feb 2024 16:39:01 +0000</pubDate> </item> </channel></rss>
\ No newline at end of file
+<?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>Mon, 26 Aug 2024 10:14:32 -0000</pubDate> <lastBuildDate>Mon, 26 Aug 2024 10:14:32 -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 09:17:57 +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>Thu, 07 Mar 2024 21:36:03 +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>Wed, 06 Mar 2024 22:42:28 +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>Wed, 06 Mar 2024 22:42:28 +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>Wed, 06 Mar 2024 22:42:28 +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>Wed, 06 Mar 2024 22:42:28 +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>Tue, 20 Feb 2024 10:10:12 +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>Thu, 08 Feb 2024 16:39:01 +0000</pubDate> </item> </channel></rss>
\ No newline at end of file