@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...
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.
So… one idea is to create some sort of branching functionality (like in a git repo) within a conversation
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
Then after the conversation is resolved, it could be merged back into the parent tag/convo
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
hey @kevnk welcome!
thanks!
would having multiple conversations with the same tag work for your sitaution?
definitely
so you could mute specific conversations - which would be different than unsubscribing to a tag?
i was missing that concept from the video - that each conversation is a new instance in which you can interact with
yes, muting is on the TODO list, we haven't needed it for compan
yes, each conversation is a new instance
i need to update the video 😛
it just looked like a new UI for a chat room
things look a lot different since then
https://www.dropbox.com/s/5tg0y7g9xojzwu7/Screenshot%202016-05-18%2016.16.52.png?dl=0
would you like an invite to the live instance we have running?
oh sure - that’d be sweet!
sent one to your gmail
i’m in