FANDOM


Forums: Yew Grove > Bot Status for Nq2h Bot
Replacement filing cabinet
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 20 March 2008 by Skill.

Purpose of Nq2h Bot

Nq2h Bot was designed to help accomplish some of the boring, repetitive edits normally done by wiki users. I have been testing Nq2h Bot all day, and it's currently at a stage where it is running without any problems. Some of the early features will include:

  • Categorizing jpeg images with the {{jpeg}} template
  • Categorizing the GEMH images with the Category:GEMH images category.

Here's a list of other features planned for the future:

  • Update infoboxes on all pages when the infobox itself is changed.
  • Automatically welcome new users - Consensus says not a good task.. so lets no do it.
  • Update all items price to the proper {{GEPrice}} template.

If anyone has ideas, or needs something to be done, feel free to ask that it be added to Nq2h Bot.

Why Bot status?

  • Bot status removes bot edits from Recent changes, unless you specifically show them.
  • Bot status allows Nq2h Bot to access links from the API for 5,000 pages at a time, rather than 500 for non-bot accounts.
  • Bot status would allow Nq2h Bot to edit faster, without causing problems. That would reduce the current wait-time from 8 hours (30 edits/hour), to under 40 minutes (6 edits/minute). Imagine how much more work it would get done going at 10 times the speed!

How to start Nq2h Bot

Currently, I am the only user allowed to run Nq2h Bot, however, I am working on a feature to allow sysops on the wiki access to him. He is run entirely from a web browser, with no downloads. The only catch is that the web browser must be left open the entire time he is running. I'll get this set up as soon as I feel Nq2h Bot is secure enough.

Consensus Needed

According to Wikia policy, community consensus is needed to update a user to a bot. That's why I need your help: please vote for support/oppose of Nq2h Bot receiving bot status, and give your reasoning behind it. Thanks! Grim reaper hood Ben RyfosTalk 01:02, 4 February 2008 (UTC)

Discussion

Support

  • Sysop crownTes FanSysop crown 02:28, 4 February 2008 (UTC)
  • Grim reaper hood Ben RyfosTalk 03:19, 4 February 2008 (UTC)
  • [[Image:Kandarincrest.gif|33px]]Chicken7[[Image:Kandarincrest.gif|33px]] 08:53, 4 February 2008 (UTC)
  • Chrislee33 09:01, 4 February 2008 (UTC)
  • Jigo22 14:38, 4 February 2008 (UTC)
  • Support, although I've got a couple of comments:
    • I'd question it auto-welcoming new editors - it's not very personal.
    • Be careful with the {{GEPrice}} thing - not all "Exchange:" article names exactly match the item's article in the main namespace.
    • Avoid sharing the "Nq2h Bot" account and password if/when you release it to other sysops (even if it's just compiled into the executable). Each sysop should really request their own bot account and log on to your code with that id, otherwise you won't have accountability if someone abuses it. Pointy 18:12, 4 February 2008 (UTC)
  • Skill 18:54, 4 February 2008 (UTC)
  • Support, but I agree about the new users - that shouldn't be a bot task. ChristineTalkFlickr 19:32, 4 February 2008 (UTC)

i supportGypsydog2 17:28, 7 March 2008 (UTC)

Oppose

Neutral/Other

Pointy's Points

  • Okay, if there's no consensus, I won't run any of the specific bots.
  • {{GEPrice}} - That bot specifically is a difficult one. There are a few checks built in:
  • Reads Exchange: templates and finds the matching title mainspace article.
  • Checks for the item infobox, and only ONE item infobox.
  • Checks that the item name is spelled the same.
  • Checks that the item image is the same.

If any of these checks fail, then the bot will require manual confirmation.

  • For other sysops: The code is based online, on a server, and is run entirely from the browser. The code isn't downloaded, so the username/password is secure on the server. There's going to be an implemented "SHUT OFF" switch, in case of abuse/problem, linked from the user page, and in every Edit summary. That way if it goes haywire, it's easy to fix. Once the link is clicked, Nq2h Bot could only process one more edit before it is forced to shut down. There is no manual override, and it must be changed by me. And, of course, there is no way to send custom commands to the bot, I set up an initialization file, which starts the basic settings (IE, for categorizing the jpeg images, it loads all the .jpg, .jpeg, .JPEG, and .JPG files from the wiki to a list to be processed.), and passes that to the actual bot, who runs that info. The only potential for abuse would be to modify the settings, which, I am rewriting the bot framework to save to a file on the server (rather than using GET paramaters in the url.) As I said, this won't be done until Nq2h Bot is completly secure, to my standards, which is to prevent hacking from experianced users, and not just mistakes by sysops. Grim reaper hood Ben RyfosTalk 18:34, 4 February 2008 (UTC)
    • A comment on the shut off switch: there would have to be a mechanism to prevent abuse of that switch, wouldn't there? And if it's restricted to sysops only, then how is it different from blocking? Unless it's just a link to the block page? Skill 18:52, 4 February 2008 (UTC)
      • I was going to put a simple password on it, so that it wasn't restricted just to sysops, but I could, of course, give the password to trusted editors. And, of course, someone like me who needed to quickly shut off a bot going out of control. Nothing too hard of a password, but something that would prevent ips from forcefully shutting it off. Maybe, like BotNq2h1 or similar. Grim reaper hood Ben RyfosTalk 18:46, 5 February 2008 (UTC)

Nq2h Bot has been Botted!

Nq2h Bot has been botted by Avatar today. Thanks to all who supported this! Nq2hBot3 and Nq2hBot4 will be on their way soon! Grim reaper hood Ben RyfosTalk 07:59, 7 February 2008 (UTC)

Community content is available under CC-BY-SA unless otherwise noted.