From 0527e4e1372c1ee3ebc2c4af1b9e1243422bca2e Mon Sep 17 00:00:00 2001 From: Sarah Jamie Lewis Date: Thu, 12 Jan 2023 11:55:42 -0800 Subject: [PATCH] More links --- blog/2023-01-13-cwtch-stable-api-design.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blog/2023-01-13-cwtch-stable-api-design.md b/blog/2023-01-13-cwtch-stable-api-design.md index 7cf205df..031103a4 100644 --- a/blog/2023-01-13-cwtch-stable-api-design.md +++ b/blog/2023-01-13-cwtch-stable-api-design.md @@ -16,9 +16,9 @@ Cwtch grew out of a prototype and has been allowed to evolve over time as we dis As we grew, we inserted experimental functionality where it was most accessible to place - not, necessarily, where it was ultimately best to place it - this has led to some degree of overlapping, and inconsistent, responsibilities across Cwtch software packages. -As we move out of Beta and towards Cwtch Stable it is time to revisit these previous decisions with both the benefit of hindsight, and years of real-world testing. +As we move out of Beta and [towards Cwtch Stable](https://docs.cwtch.im/blog/path-to-cwtch-stable) it is time to revisit these previous decisions with both the benefit of hindsight, and years of real-world testing. -In this post we will outline planned new changes to the Cwtch API that realign responsibilities, and explicitly enable new functionality to be built in a modular, controlled, and secure way. In preparation [for Cwtch Stable](https://docs.cwtch.im/blog/path-to-cwtch-stable), and beyond. +In this post we will outline our plans for the Cwtch API that realign responsibilities, and explicitly enable new functionality to be built in a modular, controlled, and secure way. In preparation for Cwtch Stable, and beyond. ![](/img/devlog2.png)