This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # bangalore-clj (4)
- # beginners (160)
- # calva (132)
- # cider (18)
- # clara (1)
- # cljsrn (2)
- # clojure (129)
- # clojure-boston (1)
- # clojure-europe (5)
- # clojure-italy (5)
- # clojure-losangeles (1)
- # clojure-nl (33)
- # clojure-uk (49)
- # clojurescript (88)
- # cursive (20)
- # datomic (5)
- # duct (3)
- # fulcro (33)
- # graphql (7)
- # jobs (3)
- # kaocha (3)
- # nrepl (41)
- # off-topic (58)
- # pathom (18)
- # re-frame (1)
- # reagent (5)
- # shadow-cljs (148)
- # spacemacs (7)
- # tools-deps (7)
Hi there! I am looking for job now, and if anybody have cool idea or open-source project I will pleasure to help write couple of line for you. I hope it's not so incorrectly for this chat to write like this. 🙂
I work on Yetibot - a chat bot written in Clojure. very beginner friendly and welcoming of new contributors. http://yetibot.com / https://github.com/yetibot/yetibot check out some of the "good first issue" https://github.com/yetibot/yetibot/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22 and if you want to learn more just ask! we hang out on Yetibot slack - feel free to join at http://slack.yetibot.com
https://clojurians.slack.com/archives/C03RZGPG3/p1554345353175300 @seancorfield @nathantech2005 I'm the author of a Slack (and IRC) bot called Yetibot written in Clojure that offers this capability (and many others). I've been thinking about bringing it up here to see if there's interest in running one here. Another potentially relevant/useful feature is viewing and searching Slack history directly from Slack or via its web dashboard.
Looking in the docs, I don't see karma as something built in? Also, it looks like we'd have to find someone/somewhere to host the bot (for free) in order to add it to this Slack?
karma command was added by a contributor a few months ago and i haven't documented it yet. i'll add some basic docs today or tomorrow.
yes, we'd need somewhere to run it. I currently run the public instance (dashboard at http://public.yetibot.com) on a 1GB Droplet that's donated by DigitalOcean. i'm running a postgres database and yetibot instance on the same droplet. its Slack instance only has 80 members, so much less traffic than Clojurians.
LMK when the docs are updated so I can put them in front of them Admin team -- and also see if someone has spare capacity to host the bot.
I would just make sure any bot is secure though. API's are prone to security flaws. They just recently found a remote shell in a super popular library that had gone un noticed for 3 years. Someone put an eval in the code which called a cookie. I cannot say the library name in order to protect people's reputations.
And the larger your friend network, the more "trusted friend" tunnels you can build for anonymization
I am afraid to accidentally down illegal content just from reading an unsolicited message
Because whaysapp is p2p encrypted... so all kinds of illegal stuff gets through
yeah.... I mean, cars can be used to do illegal stuff... Do you want twitter driving your car too? I don't buy the argument
I think it'd be good to build a version of i2p on it... but the the fact that most webrtc clients tend to point to Google's stun servers is worrisome
How does one handle dealing with levels of nested code? I was wondering about that this week.
Yeah, the problem is async's inversion of the call graph. Makes it harder to reason about
I’m keen towards Bacon js in ClojureScript for organizing async code, but I’m sure core.async would work well.
Now that nodejs is getting webworkers, I'll probably crack that project back open an start porting it there