Goodbye Diary-X

There's already a thread on this in the forum, but the more I think about, the sadder it all seems - and I think it deserves some front page attention.

Diary-X, if you don't know, was a website - one of the original online journalling tools, a little like Livejournal or Blogger, but with a simpler emphasis on journal writing rather than the link-heavy style of most blogs. Since its launch in 2000, it attracted over 120,000 members in six years, in spite of its entirely non-profit nature and limited admin resources. It inspired some great writing, and was the creative home of many thousands of people - but two weeks ago, all of this was lost.On February 24th, it was announced in a stark message on the site here that the failure of one hard drive had resulted in the loss of the entire site - and every single diary account and post. The only existing backup was two years old, and didn't contain any posts either. The collective work of 120,000 people over the last six years had just blinked away in an instant.

It's a very sad event and a real digital tragedy. As a one-time DX'er myself, my heart goes out to everyone who lost their work of the last few years - and as the mug behind this place I can't help but feel for Stephen Deken, Diary-X's long suffering creator, for the pain he must be going through - to have built the place up for six years and then see it all dissappear for want of a backup.

Goodbye Diary-X, and good luck to all of its survivors.

Re:Goodbye Diary-X

While not on the same scale as diary X, MinorCeleb has been broken for some time now.

I've looked in the file manager, and everything is still there, so it looks like there's just a problem somewhere.

If someone understands the error message that's currently displaying on the front page, and knows how to fix the problem, I'd be very grateful!

Tim's picture

Re:Goodbye Diary-X

Tom, basically that message is telling you that the database is down/inaccessible/ broken in some way. it could be that your host's database server is down, or it could be that your particular database record is damaged in some way, or it could even be that the database is fine but postnuke can't get to it because it has the wrong password (ie, the config.php file is missing or corrupted in some way).

the first thing to do is log into your host's control panel, and try to use phpmyadmin (or similar) to look at your database. it should be fairly obvious if it's broken (it won't be able to open it), missing, or has been emptied in some way. if you're not sure what you're doing, you could also contact the host and ask them what's going on - you had a working site a couple of weeks ago and now something has changed on the server to affected that. they may have a backup they can restore, or at least be able to reboot the server/check the database (or "mysql" server" is running okay.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.