Date

build-staging/blog/atom.xml

@@ -2,7 +2,7 @@
 <feed xmlns="http://www.w3.org/2005/Atom">
     <id>https://docs.cwtch.im/blog</id>
     <title>Cwtch Development Log</title>
-    <updated>2023-09-20T00:00:00.000Z</updated>
+    <updated>2023-09-27T00:00:00.000Z</updated>
     <generator>https://github.com/jpmonette/feed</generator>
     <link rel="alternate" href="https://docs.cwtch.im/blog"/>
     <subtitle>The latest insight into Cwtch Development and what the Cwtch team are working on</subtitle>
@@ -12,11 +12,11 @@
         <title type="html"><![CDATA[Cwtch 1.13 Stable Release Candidate]]></title>
         <id>https://docs.cwtch.im/blog/cwtch-1-13</id>
         <link href="https://docs.cwtch.im/blog/cwtch-1-13"/>
-        <updated>2023-09-20T00:00:00.000Z</updated>
+        <updated>2023-09-27T00:00:00.000Z</updated>
         <summary type="html"><![CDATA[Cwtch 1.13 (Stable Release Candidate)]]></summary>
         <content type="html"><![CDATA[<p><a href="https://cwtch.im/download" target="_blank" rel="noopener noreferrer">Cwtch 1.13 is now available for download</a>!</p><p>Cwtch is a communication application (and associated libraries) that uses Tor v3 Onion Services to establish surveillance resistant channels between people. Cwtch has been designed to be
 secure, private, and resiliant.</p><p>Cwtch 1.13 is the culmination of the last few years of effort by the Cwtch team, and is the first release that meets our bar to be labelled a <a href="/blog/path-to-cwtch-stable">Cwtch Stable</a> candidate.</p><p>While much more work remains, we are now very confident in the state of the Cwtch library, and the Cwtch UI. We are prepared to make certain commitments regarding peer-to-peer messaging, the UI,
-and experimental interfaces. In this post we will chart the journey that got us to this point, highlight what is in this new release, and talk about our next steps.</p><p><img loading="lazy" src="/assets/images/devlog14-3b9adf25edebfc8385b0b6fcc219d87b.png" width="1004" height="480" class="img_ev3q"></p><h2 class="anchor anchorWithStickyNavbar_LWe7" id="cwtch-stable-and-beyond">Cwtch Stable and Beyond!<a href="#cwtch-stable-and-beyond" class="hash-link" aria-label="Direct link to heading" title="Direct link to heading">​</a></h2><p>Over five years ago, on the 28th June 2018, we published the first official announcement of Cwtch. Throughout 2019 we published various Alpha releases of Cwtch. The original plan was to release a Cwtch Beta in 2020.</p><p>Like so many other projects in 2020, Cwtch Beta was delayed, and towards the end of 2020 it became clear that our original approach to a cross-platform UI was not sustainable long term.</p><p>Finally in June 2021 we launched Cwtch Beta 1.0. We have spent the years since refining beta, adding features, and responding the feedback.</p><p>We have now reached a pivotal moment in Cwtch, one that the team has been working towards for many years. We now believe that Cwtch has reached a point where people can use core features, and enable
+and experimental interfaces. In this post we will chart the journey that got us to this point, highlight what is in this new release, and talk about our next steps.</p><p><img loading="lazy" src="/assets/images/devlog14-3b9adf25edebfc8385b0b6fcc219d87b.png" width="1004" height="480" class="img_ev3q"></p><h2 class="anchor anchorWithStickyNavbar_LWe7" id="cwtch-stable-and-beyond">Cwtch Stable and Beyond!<a href="#cwtch-stable-and-beyond" class="hash-link" aria-label="Direct link to heading" title="Direct link to heading">​</a></h2><p>Over five years ago, on the 28th June 2018, we published the first official announcement of Cwtch. Throughout 2019 we published various Alpha releases of Cwtch. The original plan was to release a Cwtch Beta in 2020.</p><p>Like so many other projects in 2020, Cwtch Beta was delayed, and towards the end of 2020 it became clear that our original approach to a cross-platform UI was not sustainable long term.</p><p>Finally, in June 2021 we launched Cwtch Beta 1.0. We have spent the years since refining beta, adding features, and responding the feedback.</p><p>We have now reached a pivotal moment in Cwtch, one that the team has been working towards for many years. We now believe that Cwtch has reached a point where people can use core features, and enable
 experimental features, with a confidence that any risks are well understood and appropriately mitigated. As such we are dropping the "beta" label.</p><p>Some features, like automatically downloading and displaying images, will always carry some risk - as such these will always remain off-by-default in Cwtch. </p><p>However, if approporate precations are taken (like never accepting conversations from untrusted entities) then these features can be turned on and used without additional considerable risk.</p><p>Further, we believe that the API presented by libCwtch has reached a point where its core design is unlikely to require changes - and as such are prepared to make additional committements to the stability
 of that API going forward. Any new functionality will be provided by new interfaces, or otherwise be handled behind the scenes.</p><p>This is certainly not the end of Cwtch development. We have big plans for the future including the long-anticipated Hybrid Groups
 implementation, a light client for restricted mobile operating systems, a return of the bulletin boards overlay, and much more.</p><p>We want to extend a huge thank you to everyone who helped Cwtch get this far. We could not have done it without you. If you

build-staging/blog/rss.xml

@@ -4,7 +4,7 @@
         <title>Cwtch Development Log</title>
         <link>https://docs.cwtch.im/blog</link>
         <description>The latest insight into Cwtch Development and what the Cwtch team are working on</description>
-        <lastBuildDate>Wed, 20 Sep 2023 00:00:00 GMT</lastBuildDate>
+        <lastBuildDate>Wed, 27 Sep 2023 00:00:00 GMT</lastBuildDate>
         <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
         <generator>https://github.com/jpmonette/feed</generator>
         <language>en</language>
@@ -13,11 +13,11 @@
             <title><![CDATA[Cwtch 1.13 Stable Release Candidate]]></title>
             <link>https://docs.cwtch.im/blog/cwtch-1-13</link>
             <guid>https://docs.cwtch.im/blog/cwtch-1-13</guid>
-            <pubDate>Wed, 20 Sep 2023 00:00:00 GMT</pubDate>
+            <pubDate>Wed, 27 Sep 2023 00:00:00 GMT</pubDate>
             <description><![CDATA[Cwtch 1.13 (Stable Release Candidate)]]></description>
             <content:encoded><![CDATA[<p><a href="https://cwtch.im/download" target="_blank" rel="noopener noreferrer">Cwtch 1.13 is now available for download</a>!</p><p>Cwtch is a communication application (and associated libraries) that uses Tor v3 Onion Services to establish surveillance resistant channels between people. Cwtch has been designed to be
 secure, private, and resiliant.</p><p>Cwtch 1.13 is the culmination of the last few years of effort by the Cwtch team, and is the first release that meets our bar to be labelled a <a href="/blog/path-to-cwtch-stable">Cwtch Stable</a> candidate.</p><p>While much more work remains, we are now very confident in the state of the Cwtch library, and the Cwtch UI. We are prepared to make certain commitments regarding peer-to-peer messaging, the UI,
-and experimental interfaces. In this post we will chart the journey that got us to this point, highlight what is in this new release, and talk about our next steps.</p><p><img loading="lazy" src="/assets/images/devlog14-3b9adf25edebfc8385b0b6fcc219d87b.png" width="1004" height="480" class="img_ev3q"></p><h2 class="anchor anchorWithStickyNavbar_LWe7" id="cwtch-stable-and-beyond">Cwtch Stable and Beyond!<a href="#cwtch-stable-and-beyond" class="hash-link" aria-label="Direct link to heading" title="Direct link to heading">​</a></h2><p>Over five years ago, on the 28th June 2018, we published the first official announcement of Cwtch. Throughout 2019 we published various Alpha releases of Cwtch. The original plan was to release a Cwtch Beta in 2020.</p><p>Like so many other projects in 2020, Cwtch Beta was delayed, and towards the end of 2020 it became clear that our original approach to a cross-platform UI was not sustainable long term.</p><p>Finally in June 2021 we launched Cwtch Beta 1.0. We have spent the years since refining beta, adding features, and responding the feedback.</p><p>We have now reached a pivotal moment in Cwtch, one that the team has been working towards for many years. We now believe that Cwtch has reached a point where people can use core features, and enable
+and experimental interfaces. In this post we will chart the journey that got us to this point, highlight what is in this new release, and talk about our next steps.</p><p><img loading="lazy" src="/assets/images/devlog14-3b9adf25edebfc8385b0b6fcc219d87b.png" width="1004" height="480" class="img_ev3q"></p><h2 class="anchor anchorWithStickyNavbar_LWe7" id="cwtch-stable-and-beyond">Cwtch Stable and Beyond!<a href="#cwtch-stable-and-beyond" class="hash-link" aria-label="Direct link to heading" title="Direct link to heading">​</a></h2><p>Over five years ago, on the 28th June 2018, we published the first official announcement of Cwtch. Throughout 2019 we published various Alpha releases of Cwtch. The original plan was to release a Cwtch Beta in 2020.</p><p>Like so many other projects in 2020, Cwtch Beta was delayed, and towards the end of 2020 it became clear that our original approach to a cross-platform UI was not sustainable long term.</p><p>Finally, in June 2021 we launched Cwtch Beta 1.0. We have spent the years since refining beta, adding features, and responding the feedback.</p><p>We have now reached a pivotal moment in Cwtch, one that the team has been working towards for many years. We now believe that Cwtch has reached a point where people can use core features, and enable
 experimental features, with a confidence that any risks are well understood and appropriately mitigated. As such we are dropping the "beta" label.</p><p>Some features, like automatically downloading and displaying images, will always carry some risk - as such these will always remain off-by-default in Cwtch. </p><p>However, if approporate precations are taken (like never accepting conversations from untrusted entities) then these features can be turned on and used without additional considerable risk.</p><p>Further, we believe that the API presented by libCwtch has reached a point where its core design is unlikely to require changes - and as such are prepared to make additional committements to the stability
 of that API going forward. Any new functionality will be provided by new interfaces, or otherwise be handled behind the scenes.</p><p>This is certainly not the end of Cwtch development. We have big plans for the future including the long-anticipated Hybrid Groups
 implementation, a light client for restricted mobile operating systems, a return of the bulletin boards overlay, and much more.</p><p>We want to extend a huge thank you to everyone who helped Cwtch get this far. We could not have done it without you. If you

build-staging/de/blog/atom.xml

@@ -2,7 +2,7 @@
 <feed xmlns="http://www.w3.org/2005/Atom">
     <id>https://docs.cwtch.im/de/blog</id>
     <title>Cwtch Development Log</title>
-    <updated>2023-09-20T00:00:00.000Z</updated>
+    <updated>2023-09-27T00:00:00.000Z</updated>
     <generator>https://github.com/jpmonette/feed</generator>
     <link rel="alternate" href="https://docs.cwtch.im/de/blog"/>
     <subtitle>The latest insight into Cwtch Development and what the Cwtch team are working on</subtitle>
@@ -12,11 +12,11 @@
         <title type="html"><![CDATA[Cwtch 1.13 Stable Release Candidate]]></title>
         <id>https://docs.cwtch.im/de/blog/cwtch-1-13</id>
         <link href="https://docs.cwtch.im/de/blog/cwtch-1-13"/>
-        <updated>2023-09-20T00:00:00.000Z</updated>
+        <updated>2023-09-27T00:00:00.000Z</updated>
         <summary type="html"><![CDATA[Cwtch 1.13 (Stable Release Candidate)]]></summary>
         <content type="html"><![CDATA[<p><a href="https://cwtch.im/download" target="_blank" rel="noopener noreferrer">Cwtch 1.13 is now available for download</a>!</p><p>Cwtch is a communication application (and associated libraries) that uses Tor v3 Onion Services to establish surveillance resistant channels between people. Cwtch has been designed to be
 secure, private, and resiliant.</p><p>Cwtch 1.13 is the culmination of the last few years of effort by the Cwtch team, and is the first release that meets our bar to be labelled a <a href="/de/blog/path-to-cwtch-stable">Cwtch Stable</a> candidate.</p><p>While much more work remains, we are now very confident in the state of the Cwtch library, and the Cwtch UI. We are prepared to make certain commitments regarding peer-to-peer messaging, the UI,
-and experimental interfaces. In this post we will chart the journey that got us to this point, highlight what is in this new release, and talk about our next steps.</p><p><img loading="lazy" src="/de/assets/images/devlog14-3b9adf25edebfc8385b0b6fcc219d87b.png" width="1004" height="480" class="img_ev3q"></p><h2 class="anchor anchorWithStickyNavbar_LWe7" id="cwtch-stable-and-beyond">Cwtch Stable and Beyond!<a href="#cwtch-stable-and-beyond" class="hash-link" aria-label="Direkter Link zur Überschrift" title="Direkter Link zur Überschrift">​</a></h2><p>Over five years ago, on the 28th June 2018, we published the first official announcement of Cwtch. Throughout 2019 we published various Alpha releases of Cwtch. The original plan was to release a Cwtch Beta in 2020.</p><p>Like so many other projects in 2020, Cwtch Beta was delayed, and towards the end of 2020 it became clear that our original approach to a cross-platform UI was not sustainable long term.</p><p>Finally in June 2021 we launched Cwtch Beta 1.0. We have spent the years since refining beta, adding features, and responding the feedback.</p><p>We have now reached a pivotal moment in Cwtch, one that the team has been working towards for many years. We now believe that Cwtch has reached a point where people can use core features, and enable
+and experimental interfaces. In this post we will chart the journey that got us to this point, highlight what is in this new release, and talk about our next steps.</p><p><img loading="lazy" src="/de/assets/images/devlog14-3b9adf25edebfc8385b0b6fcc219d87b.png" width="1004" height="480" class="img_ev3q"></p><h2 class="anchor anchorWithStickyNavbar_LWe7" id="cwtch-stable-and-beyond">Cwtch Stable and Beyond!<a href="#cwtch-stable-and-beyond" class="hash-link" aria-label="Direkter Link zur Überschrift" title="Direkter Link zur Überschrift">​</a></h2><p>Over five years ago, on the 28th June 2018, we published the first official announcement of Cwtch. Throughout 2019 we published various Alpha releases of Cwtch. The original plan was to release a Cwtch Beta in 2020.</p><p>Like so many other projects in 2020, Cwtch Beta was delayed, and towards the end of 2020 it became clear that our original approach to a cross-platform UI was not sustainable long term.</p><p>Finally, in June 2021 we launched Cwtch Beta 1.0. We have spent the years since refining beta, adding features, and responding the feedback.</p><p>We have now reached a pivotal moment in Cwtch, one that the team has been working towards for many years. We now believe that Cwtch has reached a point where people can use core features, and enable
 experimental features, with a confidence that any risks are well understood and appropriately mitigated. As such we are dropping the "beta" label.</p><p>Some features, like automatically downloading and displaying images, will always carry some risk - as such these will always remain off-by-default in Cwtch. </p><p>However, if approporate precations are taken (like never accepting conversations from untrusted entities) then these features can be turned on and used without additional considerable risk.</p><p>Further, we believe that the API presented by libCwtch has reached a point where its core design is unlikely to require changes - and as such are prepared to make additional committements to the stability
 of that API going forward. Any new functionality will be provided by new interfaces, or otherwise be handled behind the scenes.</p><p>This is certainly not the end of Cwtch development. We have big plans for the future including the long-anticipated Hybrid Groups
 implementation, a light client for restricted mobile operating systems, a return of the bulletin boards overlay, and much more.</p><p>We want to extend a huge thank you to everyone who helped Cwtch get this far. We could not have done it without you. If you