Fork me on GitHub

remote for standup today, ito afetr




derp disregard that


It's kind of a bummer we're locked into 10,000 messages in the archive


Has anyone spoken with the Slack folks to see if they'd be willing to give us a paid account for free?


The downside to moving to a paid account would be having to pay $6*15000 /mo right?


@erichmond: yes, and for obvious reasons, that ain't gonna happen


i messaged their support and politely request they consider giving us access the ability to search the archive


being capped at 10k is a pretty big bummer


unless someone is capturing all of the messages somewhere and making them searchable...


(which is an option)


I do believe that’s a violation of the ToS.


@devn: this is a known issue and there is a bot, or there was one. The admins are dealing with it so we probably shouldn't all bug the slack folks.


I wonder what the language there is...


It’s actually kind of vague. I think that @gjnoonan was looking into it.


some integrations by their very nature force you to see every message anyway


people persist all sorts of bits already


seems more or less unenforceable


@devn: I agree, but I think we're trying be polite at this point. Anyhow, I haven't bothered to look because I've been on here a while, but I'm pretty sure someone added a bot to all the channels and was archiving this. @gjnoonan is probably the best person to ask.


@meow: gotcha. thanks for the info. given Slack's recent valuation, you'd think they could find it in their hearts to give an open source community some love.


@devn: I know, right! simple_smile And welcome aboard.


Looks pretty clear that we should be able to create our own searchable archives: > Slack is the custodian of data on behalf of the teams that use Slack. We don’t own team communication data. Teams own their data. They like it that way and so do we. and > Administrators of all teams, both free and premium, can export their team’s message content that is shared in channels. Message history for private groups and direct messages is not included in this.


IRC + cute colorscheme == $$$


@meow: thanks man! I'm kind of amazed to find out about this so late. I've been in IRC since 2010


@meow: yeah, and the pricing model just doesn't make sense for a community like this. the number of active users for a particular day is nowhere near the full number of users who have access


@devn: the big adoption of slack by clojurians is quite recent.


so charging by user is kind of insane


On the bright side, the clojure community is really amazing and I'm so glad I decided to start using clojure.


How does map-vals ( differ from something like this:

(into {}
  (for [[k v] m]
    {k (f v)}))


martinklepsch: It uses transients


@juhoteperi: and that’s the only difference?


@juhoteperi: is that actually a relevant property in the context of


@martinklepsch: Well, it's a function so it's easier to compose etc.


@juhoteperi: but that could equally easy be achieved with into & for right? (not trying to rule out using the map-vals from potpuri, just curious for reasons)


martinklepsch: Yes. Or (reduce-kv (fn [acc k v] (assoc acc k (f v))) {} m)


Btw. I don't like slacks nick autocomplete. I always forgot to write @, the nicks aren't ordered by who has spoken the last and ctrl-w doesn't remove previous word but closes the tab.


@juhoteperi: you can start a message with /feedback to send to slack. some good tips there


That was easy. Though I guess bringing readline commands to browser would be hard and upset many, and I can do that myself with cVim.


logbot is the bot


I can't remember who gets credit for setting it up.


@ul did it based on the whois info simple_smile


thanks for the link @meow


@martinklepsch: i was really resistant to ideas like map-vals, filter-vals, etc. once upon a time


but now i have to say i view them as a obvious hole in the stdlib


along with things like deep-merge


i voted for (into {} (for ...)) on numerous occasions

Alex Miller (Clojure team)20:06:20

deep-merge has been batted around in the past and Rich didn't like the fuzziness of certain parts of the proposed version

Alex Miller (Clojure team)20:06:31

but I don't think he was against the idea

Alex Miller (Clojure team)20:06:53

I personally would love to see a few things like map-keys and map-vals in the box

Alex Miller (Clojure team)20:06:27

but of course there is nothing stopping you from using the fine versions available in your favorite utility library


It'd be a fun hack to try to walk the crossclj dataset and find the most used library symbols... maybe even most duplicated functions and then propose those to core.

Alex Miller (Clojure team)21:06:20

arrdem: that sounds like a terrible idea :)

Alex Miller (Clojure team)21:06:12

I think weavejester/medley has most of the things in it that I wish were in core

Alex Miller (Clojure team)21:06:06

fyi, I created #C06E3HYPR


alexmiller: I mean if your goal is to include in core the things that people otherwise reinvent for themselves 😛

Alex Miller (Clojure team)22:06:14

Well it's a matter of judgement of course- I don't think core can or should contain everything. But obviously some things are widely used and useful.

Alex Miller (Clojure team)22:06:35

And I think it's particularly compelling when it affects portability across platforms or greater perf can be achieved

Alex Miller (Clojure team)22:06:56

Some of the map-keys etc have many possible impls that vary a lot


@alexmiller: dissoc-in would be a prime candidate for graduation from Clojure Incubator


@meow: @devn @akiva Sorry for the late reply, I have been out to the cinema and for a meal with friends (Yay Jurassic World). at our current number of users it will cost $125,856 per year to upgrade to the standard plan; Far more than I can afford! I have contacted slack about adding an open source tier to their pricing structure, for the myriad of communities that have started to use it (I myself am a member of 11 so I can attest how popular it is in that space) and how much good standing it would put them in in said communities, heck I couldn’t care if they didn’t give us unlimited integrations .. just unlimited message history. Initially they were very receptive and said they had been throwing around the idea themselves, then after further discussion I was told “not yet”. I contacted them about their rather ambiguous TOS and our logbot but did not hear back— I will Chase that up now though. However as you have discovered we own the data so I don’t see the harm, a few channels have asked for the logbot to be taken out (clojureladies) which we have done.


I will chance them now, and let you know when/if I get a response

Alex Miller (Clojure team)23:06:51

@danielcompton: yeah, I think the main open question on that is what to do when a submap is empty - remove or leave?


Yeah it’s tricky, I’m personally in favour of removing submaps, though I don’t really mind one way or the other though. It would just be nice to have one of them in there, and document it’s behaviour wrt submaps.


@gjnoonan: @devn @erichmond @meow @akiva I know it's probably too late but why not it has unlimited chat history and seems more geared toward developers (not that I've used it). Also has explore option. I find it hard (impossible?) to search for slack teams without somehow just stumbling across them.