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 curtida
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 curtidas
Yes all are deployed.
1 curtida
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 curtida
Como essa solução parece continuar o problema de desempenho, existe alguma outra maneira de manter o chat TL3 (especificamente aquele) ativo após atingir o limite de 10 mil posts?
Estou apenas pedindo um COMO-FAZER canônico para que eu possa direcionar os moderadores da minha comunidade ¹ sem adiar o problema e continuar com o problema original, já que a plataforma Discourse eventualmente enfrentará essa questão em todos os chats TL3 ².
Portanto, uma maneira fácil de postar um link no antigo chat TL3 convidando todos os usuários TL3 atuais e futuros para o novo chat, com um limite adicional de 10 mil posts, seria benéfica tanto para a plataforma Discourse quanto para os moderadores por aí…
Nota 1: Sim, o presente de Páscoa do Discourse do coelho da Páscoa em 2020 foi um chat TL3 do Manjaro.org congelado… 
Nota 2: Definição do ITIL de “Problema” = “Múltiplos problemas com a mesma Causa Raiz”
A solução é usar um chat real… caso contrário, você vai ficar nadando contra a corrente para sempre 
Lembre-se de que megatópicos são incrivelmente perigosos por tantos motivos.
3 curtidas
Note que o chat será lançado no Discourse 2.9 como um recurso oficial, embora beta (e possivelmente desativado por padrão). Então, se você sentir a necessidade… a necessidade… de velocidade, ou seja, chat rápido, atenderemos a essa necessidade em breve!
5 curtidas