AjaxLife Blog

[01:26 BST] AjaxLife is up again, running version 0.3.7. If you see a checkbox labelled “(loading)”, please clear your cache and try again. Thanks to a backend change made in 0.3.7, this should not be necessary for the next version (probably 0.3.8).

[00:46 BST] S3 is now up. However, AjaxLife remains down for work that will decrease the time required for updating in the future, and for an update to 0.3.7.

Due to a failure with Amazon’s S3 storage service, AjaxLife is down until they fix it. This is the same reason that LL’s website is broken and half the rest of the “Web 2.0″ thing is screwy. Apologies for any inconvenience. Please moan at Amazon instead.

AjaxLife is currently down for updating to 0.3.6. This version is less buggy and has improved inventory support. More details will follow.

(Anyone wondering why I always make these posts just before I do an update: because the system redirects new requests to ajaxlife.net to blog.ajaxlife.net when I set it to update mode.)

AjaxLife is currently down for an update to 0.3.5. Release notes will follow.

[17:30 GMT] Update complete. We’re back (and unblocked)! Please clear your browser cache and try again if you receive a message to the effect of “A C# exception was caught: array index out of bounds.”

[17:17 GMT] Final testing has passed. We’re now waiting for the deploy script to update the servers. We should, hopefully, be back up shortly. Release notes will be posted in a separate post.

AjaxLife is going down for an unscheduled update to 0.3.4. The version was going to be released in a week or so, but is going out now due to having the property of bypassing the libsl block currently in place. It was actually almost released last week, but failed final testing. Those bugs have been fixed now, so it’s just being released without a bugfix/enhancement that was planned.

We’ll be back as soon as possible!

[17:32] We have resolved this issue. Please clear your browser cache and retry if you receive a message to the effect of “A C# exception was caught: array index out of bounds.”

[UPDATE] See this post for information about the solution in progress.

Linden Lab have apparently blocked AjaxLife from accessing Second Life. Again. It appears to once again be a generic libsecondlife block (although certain programs - e.g. TestClient - are unaffected).

We seem to be blocked again. I’m assuming this is a general libsl block.

Grr.

And now we’re fine.

[01:33 GMT] Open again!

[01:26 GMT] Running the startup scripts. AjaxLife will reopen itself when the script has finished (in about ten minutes).

[01:06 GMT] Problem resolved. Deploying new server. Going to get a drink as well; this script takes a while.

[00:42 GMT] Hit a problem in testing that didn’t (and continues to refuse to) appear in the preview environment.

[00:27 GMT] Logins are disabled.

AjaxLife will be down for an upgrade to version 0.3 shortly. Please be patient. And such.

[19:17 GMT, 3/3/08] And we’re unblocked!

[18:54 GMT, 3/3/08] And we’re blocked again!

[20:15 GMT, Wednesday] And it’s unblocked again. Theory: it’s blocked between 6 and 8pm GMT.

[18:32 GMT, Wednesday] And it’s blocked again. Please, make up your mind?

[20:37 GMT] Okay, no idea what happened, but it seems to be back now… fingers crossed.

There appears to be an IP ban on AjaxLife’s login proxy (which is needed to fix issues with LL’s login server). As such, the service is down until further notice. I have no idea why Linden Lab have decided to close AjaxLife.

I have no idea if this is temporary, accidental, intentional, etc.

[22:44 GMT] We’re back!

Release notes:

• Hebrew and Japanese translations added in llDialog and llRequestPermissions dialogs
• IMs scroll down when someone’s typing to show the “Some Person is typing…” message
• Login and application are now on the same webpage (”Loading subsystems” no longer exists)
• Login screen can be translated, pending translations of the new text
• Changing the language in the drop down box immediately changes the language in use.

Old status announcements