I apologize if my frustration around this is also frustrating you - Not my intent.
We are just trying to give constructive feedback as we love the forum and want it to get better.
I do notice that my answers don't seem to be heard, hence the need for repetition. That might be what you interpret as frustration.
Feedback is great, but when we answer there's not a lot of use in repeating the question. I understand from your many requests that you feel strongly about this, but really all I can do is repeat our stance. If there were black-and-white answers, we would give them to you.
The reason I wrote "and that's where we'll leave it" was to attempt to convey that as far as this specific issue, there's nothing more to discuss right now.
It does feel like a bit of an oxymoron to cite "experience has shown us" but in the same sentence say "I have no idea" when it will die down....Shouldn't the experience being used to cite the decision to do nothing be able to inform when the X fever will die down, or at least be guessed at based upon previous releases over the years? (the experience part)
We're not doing nothing, we're waiting to see how the situation evolves. No, I can't predict when this specific wave will die down. I can however say that it's still early days. I can - and have - told you that we have experience in evaluating forum structure in relation to new products, and that we aren't ignoring it this time. I and others have pointed out that this is not a new phenomenon; there's always a surge when a new product is announced. Often, it dies down. Sometimes it doesn't. Hence the wait and see attitude.
Anyhow - It's actually different points now. The X (or whatever latest phone) dying down is separate issue from the value of breaking up the iPhone section into relevant models/generations.
It's fine to discuss if we're moving on from the previous issue now.
I still wonder about requiring that thread titles discussing a certain model label the thread as such. That alone would help immensely!
I agree. This unfortunately doesn't work. Users either don't bother or forget. If it's required, lack of compliance generates many extra post reports and a much greater need to edit thread titles, at the expense of more pressing duties.
I've traditionally been in favor of thread prefixes. I think they're a good compromise between new sections and the need to categorize groups of threads. Sadly, experience has shown us that users don't bother using them. And if they aren't used consistently, they don't help. Requiring them before a thread can be created is one possibility, and the relative value needs to be balanced against the extent to which the extra step irritates users (and it does irritate some - we get feedback about this as well).
We're discussing this now.