Clojurians Log v2

:thumbsup:

Picking up on the #announcements topic: 6mo after we agreed in tightening its scope, I'd say that the effect has been visible, and that people have picked up this scope fairly quickly. It also helped when at some point its desc was set to Project / library announcements ONLY. The only (somewhat) frustrating point for me is when a same library is repeatedly announced a bit too often. Although it doesn't come across as spammy, it really resides in a grey zone (are you informing me of updates, or promoting by repetition?) Like 6mo ago, I still think some orientative rate limiting could be established. Verifying it can be easy: * I sense lib foo pops up quite often * I grep for it in the <http://clojurians.zulipchat.com|clojurians.zulipchat.com> archives * I can verify it's being announced every e.g. 10 days ...Personally I'm not interested in performing this policing at all, but I'd have faith that if the limit was established, people would follow it quite organically. One could always dig up the Zulip archives as a last resource :) Also, specifically, no need to name-and-shame. There are a lot of clojurians, obviously with different sensibilities around what is acceptable promotion.

scraped clojars stats, looking good based on ring downloads.

😂 or somebody has forgotten to configure their m2 cache on CI

@vemv The guidance was given that a library shouldn't re-announce a release if it's previous release was still visible in the limited history available in #announcements -- I had a private word with one person who was violating that and they apologized. Feel free to respond to an announcement in a thread asking them (politely) not to post so frequently about the same library if their previous announcement is still visible in the scrollable history on Slack. There's no reason that burden should be forced on the Admin Team here as you seem to be suggesting.

"I'm not interesting in performing this policing at all" -- yet you've brought this sort of thing up several times now. If you're not interested in helping, please stop complaining about how others do it.

Thanks for the reply. Happy to see I'm not requesting something too misaligned. > The guidance was given that a library shouldn't re-announce a release if it's previous release was still visible in the limited history available in #announcements Could this be stated in the About section of the channel? So that one can point to it etc > If you're not interested in helping, please stop complaining about how others do it. I'm interested in helping maintain a healthy and engaging community. Personally I don't want to be either a 'human rate limiter' or an antagonistic figure. Something as simple as setting some visible rules could help. ps - IIRC the scrolling limit is per-device (maybe even per-user?). So setting that as a baseline might cause misunderstandings. An approximate rate limit would seem more accurate

I believe there is a limit on free Slack communities, like Clojurians Slack, to something like 10,000 total messages of visible history, across all channels and users. I haven't checked whether that differs by user, or by device, but have no evidence for or against on that.

Well, a small amount of evidence for, in that it has been mentioned several times by people who know more about Slack's support for free communities like this one.

I think it is awesome that Clojurians have progress to announce. Please do not rate limit it.

@andy.fingerhut The available history in a particular channel seems to differ from device to device (but overall is "a few days" due to the free plan's 10,000 message history limit).

> Could this be stated in the About section of the channel? So that one can point to it etc Sure, but a) these are editable by anyone and b) hardly anyone seems to read the About section (few enough people bother reading the Topic -- and that's always visible! A lot of people do not have the Details sidebar open at all, let alone have the About section expanded).

Thanks! I have added Please keep them occasional.. Unfortunately there's a char limit over this About field, so I cannot describe the exact limit ("scrollable area") without erasing other bits. I'll keep the described limit in mind and will make an occasional/polite effort at reminding about it.