One of the larger remaining goals outlined in our Cwtch Stable roadmap update is comprehensive developer documentation. We have recently spent some time writing the foundation for these documents.

In this devlog we will introduce some of them, and outline the next steps. We also have a new nightly Cwtch release available for testing!

We are very interested in getting feedback on these documents, and we encourage anyone who is excited to build a Cwtch Bot, or even an alternative UI, to read them over and reach out to us with comments, questions, and suggestions!

As a reminder, the Open Privacy Research Society have also announced they are want to raise $60,000 in 2023 to help move forward projects like Cwtch. Please help support projects like ours with a one-off donations or recurring support via Patreon.

Two new Cwtch features are now available to test in nightly: Availability Status and Profile Information.

Additionally, we have also published draft guidance on running Cwtch on Tails that we would like volunteers to test and report back on.

The Open Privacy Research Society have also announced they are want to raise $60,000 in 2023 to help move forward projects like Cwtch. Please help support projects like ours with a one-off donations or recurring support via Patreon.

The next large step for the Cwtch project to take is a move from public Beta to Stable – marking a point at which we consider Cwtch to be secure and usable. We have been working hard towards that goal over the last few months.

This post revisits the Cwtch Stable roadmap we introduced at the start of the year, and provides an overview of the next steps on our journey towards Cwtch Stable.

Cwtch 1.11 is now available for download!

Cwtch 1.11 is the culmination of the last few months of effort by the Cwtch team, and includes many foundational changes that pave the way for Cwtch Stable including new reproducible and automatically generated bindings, as well as support for two new languages (Slovak and Korean), in addition to several performance improvements and bug fixes.

One of the main streams of work in the lead up to Cwtch Stable has been improving all aspects of Cwtch Documentation. In this development log we will highlight some of the major updates over the last few weeks.

Last time we looked at autobindings we mentioned that one of the next steps was introducing support for Application-level experiments. In this development log we will explore what application-level experiments are (technically), and how we added (optional) autobindings support for them.

The C-bindings for Cwtch evolved as part of Cwtch UI development. After two years of prototyping, development, new features, and revisiting first-implementations we have reached the point where we have a good understanding of what the bindings need to do, and how they should do it. To that end we have produced a first-cut of a workflow to automatically generate these bindings: cwtch-autobindings.

This this development log we will introduced autobindings, the motivation behind them, and how we plan to use them on the path to Cwtch Stable.

In this development log, we investigate some text-based UI bugs encountered by Fuzzbot, add more automated UI tests to the pipeline, and announce a new release of the Cwtchbot library.

In this development log, we continue our previous work on reproducible Cwtch bindings, uncovering the final few sources of variation between our Repliqate scripts and our docker/drone builds, leading to fully reproducible builds for Cwtch Android bindings!

We first introduced UI tests last January. At the time we had developed a suite of UI tests that could be run manually in a development environment. However, we faced a number of issues consistently running these tests in our automated pipelines.

One of the main threads of work that needs to be complete early in the Cwtch Stable roadmap is integrating UI tests into our CI pipelines, in addition to expanding their scope. Now that Flutter 3 has stabilized desktop support, and we have invested effort in improving Cwtch performance, it is time to ensure these tests are running on every build.