-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[braid] add ability to branch / fork / reply to a message in a conversation #243
Comments
➤ Braid Sync Bot commented: It would be good to find the previous chats that a new tag/idea originated from. On Discourse you can reply as a linked topic. Sort of the same idea just a different implementation. [--- Commented from GitHub.com |
I love the idea of forking. What about allowing only one fork per message? If you fork that into a new conversation, the Fork icon now takes you to the newly created conversation. Maybe I missed some use cases you had in mind, but this way the idea of forking seems pretty easy to understand. Besides forks, I personally think replies help bring the chat together, removing ambiguities that might arise because someone sent a message just before yours, or because the message you're addressing has already been buried by others. I use telegram daily and their solution is simple and effective: a message can be a reply to another message, as simple as that. It's only a link to a previous message (maybe notifying whoever wrote it). What do you guys think? |
have UI in a message to allow fork
at minimum, would be nice to be able to fork retrospectively
(ie. someone messaged in thread, but then someone else can instead make it a fork)
would want to show ‘forks / replies’, on the message, which would then show a separate thread/convo
the new convo would have “re: [link to previous thread]” at the top
The text was updated successfully, but these errors were encountered: