This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-06
Channels
- # adventofcode (1)
- # aleph (9)
- # announcements (22)
- # beginners (59)
- # boot (8)
- # calva (1)
- # cljdoc (7)
- # cljs-dev (10)
- # cljsrn (9)
- # clojars (10)
- # clojure (23)
- # clojure-dev (6)
- # clojure-europe (3)
- # clojure-italy (26)
- # clojure-nl (3)
- # clojure-seattle (1)
- # clojure-spec (46)
- # clojure-uk (85)
- # clojurescript (97)
- # core-async (13)
- # cursive (3)
- # data-science (10)
- # datomic (156)
- # duct (34)
- # emacs (37)
- # figwheel (3)
- # figwheel-main (9)
- # fulcro (59)
- # hyperfiddle (4)
- # immutant (1)
- # jackdaw (3)
- # jobs (1)
- # off-topic (112)
- # parinfer (1)
- # qlkit (2)
- # re-frame (1)
- # reagent (35)
- # ring-swagger (2)
- # shadow-cljs (104)
- # spacemacs (9)
- # speculative (12)
- # tools-deps (30)
- # yada (10)
i'm unable to connect to http://clojars.org atm, wondering if anyone else if having the issue
just noticed that the earlier history of this channel is gone. Why would anyone use Slack for anything that is supposed to be open?
Discussions about that happen in #community-development (the topic/description there link to persistent information about "Why Slack?" and all the alternatives people have tried).
@UEJ5FMR6K there is also the Slack log at https://clojurians-log.clojureverse.org
@mgrbyte can you give some more details or open an issue? I've heard of IPv6 issues from someone else recently, but we haven't been making any changes AFAICT
there are some ipv6 checkers out there if you google for them
might be helpful, dunno