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 me gusta
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 Me gusta
Yes all are deployed.
1 me gusta
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 me gusta
Dado que esta solución parece perpetuar el problema de rendimiento, ¿existe alguna otra forma de mantener activo el chat de nivel TL3 (ese en particular) una vez alcanzado el límite de 10K?
Solo estoy buscando una guía CANÓNICA a la que pueda remitir a los moderadores de mi comunidad ¹, sin posponer el problema perpetuar la situación original, ya que la plataforma Discourse eventualmente se encontrará con este problema en todos los chats de nivel TL3 ².
Por lo tanto, una forma sencilla de publicar un enlace en el antiguo chat de nivel TL3 invitando a todos los usuarios actuales y futuros de nivel TL3 a unirse al nuevo chat, que cuenta con un límite adicional de 10K publicaciones, sería beneficioso tanto para la plataforma Discourse como para los moderadores…
Nota 1: Sí, el regalo de Pascua de Discourse del conejo de Pascua en 2020 fue un chat de nivel TL3 en Manjaro.org congelado… 
Nota 2: Definición de ITIL de “Problema” = “Múltiples incidencias que comparten la misma Causa Raíz”
La solución es usar un chat real… de lo contrario, estarás nadando contra la corriente para siempre 
Recuerda que los megatemas son increíblemente peligrosos por muchas razones.
3 Me gusta
Tenga en cuenta que el chat se lanzará en Discourse 2.9 como una función oficial, aunque beta (y posiblemente desactivada por defecto). Así que si siente la necesidad… la necesidad… de velocidad, también conocida como chat de respuesta rápida, ¡satisaremos esa necesidad pronto!
5 Me gusta