This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-18
Channels
- # beginners (56)
- # boot (1)
- # cider (96)
- # cljs-dev (148)
- # clojure (60)
- # clojure-austin (11)
- # clojure-france (2)
- # clojure-italy (5)
- # clojure-russia (11)
- # clojure-spec (31)
- # clojure-uk (5)
- # clojurescript (52)
- # community-development (37)
- # cursive (3)
- # data-science (8)
- # datomic (14)
- # devcards (2)
- # emacs (1)
- # fulcro (13)
- # hoplon (1)
- # immutant (2)
- # luminus (3)
- # off-topic (2)
- # onyx (16)
- # parinfer (38)
- # re-frame (8)
- # reagent (5)
- # shadow-cljs (332)
- # spacemacs (5)
- # specter (5)
- # sql (6)
- # vim (52)
@logbot seemed to stop logging our #parinfer channel back in november đ
checked other channels, i guess logbot became non-operational for all channels in november
did i miss something?
@shaunlebron it is still logging but the website to search the logs is under repair
thanks, is it this one? https://github.com/clojureverse/clojurians-log-app
@seancorfield do you have the ability to put an informational notice on the clojurians slack log website? i think this question comes up twice a day (with good reason)
thatâs probably it (?). iâm really just repeating what iâve heard on slack before
@lee.justin.m I have nothing to do with the logging site, sorry. @shaunlebron it is still logging. Just the display part is broken. @plexus is working on a replacement.
I almost donât want to start another common recurring thread ⌠If the hackpad file is what contains the FAQ, then Iâve never seen it because of the Dropbox login requirement. Is it possible to post it as a âShared Fileâ in Slack without it being reaped by the auto-cleaner? Or create a clojurians/community-development project in GitHub solely to host a FAQ and maybe also issues in a less ephemeral way?
I don't know how to get access to that Hackpad document any more. I don't remember who created it (and they may no longer even be active in Clojurians any more). I agree that it would have been better to put it up on a public wiki in the first place.
https://github.com/clojurians should host the FAQ I think?
I believe itâs been automatically migrated over to dropbox, where I donât have an account.
Seems a bit moot these days but might be good to archive it e.g. in a github account.
Largely moot, I think that #braid-chat was really what came out of that since the hackpad consensus was that we really shouldn't rely on a non-community developed chat tool
But largely moot because for whatever reason weâre not moving this off Slack any time in the foreseeable future.
Still, it would be good to have the investigation of alternatives up somewhere we can point people to when they ask âbut what about⌠xxxâ
I think so, @seancorfield who would need to create that repo?
the year is 2018 and mailing zips around is still one of the most reliable delivery mechanisms #darkesttimeline
soon the only way to deliver data will be steganographically appending it to a series of advertisements
like the block chain but for ads