Anyone developing automated software which interfaces with MediaWiki should be subscribed to this list. And for any such person, this thread should be enough of a red-flag for them. The API has existed for awhile, and the UI should not be depended on for any automated things.
~Daniel Friesen(Dantman, Nadir-Seen-Fire) of: -The Nadir-Point Group (http://nadir-point.com) --It's Wiki-Tools subgroup (http://wiki-tools.com) --The ElectronicMe project (http://electronic-me.org) --Games-G.P.S. (http://ggps.org) -And Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG) --Animepedia (http://anime.wikia.com) --Narutopedia (http://naruto.wikia.com)
Robert Ullmann wrote:
Quite so. However, it doesn't. And a *very* large amount of stuff is built on it. Would be good to fix it. Before changing the UI it relies on.
Question: How would the people maintaining it have known that it was going to be broken this morning?
Is easy to fix, took me < 3 minutes to fix my copy of wikipedia.py (mostly deleting code ;-).
But everyone else using the allpages generator will be stuck, and almost all will have no clue what is wrong or how to fix it.
On Wed, Aug 20, 2008 at 10:17 AM, Andrew Garrett andrew@epstone.net wrote:
On Wed, Aug 20, 2008 at 3:58 PM, Robert Ullmann rlullmann@gmail.com wrote:
It is now broken, and should be put back. (In particular, the python wikipedia framework has been broken.)
The User Interface is designed for users. The python Wikipedia framework, therefore, should use the API, and then it won't have these problems.
-- Andrew Garrett
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l