This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-23
Channels
- # aleph (8)
- # aws (2)
- # beginners (36)
- # cider (35)
- # cljs-dev (157)
- # cljsjs (3)
- # cljsrn (5)
- # clojure (97)
- # clojure-dev (5)
- # clojure-gamedev (3)
- # clojure-italy (27)
- # clojure-russia (11)
- # clojure-spec (19)
- # clojure-uk (39)
- # clojured (6)
- # clojurescript (87)
- # clojutre (4)
- # community-development (35)
- # cursive (8)
- # datascript (2)
- # datomic (14)
- # dirac (8)
- # duct (3)
- # figwheel (13)
- # fulcro (22)
- # graphql (20)
- # jobs (1)
- # london-clojurians (1)
- # off-topic (55)
- # onyx (3)
- # parinfer (3)
- # protorepl (39)
- # re-frame (3)
- # reagent (26)
- # ring (7)
- # ring-swagger (2)
- # rum (1)
- # shadow-cljs (107)
- # spacemacs (8)
- # test-check (4)
- # unrepl (3)
am I correct in assuming that the current archives do not have data for 2018 yet? (https://clojurians-log.clojureverse.org/clojure/index.html)
has anyone here successfully connected to this slack with wee-slack?
perhaps there’s a plugin that needs to be installed on clojurians side before it works
I haven't to this slack, but I have to our work slack with no changes on the work slack side.
I'm sending this message from weechat - the trick was to get a legacy token and store and use that, instead of relying on clojurians to integrate
@noisesmith that's what I was about to say. The OAuth application is very new.
yeah - it seems decent so far - haven't tried anything like threads yet though
@noisesmith I really like threads, I place them equal with native ones. The only things that bother me are : No notifications when I open weechat again No all threads page Naming a thread doesn't work with go.py
testing thread reply
interesting - so how do I start a thread from an existing message?
n/m I RTFM and I figured out how to edit too 😄
testing Emacs ERC via the IRC bridge on http://clojurians.irc.slack.com:6697
So far, reactions and threads aren’t being recognized … not sure if that’s config related.
testing Emacs ERC via the IRC bridge on
[12:54]
<dominicm> halo [12:55]
<dominicm> i am testing
<noisesmith> nice
<dominicm> reactions are fun too
I suppose not, considering how old the protocol is.
problem being, I can’t even see that your comment was in this thread… Had I responded in IRC it would have been out of context in the main channel.
yeah, the slack UI is richer - eg responses, threads, edits - and since weechat hooks into those I can use and see them all from weechat, but to do it via IRC you'd need some interface to stack that on irc and it would look weird from a normal client
I just ran into a weird thread bug in weechat though
if I respond to this thread in weechat, I only see the message in the GUI slack, not weechat