Unexpected Slashdot Downtime

Netcraft confirmed it ... Slashdot was dying for several hours (along with SourceForge, which shares a corporate overlord and router). Some planned downtime from our provider apparently didn't come back up quite as planned. Sorry for the inconvenience. On the upside, we're moving to a new network and hardware soon, so the site should be much faster and more stable rsn.

I thought it was a wider net outage

[suso]

At first, I was thinking there was a wider internet outage because Google was having problems this morning and so was MSN.. But I guess not.

If you look at this website [internetpulse.net] it shows that there is some issue between SBC and Cogent.

Feds installing user tracking software on /.

[Reality Master 201]

I hear the FBI was installing software to track Slashdot posters. Is that true?

Re:Please update the FAQ, too!

[Anonymous Coward]

Did you miss the story about Slashdot's hardware [slashdot.org] and the story about Slashdot's software [slashdot.org] last year?

Re:Modernization?

[jc42]

Will this new network include IPv6 access, or will ./ remain in the 20th Century?

Actually, the main thing that would make for 21st-Century cred is accepting UTF-8 text.

I've had a couple of posts recently on topics where it would have been better to use Chinese or Japanese characters (though not very many of them). I had to settle for pinyin/romaji instead, which isn't really ideal. The ability to correctly include text in non-Western language is of growing importance in the world, even to people whose primary language is English.

Of course, there are somewhat similar sites in other parts of the Web that work in languages other than English. The real problem is the barrier between the English-speaking world and the rest of the world, caused by our ongoing inability to include text in other major languages inside our English text, even as small examples.