The error messages here seem to be wrong.
This is a long public topic on my forum which has just locked itself but it’s referencing the 200 post limit that applies to a PM topic.
1 Like
Yep, that was a bug that we fixed – it swapped the 10k and 200 (now 500) numbers unfortunately. @sam we should redeploy to reach the sites that have the bug. Very, very unfortunate bug there.
4 Likes
Yes all are deployed.
1 Like
So I’m a bit confused. As originally, I thought the plan was two settings for PMs, one for regular users and one for staff, now it also affects public topics?
My concern with the public topics, although, a topic being over 10,000 posts is likely to not be on its original topic and more than likely shifted a hundred times over, but rather it kills any discussion immediately. Just bam, shuts it down.
However, I do like that it can be disabled. As we do have a few that are over 10,000 posts, but they are quirky fun related topics, not serious discussions.
I am still uneasy about adding a separate setting for staff here. It kind of feels like cheating.
Regarding public topic, this is a temporary measure.
Yeah we can defer on the staff override there for a bit.
Yeah, that makes sense. I honestly don’t see the big need for two separate settings, was just trying to figure out how it went form 2 settings regarding private messages to 1 public 1 private, but your second statement, answered that.
I half wonder if a better approach would have been to set Auto-Close to an hour once it hits the threshold, so people can quickly finish up whatever discussion they had on-going and not get a it is shut down response. However, many this is being done in sideqik in which case there might be a “time period” that will still run letting it exceed 10,000 posts for a bit before it flips to close. I may need to play with this feature a bit by setting it to a relatively low number to see how it behaves.
It would be nice to document how it behaves, be it sideqik (and how often the job runs) or immediate based on the post that forces it to exceed the threshold.
1 Like
As this solution seems to continue the performance issue is there any other way to keep the TL3 chat alive (that one specifically) after the 10K limit has been reached?
Just asking for a canonical HOW-TO I can point the mods from my community ¹ to without kicking the can down the road continuing the original problem as the Discourse platform will run into this issue eventually for all TL3 chats ².
So an easy way of posting a link in the old TL3 chat inviting all current and future TL3 users over to the new chat with an additional 10K post limit would be beneficial to both the Discourse platform and the mods out there…
Note 1: Yup, the Discourse Easter present from the Easter bunny in 2020 was a frozen Manjaro.org TL3 chat room… 
Note 2: ITIL definition of “Problem” = “Multiple issues having the same Root Cause”
The solution is to use an actual chat… otherwise you’re going to be swimming upstream forever 
Remember that megatopics are incredibly dangerous for so many reasons.
3 Likes
Note that chat will be released in Discourse 2.9 as an oifficial, albeit beta (and possibly default off) feature. So if you feel the need … the need… for speed, aka rapid-fire chat, we will meet that need soon!
5 Likes