Skip to content
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

Open
braid-sync opened this issue Mar 31, 2017 · 3 comments

Comments

@braid-sync
Copy link

braid-sync commented Mar 31, 2017

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

@braid-sync
Copy link
Author

➤ Braid Sync Bot commented:
wade 22-01-2016:

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
#commenter rafd
---[gh]

@braid-sync
Copy link
Author

➤ Braid Sync Bot commented:
braid-fork-idea

  • would need a way to see forked messages from the original message
  • "fork" could probably have a better name, ex "reply" (?)

[--- Commented from GitHub.com
#commenter rafd
---[gh]

@cauebs
Copy link

cauebs commented May 29, 2017

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?

@braid-sync braid-sync changed the title branch / fork / reply to a message in a conversation [braid/core] branch / fork / reply to a message in a conversation May 23, 2018
@braid-sync braid-sync changed the title [braid/core] branch / fork / reply to a message in a conversation [braid/core] add ability to branch / fork / reply to a message in a conversation Jun 12, 2018
@braid-sync braid-sync changed the title [braid/core] add ability to branch / fork / reply to a message in a conversation [braid] add ability to branch / fork / reply to a message in a conversation Jun 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants