Unexpected Slashdot Downtime 219
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.
How about moving to a better news system? (Score:2, Insightful)
Things I hate about
1. Goddam CSS design
2. dupes
3. slashadvertisement
4. bad summaries
5. lazy editors
Re:How about moving to a better news system? (Score:5, Insightful)
Re:If it was planned downtime... (Score:3, Insightful)
And exactly HOW were we to read this story that was posted on the website, while that website was down? You have suggested yourself into a circular argument. Most normal people (which includes
Re:Modernization? (Score:3, Insightful)
This is why slashdot was so reluctant to use
That all said, IPv6 wouldn't break compatibility with existing IPv4 users, and would be a fantastic gesture to the internet community at large. Of course, if IPv6 support would cost a mint to implement, or force them into a "less desirable" data centre, it wouldn't be practical.
Re:Modernization? (Score:3, Insightful)
What are the reasons for holding back? Well, the main one is that the current database holds the data in ISO-8859-1 (probably) and would either need converting or at least to have some kind of migration strategy (extra column for the encoding?) which could be rather messy.