@mischif Yes, we did an initial assessment. We do not currently believe that Veilid meets the bar necessary for us to consider it as an alternative ACN - any privacy properties it has are strictly weaker than those offered by tor v3 onion services - especially when coupled with the offline-deniable auth protocol used by Cwtch.
There is a new Cwtch Nightly available for testing!
This nightly supports configurations necessary to get Cwtch working in environments like Whonix. We are asking for people to test this and report back their experiences so we can improve the documentation / flow.
There are also several new features ready for testing include: a new setting to tell Cwtch to save conversation history by default, and the ability to delete unneeded Cwtch Server information.
This nightly contains a first cut of Conversation Search, in addition to several bug fixes impacting effectiveness of the contact retry plugin when combined with a large contact list, and an unstable network connection. Finally we have made a few tweaks to the font scaling based on feedback.
If you have participated in the development process in any way e.g. protocol design, writing code, UI design, writing tests, testing release candidates, reporting issues, translating the application or documentation, promoting metadata resistant applications or any other meaningful contribution to the Cwtch ecosystem we want to offer you the option to have your name or handle credited in both the source code repository and the application itself.
Due to the nature of Cwtch we have always had a policy of evaluating contributions based on value, and not on identity.
This approach means that, while we do have contributors whose identity is known to us in some way, we have many who we know only by writing style, contribution type, or Cwtch address.
We understand that many people much prefer it this way.
However, as we approach Cwtch Stable, we would like to give all contributors the option of being credited.
As part of our ongoing Cwtch Stable work, we are working towards making all parts of Cwtch reproducible and verifiable.
In this devlog we will talk about how the Cwtch UI are currently built, the changes we have made to Cwtch UI to make future distributions verifiable, and the next steps we will be taking to make all Cwtch builds reproducible.
We plan on releasing a candidate Cwtch Stable release during Summer 2023!
Back in March we extended and updated several goals from our January roadmap that we would have to hit on our way to Cwtch Stable, and the timelines for achieving them. Now that we have reached target date of many of these goals, we can look back and see how work is progressing.
We do have some plans towards that - basically extended how groups work to also cover offline p2p communication.
We've also done some research in the past towards different networking options which would provide some external storage (e.g. https://git.openprivacy.ca/openprivacy/niwl) - but we've yet to find something that covers our risk model to the same standard that our current design does.
For p2p nothing is stored externally at all (except the ephemeral cryptographic material needed to setup a Tor onion circuit).
For group chat Cwtch servers are self hostable, but are also designed to be untrusted and metadata resistant to allow groups to use arbitrary public servers for communication.
🪧 - Profile Attributes and Availability Status options 🌐 - 4 new language options: Japanese, Slovak, Swahili and Swedish! 🧅 - Support for Tails and other Tor-focused Operating Systems
Along with a host of performance improvements and bug fixes.
There is a new Cwtch Nightly available for testing! This nightly will form the base of a 1.12 Beta release candidate.
In addition to previous nightly updates like Profile Attributes, Status, and Tails support nightly features new font scaling settings, new network management code, 3 new languages, and a variety of bug fixes and performance improvements.