I think moratorium means moratorium. Six months before we bring the whole painful topic up again, win or lose.
If six months should win.
As is only right.
We open it up, we talks the talk, we votes, we shuts it down. This thread is to free up Bureaucracy for daily details as we hammer out the Big Issues towards a vote. Open only when a proposal has been made and seconded according to Buffista policy (Which we voted on!). If this thread is closed, hie thee to Bureaucracy instead!
I think moratorium means moratorium. Six months before we bring the whole painful topic up again, win or lose.
If six months should win.
As is only right.
That can't be the case for thread creation, surely -- are you saying that every six months I can say "I still think a Movies thread is wrong, and we should shut it down"?
Not that I would...
That can't be the case for thread creation, surely -- are you saying that every six months I can say "I still think a Movies thread is wrong, and we should shut it down"?
Oh, I think so. And really, I think it should be that way -- but then, I'm an anti-proliferationist. But think about it -- if we only ever open threads and never close them, we'd have a zillion threads eventually, right?
That reminds me, people seem to think, correct me if I'm wrong, that having more threads is inherently a Bad Thing in terms of bandwidth and board stability.
It's not, I believe, and people are mistaken about this just because of what they believe caused the recent outage/database problems.
It's not, correct me if I'm wrong, ita, that creating more threads causes database problems, but simply that experience shows that having more threads means there's more traffic.
The outage wasn't caused by having too many threads, in other words, though it's logical to assume that our increases in traffic are due in part to having more threads.
My understanding is that the Recent Outage wasn't because of bandwidth at all, but I do believe bandwidth could become a problem at some future point, and I also believe that having more threads means we use more bandwidth -- see that Natter hasn't slowed down, even with new threads around.
None of which has anything to do with the matter at hand.
Go 6!
I must have said that wrong. If something wins, no one agitates against it for X months. If something loses, no one agitates for it for X months. That's what I recall from bureacracy. Any decision can revisited after the moratorium.
clarifying because this is part of what made me lean toward 6.
So perhaps (it seems, to my mind) the ballot would most fairly look like this:
I actually think that would unfairly penalise 6 months. See, if we go with that option, 6 would need to get over half the primary votes to win. The other two options only need to win a preferential ballot.
It's not, correct me if I'm wrong, ita, that creating more threads causes database problems, but simply that experience shows that having more threads means there's more traffic.
Yes. The table of posts is what Hostrocket says is too large.
I can't figure if you're correcting me because I'm wrong or saying I'm right.
There's one central table for all posts, which are just marked as belonging to a thread, rather than a table for each thread?
But didn't somebody run numbers that suggested that there was a strong causal correlation between numbers of threads and numbers of posts?
That is, you have 3 threads, you have 3000 posts; you have 4 threads, you don't have 3200 posts, you have 4000. (Numbers pulled out of Stephanie's frog-whistle.)