Issue 1671: Bluesky reply duplication#1800
Merged
Tlaster merged 2 commits intoDimensionDev:masterfrom Feb 16, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes the Bluesky reply duplication issue where posts in a reply chain were shown both as standalone posts and as part of the chain. The fix ensures that only the leaf post of a reply chain is displayed, with all parent posts shown as part of that chain.
Changes:
- Modified the database cache mapper to build complete parent chains and filter out intermediate posts that appear as parents of other posts in the feed
- Updated the UI mapper to display all parents in a chain (reversed for chronological order) instead of only the immediate parent
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| shared/src/commonMain/kotlin/dev/dimension/flare/data/database/cache/mapper/Bluesky.kt | Refactored toDbPagingTimeline to build parent chain maps, identify duplicate parent posts, and filter them out; extracted processBlueskyFeedItem helper function |
| shared/src/commonMain/kotlin/dev/dimension/flare/ui/model/mapper/Bluesky.kt | Modified parent rendering to display all parents in the reference chain (reversed) instead of only the first parent |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
shared/src/commonMain/kotlin/dev/dimension/flare/data/database/cache/mapper/Bluesky.kt
Show resolved
Hide resolved
Tlaster
approved these changes
Feb 16, 2026
Contributor
Tlaster
left a comment
There was a problem hiding this comment.
I think there's still room for improvement, but not right now. LGTM!
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.
Issue: #1671
This addresses the case in the linked issue. (Listed in chronological order, bottom to top.)
Current: A, B->A
Desired: B->A
It also addresses reply chains.
Current: A, B->A, C->B
Desired: C->B->A
(I, personally, would prefer that replies were displayed in chronological order, e.g. A->B->C reading bottom to top, but that is not the current behavior of the Twitter and Mastodon feeds so I didn't change it.)