The subversion repository at Google Code is no longer going to contain a “trunk” which is always stable – instead, it will contain whatever I ended up with after I finished working. When I feel happy enough with it to push it out to ajaxlife.net I’ll tag it in svn. The last version I had up there is currently tagged 0.0.1, and is identical to revision 34 of the trunk.
The net effect of this is far more frequent updates to the code, and less of me having to spend hours undoing stuff I did due to not having a copy of it.
Basically, if you want working code, look for the largest number in http://ajaxlife.googlecode.com/svn/tags/. If you want recent code, look in http://ajaxlife.googlecode.com/svn/trunk/. I’ll be dropping my own server code into the trunk shortly. The client code is so hideously broken it gets to be an exception until I have it fixed (which shouldn’t be that hard, really – it needs to be ported back to an old UI library, and it’ll all magically start working again).
I hope this makes people who want more recent code happy. Also, contributions would be welcomed, although this will involve digging through my mess of C#/JavaScript.
[EDIT] I’ve committed the server changed – see here for a list of changes.
Published on
13th of February, 2008 in
AjaxLife.
I have a nice survey for people to take. Please do so. You can find it here.
Responses will actually be taken into account when working on things As many responses as possible would be appreciated; it should only take a few minutes.
Many thanks to those who take it!
Published on
12th of February, 2008 in
AjaxLife.
I am currently not in a position to develop AjaxLife, mostly due to the brokenness of the internet over here, as well as time constraints. 
The bug that was originally delaying the release is now fixed, but other significant work is in progress, and the system is currently unusable (IMs broken, chat buttons floating oddly, inventory window wildly oversized, strange formatting bugs, profiles unviewable, search only shows one name at a time, windows becoming unopenable after closing using the “x”, etc.)
That sounds like a very long list, but most of it comes down to a single bug. The IMs being broken is another bug, and windows being unopenable is already fixed, but I haven’t applied this to all windows yet.
I want and hope that this will be done by Monday. No promises though.
I’m going to be away for a week. Somebody send me an email tomorrow morning (GMT) reminding me to put AjaxLife’s latest code on my laptop.
Published on
6th of February, 2008 in
AjaxLife.
[23:20 GMT] We’re back!
[23:15 GMT] Running the startup script again.
[23:04 GMT] Tested successfully, bundling again…
[22:49 GMT] Found the error: init-ajaxlife.sh: line 1: mono: command not found
[22:18 GMT] Startup script failed – it terminated the instance less than a minute after starting it. Trying to work out why…
[22:08 GMT] Watching the startup script run…
[21:44 GMT] Waiting for the bundling to finish.
[21:17 GMT] Image conversion should work now. Testing in progress…
[20:56 GMT] Image conversion is a pain. Still trying. >.>
[19:58 GMT] Running assorted tests
[19:41 GMT] Configuring AjaxLife server
[19:09 GMT] Rebuilding from scratch. 0% complete.
[UPDATE] As predicted, it’s down. Attempts to repair it are being foiled by such annoyances as lessons and wireless connections that drop constantly.
Due to accidental deletion of the manifest.xml file that goes with AjaxLife’s EC2 AMI, there is a reasonable chance that it’s going to break tomorrow and not be able to restart automatically.
I will work on this as soon as I get the chance; I’m going to sleep now (yawn).
Linden Lab make a good point – you probably shouldn’t be typing your passwords into my site, regardless of my promises that I don’t read them (which I don’t).
Then again, they’ve said that several times during AjaxLife’s lifespan, so I assume you all already thought about that. 
Published on
31st of January, 2008 in
AjaxLife.
So, it turns out that this month, against all (my) expectations, donations were actually higher than expenses – hooray!
If donations continue at this rate, AjaxLife’s continued availability is ensured (barring major world-ending incidents and/or the bankruptcy of Amazon.com and/or my death and/or…)
Many thanks to all of you. 
Also, even more thanks to the extremely generous French person. 
Published on
28th of January, 2008 in
AjaxLife.
Due to people insistently linking to the IP address AjaxLife redirects to (which changes often, thus breaking any links to it), I have changed the way AjaxLife redirects. Instead of actually redirecting you, it now uses a frame in order to maintain the URL. This means that refreshing whilst logged in won’t work – you’ll be sent back to the login screen.
http://ajaxlife.net/noframes is still frameless, however, should this be necessary.
I’m working on new AjaxLife features. Hoorah.
I’d hoped to have a new version out by last Friday, but I changed my mind about what I wanted to get into this one. As such, here are some screenshots of the upcoming features to make up for it:
See pictures!
I’ve worked out why I can’t use AjaxLife at school.
You have attempted to access the following web page:
http://static.ajaxlife.net/AjaxLife.Libs.IE6.js
Access has been blocked because:
Page content filters applied – score = 7576
Since this file contains only prototype.js, scriptaculous and ExtJS, I haven’t a clue why it’s been blocked. It is annoying, however.
