Fate of Io is hearby re-launched.

It has been a long time (over a year) since serious work has been done on Fate of Io. At least, by anyone other than Dev and Temporal. However, it is time to change that. With the new v5 web site up, tested, and running, we're ready to get back in business.

Check the current tasks forum for things to work on. More tasks will be posted soon, but a few are already there and ready to go. Remember to check back daily for updates.

Weekly meetings will take place in the chat room on Saturdays at 1 PM Pacific time (4 PM Eastern, 9 PM UK), and will continue as long as we feel necessary. This time is open to change if important contributors can't make it.

We need more people! If you know anyone who would make a good contributor to Fate of Io, please let them know about us. If you know any good sites to post links to Fate of Io please consult with Dev or Temporal before posting. We want to advertise on such sites, but we want to make sure to do it tactfully. We will want to review exactly what you intend to post before you post it. Thanks.

That's right. This is now a release candidate. That means I have no further features to implement and I know of no bugs which I care to fix. If you can think of any features you'd like to see or find any bugs that need fixing, please post them below.

In the meantime, I am working on porting Evlan to FreeBSD, after which I will be able to set up the site at a professional FreeBSD hosting service.

I think we only lost, like, two posts this time, as I had saved pretty recently... In any case, this time I found and fixed the cause of the crash right away; it was pretty straight-forward.

Activity tracker and user list implemented (see navigation box, left). Neat image-based decorations provided by Dev.

Well, as you might notice, several comments are now missing from yesterday's news post. This is because the server just crashed, and I had to restore from yesterday's backup.

Unfortunately I still don't completely know why it crashed. I have it narrowed down to a pretty specific area, but it'll take careful examination of the code to find out what exactly happened and fix it.

The good news is that the server ran for over a week without a hitch before that. And that was on my first attempt at real-world usage, so that's pretty damn good, IMO. Clearly the crash bug that occurred is very rare, so it probably won't happen again before I manage to find and fix it.

More good news is that restoring from backups works flawlessly. I've been rather uneasy about that whole system since it's very complicated, but this was by far its toughest test yet, and it had no problem. So, yay.