Why not just put something in the FAQ about changing the post # in the URL?
'Lineage'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Man, I'm waiting up to 4 hours with IE, and still no error.
Are you still on the board in another window, though?
Nope. I tried overnight and everything.
This is going to take some puzzling out.
I don't know if it's my connection or the site, but I'm on a T1 line and I've been getting timed out and having trouble connecting for abou half an hour (since 11:30 a.m. EST).
Host response time is glacial this morning.
Same thing is happening to me. It's taken me several tries to get to this page. No idea if post will take...
I can't pinpoint if it's a net congestion problem (other non-Hostrocket sites are dicking with me this morning as well) or a more localized one (since the server itself seems healthy).
It's definitely a hostrocket network congestion problem. Doing a traceroute to www.buffistas.org shows that the congestion starts as soon as the packets hit the hostrocket network:
$ traceroute www.buffistas.org traceroute to buffistas.org (66.162.73.252), 30 hops max, 40 byte packets . . . 6 gi4-1.msfc1.tlw.nac.net (167.206.16.130) 13.383 ms 11.317 ms 13.8 ms 7 gi4-5.msfc1.nyc.nac.net (209.123.11.229) 12.472 ms 12.85 ms 14.931 ms 8 fast0-0.iix-igr01.nycl.twtelecom.net (198.32.160.35) 11.587 ms 12.731 ms 16.544 ms 9 core-01-so-2-1-1-0.nycl.twtelecom.net (66.192.240.61) 12.734 ms 12.824 ms 17.612 ms 10 dist-01-so-3-0-0-0.bngh.twtelecom.net (66.192.240.2) 20.583 ms 20.608 ms 22.166 ms 11 dist-01-so-3-3-1-0.roch.twtelecom.net (66.192.240.6) 24.412 ms 26.309 ms 24.203 ms 12 dist-01-so-3-0-0-0.alby.twtelecom.net (66.192.240.10) 21.472 ms 22.337 ms 22.98 ms 13 hagg-01-ge-0-3-0-0.alby.twtelecom.net (66.192.240.178) 21.132 ms 21.234 ms 22.114 ms 14 * nycp-rt-hr7200-1.hrnoc.net (66.162.65.2) 68.104 ms * 15 * * 66.162.64.113 (66.162.64.113) 70.948 ms 16 * * 66-162-73-252.gen.twtelecom.net (66.162.73.252) 72.058 ms
My samspade.org traceroute has the congestion starting from the twtelecom.net part of the path.
So, what you're saying is, I need to go Minear on the host?