Dimillian / Dimillian/IceCubesApp

Feature request: Show all replies when viewing single toot

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

Nobody has claimed this yet.

enhancement
Dominant language
Swift
Stars
7.1k
Forks
720
PR merge metrics
No merged PRs in 30d

Description

Problem:
Currently when viewing a single toot, you only see some replies. You have to visit the source instance to see all replies, but this means you cannot reply as you are no longer logged in.

Proposed solution:
When the user selects a single toot it makes an additional call https://docs.joinmastodon.org/methods/statuses/#get to get ALL related status and display them.
This means that when viewing a timeline you will still see an incorrect number of replies.
BUT when opening the toot (for example, to reply), you can view more replies to add to the conversation instead of repeating the same point others are making.

Concerns:
Does this go against the intended design?

Additional notes:
Should this be an advanced feature that requires user enabling in settings? Should it default on or off?

Happy to work on this feature if it gets approval from IceCubes repo owners

Contributor guide

No contributing guide indexed for this repository

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 at the single-toot view in the SwiftUI Mastodon client and review how the current status data and replies are loaded. Read the Mastodon statuses API documentation linked in the issue before deciding how an additional request would fit. Done means the opened toot can display all available related replies and still allow the user to reply, with the default or settings behavior resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
api, mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.