Fork me on GitHub
#braid-chat
<
2016-05-18
>
kevnk19:05:16

@rafd: I’m very intererested in braid. Looks like you guys have done a good amount of work! I have a use case that I’m curious if braid would solve...

kevnk19:05:56

I’m sure you’ve experienced it before - you’re in a channel/chat room/tagged convo, and are talking with someone about topic A and then someone (even you) needs to also talk about topic B but both are valid to happen within the same channel/room/convo.

kevnk19:05:54

So… one idea is to create some sort of branching functionality (like in a git repo) within a conversation

kevnk19:05:34

I guess within braid though, it could start a new tag (maybe temporary and maybe shares access with the parent/HEAD tag) and people could optionally subscribe/unsubscribe to that sub-tag

kevnk19:05:08

Then after the conversation is resolved, it could be merged back into the parent tag/convo

kevnk19:05:21

anyways - I’ve come up against this chat "problem" so many times, and branching these "side conversations" seemed like a solution that most people (developers at least) would understand

rafd20:05:31

hey @kevnk welcome!

rafd20:05:49

would having multiple conversations with the same tag work for your sitaution?

kevnk20:05:13

definitely

kevnk20:05:44

so you could mute specific conversations - which would be different than unsubscribing to a tag?

kevnk20:05:15

i was missing that concept from the video - that each conversation is a new instance in which you can interact with

rafd20:05:26

yes, muting is on the TODO list, we haven't needed it for compan

rafd20:05:32

yes, each conversation is a new instance

rafd20:05:36

i need to update the video 😛

kevnk20:05:38

it just looked like a new UI for a chat room

rafd20:05:46

things look a lot different since then

rafd20:05:47

would you like an invite to the live instance we have running?

kevnk20:05:00

oh sure - that’d be sweet!

rafd20:05:42

sent one to your gmail