Fork me on GitHub
#slack-help
<
2017-03-23
>
viesti05:03:58

ah, didn't occur to me yesterday, should be invited by default :)

seancorfield05:03:38

That's not how Slack works @viesti 🙂

seancorfield05:03:54

(but, yeah, that would be convenient)

viesti05:03:17

was already thinking if the community could pay for history

viesti05:03:33

kinda looses a piece of slack functionality this, but irc does not keep history either without a similar bot

seancorfield05:03:08

Slack's monthly fee would be astronomical.

seancorfield05:03:50

(fwiw, we've had this discussion repeatedly over the years -- and the irony that Slack's 10k message limit "hides" these repeated discussions is not lost on those of us who've "fought this battle" many times!)

seancorfield06:03:30

I must admit, it would be a great feature for Slack to auto-invite certain users into any new channel... but I can pretty much only think of it being used for adding logbots to new channels, which of course runs completely counter to Slack's commercial program 🙂

viesti06:03:25

not the only community figuring this out I bet

seancorfield06:03:32

It used to be that 5,000 was pretty much a hard limit, then it was 8,000. Now? I'm not sure. We're at 9,000+...

viesti09:03:25

yep, they might increase in the future. I did know about the history issue, but was hilarious to find out history of #powderkeg reaches to 16th, only a week back from now, while looking for a message that I posted just over a week ago 🙂

viesti09:03:13

image one being on a holiday, could sorely miss out chat history 🙂

seancorfield16:03:34

Slack sends weekly statistics to the admin team. We typically see 15,000-20,000 messages a week here, so seeing even a week of message history is a luxury 🙂

darshanime16:03:20

can the community consider Zulip?

darshanime16:03:38

Or even Gitter (it will be opensourced soon)

seancorfield17:03:13

#community-development is the place for that discussion — and, yes, nearly all of these things have been discussed and tried, and there are many aspects of running a large community that just don’t work on most of those alternatives. That channel has a link to a community document listed stuff that’s been tried and why it wouldn’t work or why folks don’t like it.

seancorfield17:03:17

(and there is a Clojure community set up on Gitter, but very few people have wanted to switch from Slack)

seancorfield17:03:02

https://gitter.im/clojure/general has just 34 people, but there are a few projects (cider/emacs, Onyx) that have active Gitter communities.