LL Pulled map api and broke outside apps

as noted at http://blog.katharineberry.co.uk/2007/09/27/ll-killed-ajaxlife/ it appears that LL has pulled their map api breaking outside applications.

The pull may be temporary. There is a jira out there to fix the map api, since it's basically been broken for the last 6 months. Cornelius Linden has been working on it.

Looks like they've replaced it with a google-based alternative, and that is one of the things the blog the OP pointed at was upset with.

http://wiki.secondlife.com/wiki/MapAPI

IIRC, it's been "powered by google" for quite some time. snapshots taken 6 months ago will show that the silly little powered by google image has been a part of the api for months now.

http://jira.secondlife.com/browse/WEB-93

The only thing is that there has finally been some movement afoot to actually fix it.

K, trying to figure out why the blog the OP pointed to says:

It could be that they temporarily disabled the feed, that's all, while they fix it. At least that is what I'm hoping for. As for her grousing about Google... I don't know, don't care, because I remember seeing the Google reference for months now, and if she never noticed it, that's just that. It is of no consequence.

Could it possibly be she was using what the google replaced, the mapapi, not the google based webmap api? It is not a temporary disabling, but that the old version has finally been pulled as it has been replaced with the google based version (which you point out is broken)?

(Which is what I said in my original post)

My reading of it is that she is more than just annoyed with the logo in the google based version, but that she is also upset that "the replacement lacks an important function to make it work, is still in beta, still has assorted voice-map related things hardcoded in."

"the replacement" being the google version that has been out for six months.

I don't know what's different, she would need to clarify. My impression is that AjaxLife worked up until today. And the "crappy beta" has been around for months, not just today. She's getting a 404 error - file is not found. My best guess is that it does not appear to be that the map api has been permanently replaced yet with something new. It is just not there, no data available.

I think she is pretty clear. She has been writing to the old pre-google map api. Does not want to use the google version (or not until it works). That old pre-google api has disappeared with no prior announcement (that she has seen) though she does acknowledge knowing that it has been in the works for a while.

That is why Ajaxlife does not work today, it is not written to the google based api.

I realize you have been immersed in the new api, and probably don't even realize there were people who depended on the old api. I am not justifying her decision, just trying to make it clear what she is complaining about. Those who depend on Ajaxlife working do not just have to wait for LL bring the google version back on line (to my knowledge it isn't even off-line), but will have to wait until the Ajaxlife provider feels that the google-based replacement is somehow worthy of her re-writing Ajaxlife to use it.