This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (8)
- # alda (11)
- # announcements (53)
- # architecture (2)
- # aws (10)
- # beginners (69)
- # boot (403)
- # braid-chat (160)
- # cider (10)
- # cljs-dev (14)
- # cljsjs (26)
- # cljsrn (34)
- # clojure (223)
- # clojure-art (1)
- # clojure-brasil (4)
- # clojure-dev (10)
- # clojure-france (1)
- # clojure-gamedev (1)
- # clojure-nl (14)
- # clojure-russia (20)
- # clojure-seattle (8)
- # clojure-sg (1)
- # clojurebridge (2)
- # clojurescript (156)
- # code-reviews (2)
- # community-development (305)
- # cursive (5)
- # datavis (33)
- # datomic (38)
- # devcards (4)
- # dirac (39)
- # dunaj (3)
- # emacs (5)
- # events (2)
- # funcool (45)
- # hoplon (3)
- # instaparse (24)
- # jobs (2)
- # ldnclj (77)
- # lein-figwheel (4)
- # leiningen (1)
- # mount (49)
- # nyc (14)
- # off-topic (52)
- # om (125)
- # omnext (4)
- # onyx (13)
- # other-lisps (1)
- # overtone (8)
- # parinfer (31)
- # plastic (6)
- # portland-or (3)
- # quil (4)
- # re-frame (6)
- # reading-clojure (16)
- # reagent (212)
- # ring-swagger (11)
- # robots (5)
- # spacemacs (4)
- # specter (1)
- # yada (26)
@meow: Not really sure what you mean with "female perspectives are being adequately addressed"? Do you mean how we can make sure to be a welcoming community to women and all different types of people in general?
mhh, haven’t noticed anything inappropriate yet, but then I also don’t read everything that is written here
I think the tone here on slack has been very respectful and having a CoC is maybe also helping
i’m a bit confused about the nature of this channel and the appropriate topic(s). is this supposed to be about building a slack alternative (developing the technology for the clojure community to use for communication) or about broader development of the human clojure community?
Oh, it seems that this pythonesque (sorry, had "bring out your dead" ringing out in my head when I've seen that) going around the channels actually worked somewhat D :
Re: SlackChat - Can someone explain to me how we assign ourselves to tasks/features using HackPad and how we can track which tasks/features are being worked on and by whom so we can collaborate. I'm a hackpad newbie and more used to Kanban/Agile boards.
@meow: cool- I'm going to try and get stuck into writing something tonight at pair programming event in London
Oh, I mean you going around channels and asking if people are ready for slackpocalypse ; d
@meow: just need a coding task that needs doing and we will pair up and crack on. Even if it's just a spike to test approach/validity. Do we have a github repo for project?
@rm: not sure myself and can't remember who made that comment - should have the author of the comment visible on the hackpad doc
but those are being worked on live as the devs work on it and I drive them crazy with all my posts and tagging and reactji performance art
it is an option that is being developed and they hope that it will be selected by the community but that is up to the community
Happy to take a look at #C0J20813K and maybe contribute but as pair programming event is mixed ability group doubt we will do much in 2 hours but something to look at
no problem it's something substantial to consider for pairing on rather than toy / algorithmic problems.
yeah, if you want to pair program that would be hard - if you just want to get on the system and play around for 2 hours we could probably make that happen
I need a custom file writer to produces X3D xml files because clojure
data.xml isn't lazy enough and I run out of memory at that step
I had a small hackathon a few weeks ago where we created a chatclient with electron, clojure and clojurescript. We also had a UX designer working on it and the code is open source (the client is here: https://github.com/stil4m/project-typo/tree/master/client) GitHub stil4m/project-typo project-typo - A chat client written in Clojure(Script) [11:50] https://www.dropbox.com/s/wr5ba5r22fzyh0p/Screenshot%202016-01-12%2011.49.59.png?dl=0 [11:50] It was very basic but some stuff could be reused (maybe) [11:51] https://s3-eu-west-1.amazonaws.com/uploads-eu.hipchat.com/31232/633885/J3R6I3izCbgGprb/Screen%20Shot%202015-12-19%20at%2020.50.27.png (178KB)
I just added a page to the hackpad https://hackpad.com/Chatroom-vs-....-8jJD3sxtRAf Chatroom vs …, discussing slack, braid, and chaf. "The goal of this page is to discuss "chatroom paradigms." Slack is what we currently have, and we don't want to lose the good things it provides, but several people have expressed the desire for an interface that is better at maintaining separate conversations."
In the context of ephemerality (is that a word even?) I see braid (very ephemeral) < slack < chaf (not ephemeral)
thanks for the feedback, I agree with the observations, my aim is to keep improving the Braid model; open to ux concepts and suggestions
if anyone feels like they aren't being heard I do apologize and hope you will be patient or speak up
@martinklepsch: Have you used Flowdock? I think it is worth checking as one example of threaded discussion.
If you have a better title please edit it. I also see a discussion about exploring other options because these mockups are for a really “traditional” chat application
We actually started with rethinkdb but we had random freezes and then we went on with couch. But is actually very nice for a chat application you can listen for changes and you just write some functions to group them by room. And you can even write some reducers to show for example the amount of messages per room
We first tried it with https://github.com/clojure-clutch/clutch but it was way easier to just do some http calls ourselves
Cool! I was wondering about rethinkdb vs couch actually. I also like the fact that couch has master master replication + there are a few couch people here in Berlin :)
I remember couch providing some user/auth stuff - did you make use of that @mitchelkuijpers
No we didn’t really get to that part to be honest because we rewrote the server in the middle of weekend to couch 😞 but it definitely has that
But the biggest strength of couch is writing views on your data @martinklepsch
I know you guys have decided on building a slack clone, buuut, have you looked at mattermost?
I see. People say it solved problems like REST protocol being relatively slow or having to write map/reduce beforehand and was curious if you had any hands-on experience with that.
I've updated this a little: https://hackpad.com/Slackpocalypse-GRIaf1RgP5D mostly removing markdown 😜
@meow: I think everyone who has streaming access should watch all extended versions of HUMAN.
that org has some code that I contributed and a mori-fork that will need to be maintained
@juhoteperi: I've never had a chance to use flow dock unfortunately. :( have heard plenty of good things about it wrt threading though
added a section listing other “wheels” https://hackpad.com/Home-YVTdpH47Vz4#:h=Other-wheels
thanks @meow ! Seeing lots of good conversation and trying to catch up. Sounds like a cool project.
Flowdock default view is very similar to Slack, but if a message is part of a thread it has color coded badge and the badge can be clicked to view and reply to the thread
@mitchelkuijpers: how annoying is it to write views in js? 😉 considering rethinkdb just to not have to have this cut
http://whatthefuck.computer/blog/2015/11/01/on-the-balkinization-of-my-chat-communities/ quite an interesting post I just saw on stuart sierra's twitter.
I have a greater appreciation of that having now subscribed to all 197 slack channels that we are using.
I think slack is really great, I don't think it's necessarily the best place for the clojurians to reside long-term.
I think we need to think about timelines pretty sharpish. We're at 5k, and it won't be long before we're under heavy scrutiny for the next community to be kicked off slack.
Given this, we want to try and migrate users over to the new system as fast as possible.
I like the idea behind Braid, but I wonder if it's not a little too late. I have no idea if Mattermost & co are too far away from ready for us though.
mattermost has some problems that might be hardish to solve (unread messages don’t work too well, messages don’t always show up), and a variety of things that shouldn’t be too bad (adding reactji, file preview)
I am wondering about scale with Mattermost. Will it support ~10k users (future proofing)
that's why I'm spending so much time living in #C0J20813K - because the devs are continuosly tweaking the system based on how we are using it
but they had a great concept and have a great handle on the real goal which is effective communication
Yep, that's the big concern with mattermost I think. It's still not quite engineered for us.
Yeah, that's how I stumbled into here. I've been following malcolm's work, and followed his interest.
but I can't dedicate myself to doing any coding so I'm dependent on devs from the community who are willing and able to create something
https://clojurians.slack.com/archives/community-development/p1452640589001886 we can still hack on mattermost
I wonder if http://matrix.org is flexible enough for us to just build a really nice cljs front-end for.
the benefit of working in clojure is that we can live in the system and do continuous integration
@jaredly: True. Golang is dictated heavily for Google's needs, it's always felt like it's OSS for adoption purposes more than anything. (to me)
As opposed to Golang, where you really can be very restricted by what the language designers will give you.
authentication in oAuth-style (you have an auth provider), so you can create one account, and use it on all your "networks"