Multi-device Support #58
Labels
No Label
applications
BLOCKED
bug
design
duplicate
enhancement
fixed?
funding-needed
help wanted
infrastructure
invalid
payments
qubes
question
ready-for-implementation
refactor
spam
tapir-server
testing
tor
wontfix
No Milestone
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch#58
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?
The paper talks about how to achieve this, need a modification to identity key exchanges and a new peer ricochet channel that gets set up to do the syncing.
seems something like a QR code with what is needed to copy the identity or a link and code to allow a new peer to connect to the original identity peer and get that info should be pretty not hard
messages is no problem as they both fetch them
keeping groups subscribed to and peers peered with up to date and synced seems like a challenge tho?
this decision will have tremenous impact on the ux of most cwtch applications and requires careful consideration. i like the paper's idea of establishing proof of shared identity but there are subtleties to how synchronization should be implemented. i'd like to take a stab at designing this, given that it's my thesis topic and all 0:)
Erinn this is all yours