Fork me on GitHub
#off-topic
<
2015-07-02
>
sveri10:07:06

hm, there is this website hosting talks with slides, and I just cannot remember the name of it

sveri10:07:11

anyone knows what I mean?

caskolkm10:07:18

slideshare?

sveri10:07:57

but similar

sveri10:07:10

you can watch the talks and the slides will switch according to the talk

sveri10:07:22

it's pretty popular, but jeez, I hate that when i cannot remember šŸ˜„

sveri10:07:51

@epi exactly, thank you very much

canweriotnow11:07:38

@sveri I talked to Slack when they started, backend is PHP.

canweriotnow11:07:10

FWIW, the http://exercism.io devs just had a slack vs. gitter discussion and decided Gitter worked better for us, for now. But also I ā¤ļø Slack. So not offering an opinion, just sayinā€™.

canweriotnow11:07:35

Also interesting: the ā€˜plaidchatā€™ node-webkit unofficial client for Linux/Solaris/etc. is actually better in some ways than the official Slack OS X content, while providing similar UX since the official client is node-webkit as well, IIRC.

juhoteperi12:07:31

Plaidchat looks okay but doesn't have e.g. autocorrect like Chrome

seancorfield15:07:16

@canweriotnow: very interesting re: Gitter ā€” Iā€™ve been using Gitter on a couple of projects and Iā€™m less than thrilled with it. Could you share some of the pros / cons from that discussion?

canweriotnow16:07:23

@seancorfield: Gitter doesnā€™t have the massive integration capabilities of Slack, but as those are really only applicable to paid accounts, I think thatā€™s a wash. Gitter doesnā€™t have the history limits AFAIK that Slack does on free usage, so you donā€™t have the one problem weā€™ve been having with clojurians slack, which is messages disappearing quickly. Gitter doesnā€™t offer the archive facilities, but again, not what Iā€™d consider an issue.

canweriotnow16:07:41

Features certainly arenā€™t 1:1 but Gitter is designed to work along with Github, so referencing issues and repos is nicely formatted, and project-specific channels (Iā€™m thinking of, e.g., the #C06AH8PGS channel here, could have all their github activity in the sidebar. So thatā€™s pretty cool.

canweriotnow16:07:16

Donā€™t get me wrong, I ā¤ļø Slack, I use it at work, but I think for large FOSS communities, Gitter has advantages.

canweriotnow16:07:50

Datascript, for example, has a ton of activity on Gitter, and it works really well.

canweriotnow16:07:34

The one major difference I would say is that Slack makes it easy to group all the channels in one ā€œteamā€ whereas Gitter would involve maybe making a directory for peeps to find things.

seancorfield16:07:42

Yeah, the GitHub integration in Gitter is nicer than Slackā€™s version (IMO). I hadnā€™t thought about the message history limit issue.

canweriotnow16:07:23

Also, Gitterā€™s use of Github Oauth for login negates the need for the email-invite system at http://clojurians.net

canweriotnow16:07:07

So, creating a ā€œclojuriansā€ Github org would then make it easy to create any number of channels under that category. It might also be necessary to create a directory of project channels like the existing datjscript channel and other projects on github under other users/groups

seancorfield16:07:40

I wasnā€™t sure whether Gitter required a 1:1 mapping between channels and projects in an org.

seancorfield16:07:31

Oops, just noticed I omitted "less than" in my post above ā€” now edited ā€” since I was not happy with Gitter, and preferred Slackā€™s UX.

seancorfield16:07:32

Most of the Slack communities Iā€™m in have no associated presence on GitHub and a couple of them are either not very technical or not involved with OSS at all.

seancorfield16:07:57

But itā€™s interesting to read about peopleā€™s experiences with Slack at scale (there are around 1,700 Clojurians already). WordPress has a 5,000+ member Slack community and a couple of others Iā€™m in are well into their hundreds already.

canweriotnow17:07:19

No, you can have random channels under an orgā€¦ exercism has /roadmap, /dev, /support, etc.

canweriotnow17:07:32

I think itā€™s on the order of users * messages-per-user, itā€™s that message storage limit that gets you.