Repository navigation
Keep failed text sends so their bubble and Retry survive a restart - #85
Merged
Merged
Conversation
Ocnrb
commented
Oct 5, 2026
Ocnrb
commented
Member
- A failed send lived only in memory, so a restart lost the message and its Retry
- Kept per conversation in encrypted prefs scoped to the account, newest 20, device-local: never in the sync or the backup, or every device of the account would offer a Retry for the same message
- Kept per conversation in encrypted prefs scoped to the account, newest 20, and never in the sync or the backup: a Retry belongs to the device that tried - Back on the timeline when the channel or DM opens; a sent Retry, our own copy arriving, a delete or leaving the conversation drops it Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.