cwtch vs speek ? #409
Labels
No Label
android
arch
backlog
blocked-on-external
bug
bugbash
component/bindings
component/bine
component/connectivity
component/cwtch
component/tapir
component/ui
cwtch-1.14
cwtch-1.15
cwtch-beta-1.1
cwtch-beta-1.10
cwtch-beta-1.11
cwtch-beta-1.12
cwtch-beta-1.13
cwtch-beta-1.2
cwtch-beta-1.3
cwtch-beta-1.4
cwtch-beta-1.5
cwtch-beta-1.5.x
cwtch-beta-1.6
cwtch-beta-1.7
cwtch-beta-1.8
cwtch-beta-1.9
design
duplicate
enhancement
flutter
funding-needed
help wanted
hybrid-groups
in-nightly
in-progress
invalid
ios
linux
mac
need-replication-or-investigation
ops
packaging
post-stable
question
questionable
requires-more-effort-than-we-can-spare
rust
scheduled
stable-blocker
tails
testing-needed
tests
tor
waiting-on-fix-confirmation
waiting-on-new-flutter-feature
whonix
windows
wontfix
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch-ui#409
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
there seems to be a new kid on the block, brushing up the now defunct ricochet project, so basically a very similar project to yours.
Could you have a closer look at the project and see how cwtch stacks up to it ? (I'm by no means connected to the devs)... Thanks.
Links :
https://speek.network/
https://github.com/Speek-App/Speek
Have you tried this with anyone? Just curious about how well it works in practice. :)
not yet, but will next week.
So it sounds mostly like Cwtch core, Cwtch with no experiments enabled, so no groups etc, and no multiple profiles.
looks like the have filesharing from screen shots
Main security difference: This is based on the ricochet-refresh code base (based on the ricochet code base) whic has a non-offline deniable authentication protocol - the security implications of which are non-trivial. In comparison Cwtch sessions are offline-deniable. (See this part of the security handbook: https://docs.openprivacy.ca/cwtch-security-handbook/authentication_protocol.html#cryptographic-properties)
It also looks like they have adapted the QML based UI from the original ricochet, like ricochet refresh. It is very hard to lock QML down especially when introducing new features (it also doesn't translate well to a mobile environment - which is the main reason we stopped building on Qt).
Yeah I responded to them in their reddit thread:
https://old.reddit.com/r/TOR/comments/tkgk41/ricochet_reborn_a_user_friendly_torchat_for/i2hnq35/
tldr; it's ricochet-refresh with a paint-job and some interesting patches on top
Thanks Richard.
I'll be kind and go with dude-bro incompetence, which some might say verges on maliciousness. I read their documentation and just kept having this sneaky feeling that corners had been cut and problems had been glossed over. I would not hesitate to think twice about recommending this app ;)