forked from cwtch.im/docs.cwtch.im
More links
This commit is contained in:
parent
bc5937695e
commit
0527e4e137
|
@ -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)
|
||||
|
||||
|
|
Loading…
Reference in New Issue