This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-25
Channels
- # admin-announcements (3)
- # beginners (165)
- # boot (123)
- # cider (106)
- # clara (1)
- # cljsrn (20)
- # clojure (199)
- # clojure-canada (2)
- # clojure-dev (3)
- # clojure-poland (29)
- # clojure-russia (7)
- # clojure-taiwan (2)
- # clojurescript (487)
- # cursive (25)
- # datavis (89)
- # datomic (26)
- # gorilla (2)
- # hoplon (15)
- # ldnclj (12)
- # lein-figwheel (9)
- # leiningen (2)
- # liberator (1)
- # off-topic (25)
- # om (380)
- # onyx (26)
- # parinfer (52)
- # portland-or (12)
- # re-frame (28)
- # reagent (132)
@johanatan: +1 from me
It's a bridge-- the activity in each channel is mirrored in the other. Essentially melding the two into one
http://www.pilgrimbreak.com/how-to-access-slack-with-command-line-irc-client-irssi/ I guess I still don’t understand the difference
to me that looks like if I wanted to, I could use irssi (or some other irc client) to join to IRC networks and to Slack
did not know about this, will try it
is it enabled here?
it's still a little annoying having to connect to multiple channels/networks
No idea. Someone mentioned using an IRC client before, but now having moved to the Slack client
the idea with the bridge would be to copy messages from #C03S1KBA2 freenode to #C03S1KBA2 slack and vice versa
so you only need to watch one channel
@johanatan: maybe the blog post could have a better title? I hope I’m not the only one who didn’t realise what slack-irc is at first
@kauko: The title is "Bridging Slack and IRC" and that meant to me what I thought it would before reading the article (also those are the search terms I used to find the article in the first place). It looks like you made a snap judgement based on the URL rather than the article title.