Awesome! Thanks for all the replies here. I am glad I started this topic, to find out how people feel about this.
I may be wrong about this, but my own feeling from my experience in recent months has been that the Support category is different from the other categories we have currently. People come wanting to solve a problem right now and nearly always the problem is very specific to their own circumstances. If the topic does not get resolved reasonably quickly then they lose interest and move on, or become impatient and ask again in other topics. Meanwhile the support category can become littered with unanswered questions. Other later travelers then bump them to ask their own slightly different questions which would be better off in a new topic.
This is different from the other categories where we do allow and encourage open ended topics. When people post topics to Support that belong in other categories, e.g. because they are actually a Feature request, we can move them. Or if someone is looking for help with creating a plugin, we move it to Dev.
So one way or another Support topics that go unanswered or where discussion peters out need to be followed up on so they can be brought to resolution eventually. I think adding a reply a week or two later and then setting them to close 30 days after the last response seems like a reasonable way to make sure that happens.
What I am hearing here is that the automatic closing of all Support topics 30 days later is probably not the right approach after all, given that we often move them which then means we have to remove the timer. But I still think that we should aim to eventually close all Support topics.
So I’ll turn off the automatic setting for now but keep adding the timer in cases where I think it makes sense. If you notice I have set a timer on a topic where you think I should not have, let me know and the reason why.