On Wed, Dec 7, 2016 at 7:02 PM, Mihai Maruseac wrote:

/me goes and investigates if a bot who will duplicate lines in #irc/slack/gitter to the other 2 channels is a good investment.

Duplicating stuff between communities with >1000 participants can be asking for pain. #haskell already decided against such a link with the Slack community (or rather, such a link exists but by specific request it only forwards from IRC to Slack). -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

From my point of view all mentioned solutions aren't perfect:

+ with IRC I always lose the history, also, my client (Lingo on OS X) always disconnects and I can lose answers really easy too + I tried Slack in the past, and found no advantages or something that buys me + Gitter is quite buggy for now However my personal preference is Gitter, because it give history, edit abilities and nice code appearance for free (though I wish to see light theme for code highlighter as GitHub provides by default).

Does this really have to be all or nothing? It's just chat, something I consider fairly ephemeral anyway. I'd much rather people talk about Haskell as much as possible, even if that comes at the expensive of having one blessed channel/medium. On Thu, Dec 8, 2016 at 11:02 AM Alexander Kjeldaas < alexander.kjeldaas@gmail.com> wrote:

I agree.

While I've used IRC for almost 20 years, it just isn't as usable as the newer tools. - IRC assumes a permanently connected computer, which again requires a VPS as indirection. I do use that, but there are clear usability issues here. - IRC further assumes that I will be on one device only. Again I solve this by jumping through a VPS. It's a design flow though. - Slack is great, but enterprise (login ++). - Gitter is just "yet another tool", might be the best thing, but it just hasn't got the mindshare yet.

A technical solution where freenode's #haskell is bridged to one of the new fancy web UIs, where history is kept, and multiple devices can be used, would be great. I'm not sure if anyone is doing that though.

Alexander

On Thu, Dec 8, 2016 at 9:44 AM, Geraldus wrote:

From my point of view all mentioned solutions aren't perfect:

+ with IRC I always lose the history, also, my client (Lingo on OS X) always disconnects and I can lose answers really easy too + I tried Slack in the past, and found no advantages or something that buys me + Gitter is quite buggy for now

However my personal preference is Gitter, because it give history, edit abilities and nice code appearance for free (though I wish to see light theme for code highlighter as GitHub provides by default).

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Slack and Gitter are necessary steps for the final goal: The rediscovery of google wave. I would like to link to specific comments in the code, execute bots and collaborative editing, But is more usable than IRC. 2016-12-08 14:16 GMT+01:00 Geraldus :

Does this really have to be all or nothing? It's just chat, something I

...

consider fairly ephemeral anyway. I'd much rather people talk about Haskell as much as possible, even if that comes at the expensive of having one blessed channel/medium.

+1

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

-- Alberto.

On Thu, Dec 08, 2016 at 03:19:03PM +0100, Imants Cekusins wrote:

It's a pity Google Wave was shut down. I used Google Wave, found it very convenient and would use a similar product again (even with fewer features) if it became available.

Apache wave! Which is open-source too, unlike Slack and apparently this new fangled tool for open communities.