there’s been recent discussions on various groups related to comments/threads similar to how telegram implements comments/threads.
currently, we have the option in a group to reply privately. im not sure of the mechanics in the client code but have a decent grasp on the backend flow.
let’s say we’re in a baker’s group. jack posts a good recipe for muffin. i could reply privately or what if you can reply as a thread but its a child group of the parent group which parent members are added to automatically. similar to clone chat where the origin attributes are persisted (members etc) but its a new chat_id
seems the most direct route would be to consider a comment thread to be a sub/cloned group that persists the parent group members and metadata attributes to start a new thread to continue the conversation.
attached is an image to better represent the control flow
A workaround would be to a client side script the creation of a new chat group (or cloning the original one with a few distinct modifications), sending the invite link as a reply to the topic starter, forwarding the topic started message to the new group along with an invite link back to the parent group. This would already provide a clickable back & forth modality between the position of breaking out and the main discussion.
It could also be worked around by creating a new hosted bot that would execute the outlined steps upon bot commands or when forwards the topic starter in a private message to the bot to generate less noise in the main group. Maybe we should create a separate issue for this or repurpose this one?
A workaround would be to a client side script the creation of a new chat group (or cloning the original one with a few distinct modifications), sending the invite link as a reply to the topic starter, forwarding the topic started message to the new group along with an invite link back to the parent group. This would already provide a clickable back & forth modality between the position of breaking out and the main discussion.
thanks for the feedback. unfortunately this won’t be reasonable for most users. the feature shouldn’t require a user to do workaround for basic communication. i created this thread to visualize the control flow whereas the other posts are more wishlist vs theoretical implementation.
It could also be worked around by creating a new hosted bot that would execute the outlined steps upon bot commands or when forwards the topic starter in a private message to the bot to generate less noise in the main group. Maybe we should create a separate issue for this or repurpose this one?
a bot could work, but at the cost of complexity. again the goal is to bring comments/threads natively into the ui. this is a long-term goal. one of which i’m working on in my free time when not triaging other issues.
