Handle fetch when invited to a group on a server peer is already connected to #33
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
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch#33
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?
When a peer connects to a server it automatically triggers a fetch to catch up.
However if a peer is connected to a server and then receives a new group invite, it will not fetch, and not catch up. This should be handled in one of two ways:
Automatically, somewhere in processing an invite we should trigger a fetch if we detect a server connection
expose the fetch api in cwtch peer and allow applications to decide
A 3rd possible approach here is to save undecryptable messages from a server for a given period of time and rerun them whenever there is a new group on a server
semi handled: we do now reconnect and refetch. and these groups are now semi deprecated