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 个赞
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 个赞
Yes all are deployed.
1 个赞
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 个赞
由于 此解决方案 似乎 延续了性能问题，在达到 1 万条消息限制后，是否还有 其他方法 来保持该 TL3 聊天室（特指此例）的活跃？
我只是在寻找一份权威的“操作指南”，以便指向 我的社区 ¹ 的版主们，避免 拖延问题 继续引发原有问题，因为 Discourse 平台最终会为所有 TL3 聊天室遇到此问题 ²。
因此，如果在旧的 TL3 聊天室中发布一条链接，邀请所有当前和未来的 TL3 用户加入新的聊天室，并额外提供 1 万条消息的限制，将对 Discourse 平台 和 各位版主都大有裨益……
注 1：没错，2020 年复活节兔子送给 Discourse 的复活节礼物就是一个被冻结的 Manjaro.org TL3 聊天室……
注 2：ITIL 对“问题”的定义 = “多个具有相同根本原因的问题”
请注意，聊天功能将在 Discourse 2.9 中作为官方功能发布，尽管是测试版（并且可能默认关闭）。所以，如果你感觉需要……速度……（https://www.youtube.com/watch?v=odMO18xcVPs），也就是快速聊天，我们很快就会满足你的需求！
5 个赞