Repository navigation
Conversation
Page joined-channel metadata in bounded ID groups on its existing WebSocket transport. Refuse incomplete repeated pages so they cannot replace a complete cached channel list. Cover 1,080 memberships with archived rooms, tied timestamps, failed pages, repeated-page refusal, and successful retry. Signed-off-by: rclod <3385524+rclod@users.noreply.github.com>
🔐 Codex Security Review
|
This branch has not been deployed
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
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.
Summary
Joined channels stay visible when archived memberships push an account past the relay’s 1,000-event result limit. Metadata loads in bounded ID groups and pages on the existing WebSocket path; incomplete repeated pages leave the complete cached list intact.
Related issue
None found in searches for “mobile channel metadata pagination” and “mobile channels 1000”.
Testing
just mobile-check, the mobile file-size gate, and agent source review passed; the review’s completeness finding was corrected and closed.Manual check: on an account with more than 1,000 joined rooms, including archived rooms, install the candidate and refresh Conversations. All unarchived joined rooms should remain visible; a failed refresh should retain the previous list.