We would love to be on fdroid, and we have done a lot of work to basically get Cwtch ready, but we need volunteer effort to push it past the finish line.
Ah we suspect this might be an encrypted profile, which requires the password entered in the "current password" field to delete - it looks like that field is cut off in the screenshot - which would display a warning underneath it in that case?
Cwtch is a privacy-only p2p messenger based on @torproject v3 onion services.
By privacy-only, we mean privacy-only.
Cwtch provides complete control over what features (groups / file sharing / image previews etc.) are enabled, and every feature which alters the default privacy risk model is explicitly opt-in.
We believe that this level of control is what is it takes to actually take your privacy seriously.
This release features new alpha support for Managed Groups i.e. peer-hosed Cwtch groups, which use the p2p Cwtch protocol rather than the legacy groups.
We have also fixed Cwtch on newer version of Tails, improved the UX around importing unencrypted profiles, and improved rendering of markdown formatting and image previews.
We are also trailing two new release formats: a signed windows installer, and .deb package.
I also tend to bite my tongue these days because the space is filled with messengers who make similar promises regarding metadata resistance while also offering real-time video chat and transparent offline messaging - feats which, if true, I would hail as academic breakthroughs.
This fix mainly addresses several long standing issues with Android, but also contains an important update to libCwtch which prevented some contacts from exchanging profile images.
🎨 Custom Theme Support! It is now possible to load new themes into the Cwtch UI and customize it to your liking 🖌️ Additionally, this release contains many small UI fixes and accessibility improvements 🐞 Many small bug fixes including improvements to file sharing on Android, and support for newer versions of Tails.
Awesome - we know this UI is pretty clunky and are actively working on making it better!
For future reference it is also possible to run a standalone server (https://git.openprivacy.ca/cwtch.im/server/) and get a server key that way (some groups also host public cwtch servers and publish details online).
hi! It's a little unclear, and we are currently revamping this, but you can past a server key / group invite into the "Add Contact / Invitation / Key Bundle" input box.
Last week, we mentioned that enhanced permissions are essential to implementing many of the aspects of the new hybrid groups design.
In this small devlog we introduce the new enhanced permissions api in libCwtch, explain why it is needed, and how future releases of Cwtch will manage conversation-level permissions.
Anonymity is an explicit goal of Cwtch, as such the protocols have been designed to provide against that risk model (See the Cwtch handbook: https://docs.cwtch.im/security/intro)
Seems like there might be some confusion in the UI or documentation? While only one profile can be interacted with at a time (as in on screen at a time), the other profiles can be active, and will receive messages etc.