This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-19
Channels
- # beginners (25)
- # boot (143)
- # braid-chat (9)
- # cider (18)
- # cljs-dev (88)
- # cljsrn (1)
- # clojure (91)
- # clojure-austin (2)
- # clojure-berlin (3)
- # clojure-japan (26)
- # clojure-russia (148)
- # clojurebridge (1)
- # clojured (29)
- # clojurescript (105)
- # cursive (7)
- # data-science (4)
- # datomic (15)
- # devcards (4)
- # emacs (8)
- # euroclojure (2)
- # events (1)
- # gsoc (27)
- # hoplon (3)
- # immutant (3)
- # ldnclj (3)
- # lein-figwheel (9)
- # leiningen (2)
- # luminus (1)
- # off-topic (5)
- # om (176)
- # onyx (136)
- # parinfer (16)
- # proton (13)
- # re-frame (33)
- # reagent (34)
- # spacemacs (1)
- # yada (127)
I’m seriously considering making a braid-style client for slack, for use at work. cut down on the fomo & irrelevant notifications
@jaredly cool, any threading, or just the 'inbox' style? would be open to having slack integrations added to Braid client
not sure. thinking about just having each channel be a thread the more interesting ideas are about notifications — e.g., I probably care about the first few messages after I post (if there were no immediate replies), so surface that for me, and in some channels I actually don’t want to be notified for at-channel messages, etc.
it could be interesting to do some heuristics to try to infer threads from a flat slack discussion
I’d guess you could get pretty far just by time-boxing — e.g. if there’s a break for more than 10 minutes, and the new message doesn’t contain an at-mention of one of the last 3 speakers, then start a new conversation
we're planning on starting integrations work for Braid, and can bump that up to facilitate a Braid-Slack integration