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개의 좋아요
이 솔루션이 성능 문제를 계속 유발하는 것이라면, 10K 한도에 도달한 후에도 TL3 채팅(특히 해당 채팅)을 유지하는 다른 방법이 있을까요?
저희 커뮤니티의 ¹ 관리자분들이 문제를 미루지 않고 원래의 문제를 계속하는 대신, Discourse 플랫폼이 결국 모든 TL3 채팅에서 이 문제에 부딪히게 될 것이므로 ² 가리켜 줄 수 있는 공식적인 HOW-TO를 찾고 있을 뿐입니다.
따라서 구 TL3 채팅에 링크를 게시하여 모든 현재 및 미래의 TL3 사용자를 추가 10K 게시글 한도를 가진 새 채팅으로 초대하는 간단한 방법이 Discourse 플랫폼과 그곳의 관리자 모두에게 유익할 것입니다…
참고 1: 네, 2020년 부활절 토끼가 준 Discourse의 부활절 선물은 동결된 Manjaro.org TL3 채팅방이었습니다… 
참고 2: ITIL의 “문제(Problem)” 정의 = “동일한 근본 원인(Root Cause)을 가진 여러 이슈”
해결 방법은 실제 채팅을 사용하는 것… 그렇지 않으면 영원히 역류에서 헤엄치게 될 것입니다 
메가토픽은 매우 위험하다는 점을 많은 이유에서 잊지 마세요.
3개의 좋아요
채팅 기능이 디스커스 2.9에서 공식(비록 베타 버전이며 기본적으로 비활성화될 수도 있지만) 기능으로 출시될 것입니다. 따라서 속도를 원한다면.. 속도.. 속도를 원한다면, 즉 빠른 속도의 채팅이 필요하시다면, 곧 그 필요를 충족시켜 드리겠습니다!
5개의 좋아요