Linden Lab has informed me that AjaxLife cannot be run as an openly available service (this is the first time any formal policy regarding it has been determined). It is not currently actually blocked; however, I will be terminating service effective immediately. Note that it is permissible for you to obtain the source and run a private server; however, I will not be maintaining the code, and you may not make your server publicly accessible either.
I have included below the pertinent portion of the communication from Linden Lab, which is the termination of several weeks of (intermittent) discussion:
I’m afraid we can’t reinstate access for AJAX Life as an
open service, even if L$ transactions are disabled. The problem
remains that the others have used the service for harassment and
fraud, and we don’t have engineers available to integrate the IP
address hash you’ve offered to forward on connection with the
governance tools. We also don’t have resources for oauth or another
third-party authentication system at this point – the user count
doesn’t justify it against larger issues.There’s also the problem of the password being passed through AJAX
Life. This creates a security risk for Linden Lab and for the users,
and extends liability risks to you.
It is perhaps important to stress that this is not an unreasonable statement; merely an unfortunately one. I have no idea how many people used AjaxLife, but it was under 600/day, and concurrency was 50-60 at most.
If you’re wondering why this didn’t happen sooner: AjaxLife’s original architecture caused its IP to change extremely frequently, as a result of a combination of poor stability and frequent server reassignments. As part of the changes made to make AjaxLife stable (which it now is), it was given a fixed IP. As such, the issue of abuse from the IP became somewhat more prominent, resulting in whatever internal discussions lead to this.
It’s a shame, but it’s not surprising, and not really LL’s fault. It was nice for the last three years, at any rate.
Recent Comments