Clojurians Log v2

We've gone underground because we couldn't deal with the large influx of new people

But seriously, maybe this is something for @neumann to ponder about :)

One answer could be that Clojure people don't hang around Stackoverflow that much and ask questions elsewhere

I did notice that we got left off this year, even though Clojure has been one of the most loved languages many times, including last year!

It’s something on my list to follow up on. I want to do whatever I can to get Clojure on the list for next year.

I think Slack is amazing for getting help in the moment, but questions answered on Slack aren’t very discoverable via search engines. Stackoverflow is stronger in that regard.

yeah there's less than 1 clojure question a day on SO so i'm unsurprised it's not included

Yeah, I suspect it’s related to activity on the platform.

I think clojurians slack is the best community I've personally experienced, but in a strange way its domination might even be a net negative for the perception and continued growth of clojure. And this isn't specifically about slack, the same would have been true with something like zulip; what I mean is such platforms in general in comparison to traditional forums, reddit, stack overflow, etc. that tend to rank a lot higher in search engine results. The vast majority of any userbase of a technology will be "lurkers", those who are happy enough to almost never engage with the community, except for maybe upvoting something they find cool or useful, searching for an answer they expect has probably been answered countless times before, and actively engaging only as a last resort. Clojure is the only tool I use for which the first place I look at for answers or recommendations is the search function within a closed platform that I need to be logged in to. There are of course benefits, and I think I've comparatively participated more as opposed to being a lurker as with most other tools/languages I use, but I think for those that aren't already "sold" on clojure, a more balanced distribution between slack and things like forums/reddit/SO would leave a better impression.

This is something that's been on my mind for a while since I discovered that the Slack export stopped working. I'd love to have a way of lifting knowledge out of Slack and make it discoverable on the web. It would be fine with me that continuing the discussion would be in Slack. One crazy idea I've had so far is: flagging a thread as "public" would cause that whole thread to show up in a web-searchable Q&A site, but it's read only. You want to join in, then you join Slack and continue the discussion on the thread in Slack.

There used to be this https://github.com/GaiwanTeam/clojurians-log-v2

Yeah. Back in August I was considering trying to get sync going again. Then I got super busy with Clojure South and all the stuff I worked on for the Conj.

I also think the lack of big open source projects might be a factor. I am sold on Clojure, so I just look for other ways to learn, but advocating clojure to others without a few showcase projects is really hard. I'd be happy to be proven wrong of course;) Also there's no Django/Rails which makes sense once you're into Clojure, but it certainly doesn't help mitigate that first impression of Clojure being "esoteric"

Maybe, it isn't the problem of clojure community but people overall cares less stackoverflow https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/ The high quality reflection comes back to the Blog. The repeated questions are answered by search and LLM. The instant requests are warmed by community answers.

Since I started using clojure 6 years ago I've completely stopped using stackoverflow so maybe people in community don't care that much about putting their data in.

> Lifting knowledge out of Slack and make it discoverable on the web. > This is interesting @neumann I like to be of some help on this, to my capabilities. I keep this in my backlog.

When said "knowledge in Slack" 1. What do you refer to; what are the channels, formats, resources? 2. What are ways of knowledge sharing, asking questions, getting help, here in slack. (I'm new to the community)

i've sometimes wondered if we should be coordinating stack overflow questions/answers from slack, lol

that's not a bad idea

ask a question on slack and SO, link the SO in the slack thread, then others can post answers in the SO thread as desired

it's doubling up the work, but might help clojure look more active and makes the answers public

I used to be pretty active on SO answering (and asking) clojure questions, I don't know exactly when this faded.

I almost never visit the site anymore

I guess this Slack has pretty much taken over its role for me

How is the discoverability here in Slack for old content? & https://clojurians.slack.com/archives/C03RZGPG3/p1763978896871039?thread_ts=1763828521.078069&cid=C03RZGPG3

Discoverability wasn't great until this Slack got long history search. Discoverability outside this Slack isn't great either. There used to be Clojurians Log which made chats available on the internet but it's not maintained anymore.

I guess as Clojurians we could maintain a similar thing to SO in Wiki-form or http://ask.clojure.org (TBH, I don't find the UX of that website fantastic), once questions here are answered. But when questions are answered and people are in a rush, they won't maintain such a thing

Maybe that is what an LLM would be good at though, summarizing a thread. Slack could make this available as a feature maybe, so you can download a summary of the Q/A and post it on the internet

For what it's worth, I've been exploring this problem myself, but from a slightly different angle. I'm trying to take two separate instances of threaded discussion data (e.g. slack discussion threads and GitHub issue threads) and correlate them and merge all the context together. Maybe identify duplicate topics. Etc.

But I agree that the "turn slack into a knowledge base" is important as well.

There's something to be said for every question having a URL.

Absolutely.