keybase / keybase/keybase-issues
messages sent when offline should eventually be delivered (reliably)
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
This is coming from the perspective of considering KeyBase a possible future contender to Whatsapp/Signal.
One of the key features of those, is that sending a message is "reliable". What I mean by reliable is that you can trust that the app will eventually deliver the message barring non-transient conditions (e.g. phone explodes). This is contrast to the current KeyBase behavior where the client eventually gives up and presents an error message and requires user input to cancel/resend.
For me and at least some I talk to, this is a very big deal to usability. There are few things more frustrating than having issues trying to send someone a message while temporarily rushing between point A to point B without connectivity or similar and not have to worry about monitoring whether messages get sent.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the Keybase client's offline message-send and retry flow, then determine how transient connectivity is handled. Done means messages sent while offline are eventually delivered without requiring the user to monitor, cancel, or resend them.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100