DimensionDev / DimensionDev/Flare

[Feature Request] Enhance "Share Image" to include both the root post and selected replies for better context

Open
#2,055 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
1.5k
Forks
67
Avg merge
11h 8m
Merged PRs (30d)
84

Description

Current Behavior:
Currently, if I want to share a post along with a specific interesting reply underneath it, the "Share Image" function doesn't quite capture the full context.

  • If I share a single reply, it only captures that reply itself.
  • If a reply receives a sub-reply specifically from the original post author (the OP), the tool captures that immediate parent comment and the OP's sub-reply. However, the original root post is still omitted.

Desired Behavior:
It would be incredibly helpful if the "Share Image" feature could allow users to capture the root post AND a selected reply together in a single image card.

Note: I have attached a few screenshots below to illustrate the current state and the desired effect.

Image Image

current state

Image Image

desired effect

Thank you for your time and for considering this request. I really appreciate the hard work you put into this unified social client!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the existing mobile “Share Image” entry point and trace how a selected reply and its parent context are assembled for image capture. Compare that flow with the root-post data and rendering path; done means one image card can include the root post together with the selected reply while preserving the existing behavior for other shares.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.