Ok, so that method didn't work out. Is there still room for discussion on another way to allow MediaWiki to easily access the API on another MediaWiki wiki, even if it's only given shorturl information such as what is inside of an interwiki link? It may be ok for other applications like bots and such which easily reuse the same data, but it's not a good idea to force a MediaWiki extension to grab a page from MediaWiki, hack out the scriptPath from there using some ugly regex, and then make it's query to the api. And need to do that on each new page request which requires an api call to that wiki. If the extension wants to support something through InterWiki which requires some info from the api. The other two methods I can think of, are a url parameter, something like &action=api, or back to [[Special:API]], except instead make it return the url of the api as text if it is enabled. Directly giving the url of the api is better than making it need page parsing. ~Daniel Friesen(Dantman) of: -The Gaiapedia (http://gaia.wikia.com) -Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG) -and Wiki-Tools.com (http://wiki-tools.com) Roan Kattouw wrote:

Extensions have access to $wgScriptPath on THEIR wiki, not another wiki through interwiki. This is for extensions trying to get data on OTHER wiki, of which they have no knowledge of the script path. ~Daniel Friesen(Dantman) of: -The Gaiapedia (http://gaia.wikia.com) -Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG) -and Wiki-Tools.com (http://wiki-tools.com) Minute Electron wrote:

Simetrical schreef: Exactly, we have FauxRequest for that. Roan Kattouw (Catrope)