Wikipedia:Bots/Requests for approval/Nomenclaturebrowser
Tools
Actions
General
Print/export
In other projects
Appearance
From Wikipedia, the free encyclopedia
- The following discussion is an archived debate. Please do not modify it. Subsequent comments should be made in a new section. The result of the discussion was Approved.
Operator: Aaronbrick (talk)
Automatic or Manually Assisted: N/A, no edits are made
Programming Language(s): PHP, JavaScript
Function Summary: Present interwiki links graphically to users of my program, hosted elsewhere.
Edit period(s) (e.g. Continuous, daily, one time run): Runs as requested by users - no edits.
Already has a bot flag (Y/N): N/A
Function Details: This program implements a word browser for those curious about things' names in many languages. It uses NLP techniques to compare interwiki article names. I am applying for bot status so I can get the apihighlimits permission, which will make my program provide better results without making more API queries to the servers.
Discussion
[edit]- What kind of queries is this going to be doing, that it needs to get lists of more than 500 articles? Is this something that could be done on the toolserver? Mr.Z-man 16:02, 15 October 2008 (UTC)[reply]
- I only actually am trying to get from a maximum of 50 pageids per query to 500. the idea is to acquire lists of category member peer articles that the user can click to. that query is in the form http://en.wikipedia.org/w/api.php?action=query&format=xml&redirects&prop=langlinks&pageids=11%7C12%7C13. Yes, it could perhaps run on the toolserver, but isn't the MediaWiki API with XML output meant for building applications on? i don't really understand why running on the toolserver would be better for anyone involved. Aaronbrick (talk) 18:48, 15 October 2008 (UTC)[reply]
- Can you provide some links to your graphical offering. I can't see a load issue with running it via the API, although it's not time sensitive enough to really require it. It's a 6 of on half a dozen of another scenario. Tawker (talk) 16:41, 15 October 2008 (UTC)[reply]
- The graphical layout portion of the app is broken at the moment, but I posted an example PNG for you to see what i'm getting up to: [1]. Aaronbrick (talk) 18:48, 15 October 2008 (UTC)[reply]
- Flag it - there's little risk here of breaking anything -- Tawker (talk) 19:29, 15 October 2008 (UTC)[reply]
- The graphical layout portion of the app is broken at the moment, but I posted an example PNG for you to see what i'm getting up to: [1]. Aaronbrick (talk) 18:48, 15 October 2008 (UTC)[reply]
- Can you provide some links to your graphical offering. I can't see a load issue with running it via the API, although it's not time sensitive enough to really require it. It's a 6 of on half a dozen of another scenario. Tawker (talk) 16:41, 15 October 2008 (UTC)[reply]
- I am of course willing to make API queries to a toolserver URL instead of the user-facing hostname if people would prefer it. Freshness is not a priority, as Tawker mentioned. Aaronbrick (talk) 21:08, 15 October 2008 (UTC)[reply]
Approved. BJTalk 22:29, 16 October 2008 (UTC)[reply]
- The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made in a new section.