The new forums will be named Coin Return (based on the most recent
vote)! You can check on the status and timeline of the transition to the new forums
here.
The Guiding Principles and New Rules
document is now in effect.
The server is too busy at the moment. Please try again later.
Posts
Honestly, if they don't go through the trouble of working it all out ahead of time, there's going to be even more complaints and issues and unknowns cropping up; not from the hardware, which by then should be stable, but rather the software.
Have some patience, Rome wasn't built in a day.
OR, and I'm just throwing this out there, maybe they're doing their job, which is to make sure a service is, you know, serviceable, before they send it public. Instead of being like a lot of the companies they pan, who toss a new service or product out for use, completely unaware of issues that they would have known about and had time to solve if they'd tested it more thoroughly.
We have some of the finest geeks in the industry working on this. They're trying to release a product they would want other companies to release to them, and one they can reasonable proud/sure of.
And yes, I'm aware there's a strong chance you're being sarcastic. Doesn't really belong up here in the Circus, though.
I'm hoping that by "strong chance" you really meant "absolute certainty". The only possible way he could have made it more obvious would have been to use an actual [sarcasm] tag. Unless you think there's even a slight chance that he literally believes that the mods have decided to keep the new board for themselves?
I'm actually starting to think that they're not fixing it because it probably makes their lives a whole lot easier. I mean, the post volume must have dropped 60 or 70%. That's a crapload less garbage that has to be moderated. [/sarcasm]
And yet, as I just said, and you quoted, posts like that don't really belong here in the Circus.
Last ETA was "open beta in about 2 weeks", and that was 4 months ago.
At this point, I'm inclined to think Ramius has been handed the torch when Alpha left and now he's trying to figure out what the fuck is going on before he lets anyone publicly test, so we're basically at square 1.
the potential for mischief....
nah i'd rather not, i feel bad for the admin and the mods though.
The forums are already being tested by the moderators. They aren't going to be publically tested, they never were. Go ahead and keep your speculation about things you have no knowledge about to yourself.
Now, there isn't.
There was an update on it just two weeks ago. There's a stickied thread for the new forums discussion and everything.
Whatever Ramius did it was a whole lot better than it had been the previous days.
Kudos.
I noticed at one point that if you use quick reply and server is busy, it just tells you in the box instead of going to a new page and making you lose the entire post. I really, really appreciate Ramius doing that.
If you do get the "server busy" page after trying to make a post, you can reload that page once the server is responding and it will resubmit the post data.
This depends entirely on your browser.
@gamefacts - Totally and utterly true gaming facts on the regular!
As I understand it, when the servers get busy enough, they decide to take a 1 minute break and everyone can go do something else briefly while they're on cooldown, so to speak.
Now, does changing the number of posts shown to a user at a time help or hinder the system in any way? By changing the posts shown per page from 25 to 50, we're requesting more info at a time, but aren't making requests as often.
I've found that the increase to 50 has helped because as long as I get a request through, I'm seeing two pages at once (compared to default), so I can only assume I'm missing at least some of the cooldown periods that would've otherwise been hit.
Is this a good idea? Bad idea? Completely irrelevant unless adopted by thousands of users?
The increase to 50 per page has definitely helped me with the issue, as I don't need to load as many pages to read a thread, but I used 50 per page before this problem and would continue to afterwards. Can't think of a good reason not to, to be honest. For those who don't view 50 per page, why?
This is a rhetorical question
Switching to a completely alien software and hardware platform is no small thing. Failing to get it right could mean creeping DB issues that don't make themselves known until it's at the brink of complete failure. That sort of error tends to require restoring from an ancient backup.
Constant busy messages are less irritating than daily mystery crashes that require hours of debugging.
Not talking shit
Hope this gets fixed soon!
Instead of refreshing the page, I got a server busy error.