You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: