this makes a lot of sense, especially since our thread UX is not the flat standard one, when a user replies from the timeline, they don't know in which layer of the tree they're replying to. There is always a balance to find between overwhelming the feed showing too much info per single post and not giving enough context to the user (as it is now in bonfire and most of the social networks i'm aware of)
From a technical point of view, adding such info in feed views without impacting loading times to a point where it's not usable will probably mean we need to introduce caching (which we luckily haven't needed until now, as cache invalidation is famously said to be one of the "2 hard problems in computer science")... but it does indeed seem worthwhile!
Oomph I can imagine how difficult that is in a federated setting.! Maybe a balance can be found that just gives a rough sense of the "context size" of a post instead of being very exact about the whole thread metadata?
or alternatively we can leave the feed as it is, but showing more context when the user click on the reply icon.Rather than just showing the replied to post above the composer box, we can show a more contexted set of information related to the thread (We can merge the read discussion and the reply icon together, so that when you click on the reply icon it shows the thread and load the position where you want to reply to ?)
Ohh this is a good idea anyway, even if we add more info in the feed!
this makes a lot of sense, especially since our thread UX is not the flat standard one, when a user replies from the timeline, they don't know in which layer of the tree they're replying to. There is always a balance to find between overwhelming the feed showing too much info per single post and not giving enough context to the user (as it is now in bonfire and most of the social networks i'm aware of)
My sense is that commercial social networks have a high interest in providing minimal context. Minimal context increases engagement because users cannot figure out what has already been said in a discussion. Discussions most of the time look as if everything is still very "open" even if hundreds of messages already exist. The most "successful" posts on commercial social media work best without requiring any context. Such posts can be easily algorithmically processed, and presented to users at any time in any other context. Even the slightest improvement in that era would make bonfire stand out. The current nested thread view is already a great contribution.
This is a bonfire demo instance for testing purposes
Manual federation enabled