This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (69)
- # alda (8)
- # beginners (6)
- # boot (182)
- # cider (10)
- # cljs-dev (24)
- # cljsrn (17)
- # clojars (70)
- # clojure (142)
- # clojure-brasil (5)
- # clojure-czech (1)
- # clojure-poland (4)
- # clojure-russia (96)
- # clojurescript (115)
- # community-development (37)
- # component (6)
- # cursive (11)
- # datomic (32)
- # events (4)
- # funcool (6)
- # hoplon (17)
- # ldnclj (10)
- # lein-figwheel (24)
- # mount (12)
- # om (141)
- # onyx (7)
- # parinfer (48)
- # re-frame (24)
- # reagent (31)
tbh I fail to understand why IRC is not more used, it seems to be the perfect candidate: has (or can have) archives, it's distributed, mirrored, has tons of clients with all kind of fancy plugins, bots, auth etc. It's just a matter of using a good web front-end and we have basically an open slack alternative.
slack removes the barrier of entry for the uninitiated, its just easier to join and the UI is pleasant
Maybe that's were the focus should be, making a good IRC front end (if none exists), and rely on a nearly 30 yo battletested protocol like IRC with all its plugins & co
the UI can be enough reason to choose a product over another one, like you said , this is a good opportunity to make IRC better
IRC is a protocol, if you want to make something useful and not reinvent a wheel just build on it imo
@gjnoonan: if you need people to test the mattermost installation, I wouldn’t mind pitching in. EDIT: nevermind, I saw the link in the other channel.
I guess what you want is a slack, that speaks the IRC protocol and has a public server that you can connect to with any IRC client
yup more or less (potentially multiple servers). The only missing piece is a decent (clj) server app that does the bridge between a web-ui and irc servers since I am not sure you can just talk to irc directly from js/html. all the rest is candy (snippets, bots, logging, etc) and doable via bots/client side work.
These are good questions being raised. Let me play devil's advocate for a minute. If it is so easy to do a web client for IRC then why hasn't it been done? I'm not completely new to this. I've used a wide variety of IRC clients over the years and before that I would dialup to the Delphi service. When I was active in Python there was plenty of solid support for protocols like IRC and robust server frameworks like Twisted and Django and yet, I've never seen it happen. I've never seen a good web IRC client like Slack. Why not?
Sure, but we all love chat and dogfeed that [email protected] constantly. We make great editors, like emacs and IntelliJ but never good chat.
Not relevant. We're talking about a chat system for use by the Clojure community. We're all developers. And yet Clojure on Slack is superseding Clojure on IRC and if we lose the use of Slack we need an alternative. That's the issue in question right now.
And we're still human beings and social creatures, so of course one of the things we keep focusing on as we evaluate the alternative is what? Can anyone guess?
IRC is good at plain text; that’s it. It doesn’t support inline images, code formatting, or, well, anything other than plain text.
So no one sees the need to build a super-slick interface around what is a plain text interface.
@akiva: Very good point. And as someone who likes to post pretty pictures I would lose out. And colin provides tech support for Cursive and needs people to be able to submit error logs. And we all post code snippets for discussion. Plain text is not enough any more.
It could be bolted on, now that I think about it. The UI client could look for triple-ticks or other metadata and then transform the display but it would look ugly as sin for someone directly connected through an IRC client.
yes, the slack API sends emojis as their name, which is the canonical version: https://api.slack.com/docs/formatting#emoji
it's a bit like saying git commit messages do not support anything other than text, yet they show a lot more on github if you know the proper formatting or with interpretation from the client
The other issue is that, as far as I remember, IRC has no security. Anybody can join at any time as long as they know the server name. And everything is sent clear text. And, based on my experiences with the EFNet split wars of the late 90s, it can be absurdly unstable.
do you mean git commits or commit comments? AFAIK github always shows the commit message monospaced; if a branch has only one commit, the body of the commit message is used as the default for a pull request from that branch, but that's not the same thing
And there’s no user system. You can have a NickServ bot or whatever but it’s not really geared for what we’re looking for.
Right but eventually you start to pile these things up and it becomes a question of is it more worthwhile to shore up IRC to what we need or to just build our own messaging system with everything baked in rather than bolted on.
You get a battletested communication protocol with tons of server impl./plugins/bot/clients for free, in my book it's a big plus
Here's a nice github example: https://github.com/pkobrien/cad/blob/master/output/decorum/decorum-delta-vase-test-04.stl
This conversation about writing our own version of Slack seems to surface every couple of months, last time is was when one of the other dev community teams (Elixir I think?) had restrictions imposed on the number of members as it was > 5000.
We are actively evaluating alternatives to slack as they are not in favor of supporting us as a free community.
@tcrawley: I can give you permissions to add it to slack, if you have the correct permissions to the clojars github
@tcrawley: I know, I was being slightly facetious, sorry lol. you have permissions to add integrations now 👍
@mpenet I agree, a slick frontend to IRC + persistence + plugins + mobile clients would be ideal