This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-18
Channels
- # admin-announcements (7)
- # arachne (24)
- # beginners (40)
- # boot (24)
- # braid-chat (22)
- # cider (8)
- # cljsrn (35)
- # clojure (32)
- # clojure-austin (1)
- # clojure-belgium (52)
- # clojure-russia (16)
- # clojure-sanfrancisco (1)
- # clojure-taiwan (2)
- # clojure-uk (25)
- # clojurescript (112)
- # core-async (3)
- # cursive (18)
- # data-science (1)
- # datascript (7)
- # datomic (30)
- # devcards (2)
- # dirac (12)
- # emacs (4)
- # flambo (1)
- # funcool (5)
- # hoplon (146)
- # jobs (9)
- # jvm (5)
- # off-topic (4)
- # om (141)
- # onyx (22)
- # re-frame (89)
- # reagent (86)
- # ring-swagger (31)
- # rum (3)
- # spacemacs (1)
- # specter (10)
- # untangled (112)
- # yada (3)
@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
so you could mute specific conversations - which would be different than unsubscribing to a tag?