This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (19)
- # announcements (1)
- # beginners (70)
- # boot (192)
- # braid-chat (55)
- # cider (3)
- # cljs-dev (42)
- # cljsjs (2)
- # cljsrn (25)
- # clojars (23)
- # clojure (162)
- # clojure-brasil (3)
- # clojure-czech (18)
- # clojure-russia (10)
- # clojurecup (3)
- # clojurescript (63)
- # code-reviews (6)
- # community-development (340)
- # core-async (7)
- # cursive (4)
- # datomic (20)
- # events (2)
- # funcool (3)
- # hoplon (20)
- # jobs (33)
- # ldnclj (11)
- # lein-figwheel (9)
- # leiningen (6)
- # off-topic (1)
- # om (79)
- # proton (4)
- # re-frame (39)
- # ring-swagger (4)
- # slack-help (2)
- # yada (2)
If folks are willing to go along with a not-identical-to-Slack clone, then great! Let's discuss. If no one is, and would rather stick with the Slack design, then that can happen as well (but I will continue working on what I have), and someone else would need to lead the project.
@rafd: I was working on/tinkering with similar ideas a while ago: http://www.martinklepsch.org/chaf.html ‚— maybe they provide some inspiration for you. There's a rationale missing on that page but you'll get it anyways I guess.
Do you think it is possible to scale your product to support several thousand users from an architectural point of view?
And do you think you can live with someone else also providing services and hosting around it? Not saying i want to do so, but once you open source it and it becomes popular maybe someone else will.
@sveri In terms of code, there are probably things that can be improved. Currently its websockets communicating with a small API on top of a datomic database. It wouldn't handle thousands of people tomorrow (partially architecture, partially the fact it's currently on a $10 DO droplet) ... but Facebook wasn't architected to handle the sort of load it has now in the first year.
@sveri as to your second question, I think it would only be fair to the community. I've been entertaining the idea of a license like Datomic (where they have open-versions, ...but you can't offer datomic hosting yet)... but... I know how annoying that sort of thing is (it's my biggest gripe with Datomic). I would rather encourage competitors and compete on service than stunt the open-source potential.
http://Wordpress.org + http://Wordpress.com is the closest model. I'm sure that devs + some companies + come communities would want to run their own version, but most would just want a hosted solution (like Slack). I'd hope that those interested in running a hosted thing would work with me rather than against, but, if it were to happen, it's ok.
@martinklepsch: a lot of good thoughts there. Showing all the active conversations has worked well in our setting (a few devs on a team), but I think your idea of showing just the initial message and then expanding is a good one for larger communities.
...which begs the question, how's that different from Discourse (which updates new posts in real time)
yes. the idea behind the name was
chat + forum = chaf. pretty dull but don't care
@rafd: it's real time but there's no chat feel to it. messages are composed in huge rich text fields and messages consume a good amount of screen space
@martinklepsch: I agree, I think there is room for something in between the two; forum-like but with a chat-feel
things are probably a little messy with the code at the moment, but I will do what I can to clean up and open-source today
I imagine the first little while will be people complaining about this and that... and me and @jamesnvc doing the fixes, which I'm fine with.
If things work out well I have a root server at hand we could use for a test instance and stuff
@rafd: Nice summary and introduction to your project. Since you are serious about this independent of the issues facing us with slack, I would love to participate in your development as an interested user and supporter.
The code is now available here: https://github.com/braidchat/braid I didn’t want to host it under my own github, so I gave the project a name: Braid. Wiki here: https://github.com/braidchat/braid/wiki We’ll be working on the ‘get-it-running-on-your-machine’ experience over the next week. In the meantime, you can try to decipher our setup notes here: https://github.com/braidchat/braid/blob/master/deploying.md
@rafd: I think there have been some interesting discussions that have taken place on the test setup of mattermost that might be of value to you. If time is precious you might want to ignore it, but if you want to see the kinds of things that were discussed over there please just let me know and I will PM you an invite link. This applies to anyone interested, btw. Just say the word.
@rafd: I will look through the code and see what potential starting point we may have, thanks again for your offer :-h
@gjnoonan: realistically, i don't think it's a contender for moving clojurians over in its current state
i started this group b/c i think it's a worthwhile effort independent of whether clojurians is on it
anyone have recommendations on preferred ways to do roadmap/planning tasks for an open-source project? I mostly see github issues being used for bugs and feature requests
@sveri: if you do get it running, let me know any issues you've faced (i've already written down 'don't require aws keys to get started')
I give it some time tomorrow and write up what i find. Thanks for providing the code so fast. Gn8 everyone.
I've used a bunch of different project management tools over the years. Can't think of one that I would recommend. These days I use pen and paper. Caveman style.