Clojurians Log v2

It is actively being worked on, as we speak. It was broken partly by Slack changing their APIs.

Nice, where can I follow the progress?

The coordination is being done between volunteers who maintain the log/mirror bots and the admins in a private channel. There's nothing to follow really. We'll make announcements once it's all back up and running.

ok, it'll be nice if the future one had the data queryable via API than just a static site.

There are a lot of moving parts but the integration with Slack (logbot) just copies content from here to JSON files. Those are then used to build the log on ClojureVerse's servers. You could post a question on ClojureVerse about having some way to search via an API but you'd be asking volunteers to do a bunch of free work 🙂

See https://github.com/clojureverse/clojurians-log-app/blob/main/docs/Background_History_Context.md

The Admins here do not support or maintain the bots. We just work with those maintainers to provide them the access etc they need to get them working.

Thanks Sean, how does one qualify to get access to the slack webhook API? I guess gdpr stuff, excision requirements should be an agreement the webhook access requester has to make? The slack is a wealth of clj info and I'd like programmatic access to it than sifting manually through slack or a website.

In fact I'd be fully willing to build a queryable public API and pay for the servers if given the historical dump and webhook access.

Although we've granted logbot and zulip-mirror-bot those permissions in the past -- years ago -- when we expected to lose sponsorship, we do not generally grant other integrations, in case we end up back on the free plan. We do not want "everybody" to start building integrations against this service.

Like I said, if you want to work with Arne / plexus and build a query API against the logbot data archives, you should ask on ClojureVerse whether he's interested in working with you on that.

And, yes, GDPR and other privacy issues are why we limit API access.

Right, I’ve messaged one of the maintainers earlier but didn’t get a response back. I’ll try the clojureverse-ops channel and see if there is any interest in it. But it’s a bummer we don't already have programmatic access and the doc doesn’t seem to have any notes around it. Thanks.

Like I say, we don't want folks building arbitrary "query" integrations against Slack itself. There are the two real-time exporters -- logbot2 and zulip-mirror-bot -- and those maintainers may be amenable to a queryable API against the backing data they export (although I think zulip-mirror-bot just goes straight into Zulip, so ClojureVerse/logbot2 may be your only option there).

Just remember all these people are volunteer maintainers so they are already doing a lot of stuff for the benefit of the community and may also not want arbitrary "query" integrations against their systems either.

And we're not about to offer export capabilities to "anyone"/"everyone".

I’m clear on the “everybody” point. Well I’m trying to volunteer here too and I think programmatic access to pretty much static knowledge around clojure might definitely be useful to many. It's not costly as a cdn with infrequent invalidations will front most of the traffic. Anyway I’ve posted on the clojureverse channel. All I wanted is for the knowledge to be queryable more simply and efficiently and willing to volunteer via clojureverse if they're fine with it.