Talk:Bot policy

From Meta, a Wikimedia project coordination wiki

Jump to: navigation, search

Contents

[edit] Bot authorisation

Representing a widely shared point of view, I ask for explicitly telling in the policy that a bot must have a bot flag for doing regular work in a wikipedia. Smaller wikipedias often have their Recent Changes page messed because of bot owners, who regard smaller domains as unimportant or so. Slavik IVANOV 02:25, 20 October 2007 (UTC)

If there are active sysops, they can block the bots. It would be simpler leave some flexibility and let the communities to decide upon this issue. Some wikis wish to see trial edits before granting bot flags, for example. Hillgentleman 03:57, 17 July 2008 (UTC)

[edit] presence at IRC

Halló! It would be a good idea to request presence of the bot operator at IRC preferable at the freenode.net #pywikipediabot channel. This would facilitate and speed up contacts. Once a consensus is reached the channel should be listed at IRC channels. Best regards
‫·‏לערי ריינהארט‏·‏Th‏·‏T‏·‏email me‏·‏‬ 18:55, 4 February 2008 (UTC)

[edit] Interpretation of automatic approval

If the local bot policy allows automatic approval of interwiki bots but there is a local bureaucrat, what is the best way to apply for a bot flag? Case in point: I was going to resort to automatic approval in the Farsi Wikipedia (not realizing at first that there was a local bureaucrat), but ended up submitting a regular request. Well, now the standard bot policy has been abandoned in the Farsi Wikipedia, so perhaps the real problem in this case was a lack of consensus on the local policy... --Silvonen 17:37, 22 June 2008 (UTC)

[edit] Reverted adds

What do you mean with «times specific to Western world»? UTC times can be converted, but servers are busy at the same time in all the world. The link is not broken. Why do you say that it is redundant? I don't see anything about urgency and edit rate in trial periods. --Nemo 19:11, 13 July 2008 (UTC)

You added that the most busy hours are 12:00–04:00 UTC, which is based on the busy times in North America and Europe. People are asleep at that time in many other timezones, including some wikis where it is implemented. Times specified would need to take into account which wiki the user is interested in, and which server it is located on. For example, the busy hours for the yaseo server (in South Korea) seem to occur during the quiet hours of the pmtpa server (in the United States).
The link was broken at the time it was added, but works now. However, it would be more appropriate to the 'see also' section than to the policy text.
Much of the text is redundant with what is already said. For example, the text gives specific rate limits, then later vaguely repeats that they "should be run at a rate that permits review of their edits when necessary" and that "unflagged bots should edit more slowly than flagged bots". Furthermore, several of the additions contradict server administrators who have publicly stated that performance should not be a concern during editing, and that the software itself will prevent overload.
Furthermore, crosswiki policy development is different from local policy. Such significant changes to the policy will require notification and re-approval on every wiki where it is implemented. As such, they should be discussed before simply changing the policy from what was approved. —{admin} Pathoschild 06:54:29, 14 July 2008 (UTC)
The policy specifies the limits that you can never exceed, but also under that limits, although there are not specific rules, common sense is needed.
Many operations should be done where most people sleeps, and servers are not busy; obviously we can specify that in the graph everyone should consider only the server cluster which he actually uses (pmtpa, knams, or yaseo).
The «rate that permits review of their edits when necessary» is not influenced by performance, anyway performance is a problem, in fact we italians are experiencing some performance problems (example), so we don't need draconian regulation, but bot operators should be made aware of their responsibilities. --Nemo 19:23, 16 July 2008 (UTC)
It would be an extra bonus if your explanation on busy hours, server dependent and the pmtpa server busy time, was also written in the policy text as a 1 or 2 sentences example. rursus 10:49, 20 January 2009 (UTC)

[edit] Double redirects

Fixing double redirects is now done automatically in the job queue, so bots are no longer required for this task - there is no need for such bots, so I suggest removing that task from the list.  — Mike.lifeguard | @en.wb 23:28, 26 July 2008 (UTC)

If I'm not mistaken, double-redirects are only corrected for new page moves. This leaves many existing double-redirects on various wikis, so it's still a valid bot task (I even came across one a few minutes ago). It's also possible to disable the feature on the move form, so I suspect there will be a slow accumulation of unfixed double-redirects over time. Since it's still a valid bot task and it's uncontroversial, I don't think we should reject requests for bot flags to do it. —{admin} Pathoschild 23:49:49, 26 July 2008 (UTC)
Oh, I wasn't aware of that limitation... /me backreads in wikitech-l  — Mike.lifeguard | @en.wb 23:51, 26 July 2008 (UTC)
Is this the config change alluded to? I don't believe it's done automatically in any case. —Giggy 05:56, 27 July 2008 (UTC)

[edit] global bots

Global bots have permission only "bot"(be treated as automated process). How about granting "apihighlimit" (can use more api) And I request for renaming wikiset "Standard bot policy" to be "Global bot". This set includes wikis don't use standard bot policy, so current name make me confused.--Kwj2772 06:05, 29 September 2008 (UTC)

Done. —{admin} Pathoschild 09:23:41, 29 September 2008 (UTC)

[edit] Global bots and user pages

Hi. Should global bots operators create user pages for their interwiki bot on every project where it runs as a global bot? Thank you. --Ginosal 11:06, 4 October 2008 (UTC)

In my opinion, though the bot needs its own userpages on all wikis where it runs, not the operator's userpages. --Kanjy 15:25, 30 December 2008 (UTC)
I agree.--Kwj2772 13:57, 8 January 2009 (UTC)
Of course. Many global bot don't do it. It's very hard to find the owner, and the bot must generaly be blocked to have a contact. --Hercule 07:13, 5 August 2009 (UTC)

[edit] How fast the bot may run during a trial for automatic approval?

I have a question upon automatic approval process. While the bot is running for a week or making 100 edits as a trial period, how fast the bot may run? At intervals of over 1 minute, or at the speed of its full-scale operation? Regards. --Kanjy 15:25, 30 December 2008 (UTC)

Trial edits are considered as unflagged bot edit. Should have intervals of over 60 seconds.--Kwj2772 00:40, 9 February 2009 (UTC)

[edit] Clarifying 'regular' edits

This line should be changed to read something like this:

  • the bot must edit regularly without a bot flag for at least a week or make 100 edits on the applicable wikis for demonstration purposes;

One edit one or two weeks ago shouldn't qualify. -- sj | help translate |+ 01:36, 6 March 2009 (UTC)

Done, that is indeed the intended meaning. —Pathoschild 20:37:10, 06 March 2009 (UTC)

[edit] Making this policy opt-out or strengthening opt-in

I am quite concerned about the precedent that leaving an english-language message for a week on a village pump that native-language authors do not use, on wikis where there are active editors (and sometimes active admins) constitutes any kind of 'due notice'. we should not pretend that this informs any local editors, and should find better ways to do so. This is only done, as far as I can tell, for bot requests and recently 'requests to implement global bot policy' -- a request that is almost universally made, ignored, and implemented as though a week's silence were consent.


Since it makes sense for bots to stop clogging up RC's on those wikis, let's clarify bot policy here on meta, and either get consensus that this should be an opt-out policy, or define a better way to request that small wikis implement it.

1. If it were opt-out, the memo left on newly formed wikis' public pages could say something like "This wiki is now recognizing bots by default according to the global bot policy. To opt out of this policy and review bot requests locally, read on." --- and we should make a point of asking localizers to translate this as one of the core messages for a new wiki. Since "show bots" on RC is translated as a core message, anyone confused about where edits are coming from can readily figure out how to toggle that flag on to review all bot changes and potentially ask for a bot to be deflagged or blocked.

2. If it remains opt-in, we should define 'opt in' in terms of #s of local editors (not just bot maintainers) commenting on the proposal, and in terms of the activity level of the wiki. If noone has commented but the wiki has active editors, that's clearly not approval. If there are no non-bot editors, what's really going on? Some wikis just have slooower time scales -- maybe 2 months is better for some of them.

-- sj | help translate |+ 03:31, 6 April 2009 (UTC)

Hello Sj. I don't think your proposal makes sense. To avoid implementing the policy on wikis without local discussion, we should implement them on all wikis without even proposing it locally, then demand a consensus to unimplement it? This is less open than the current process.
Implementation is not a grave issue; if a community member comes along three months later and objects, global bots will be disabled on that wiki. Out of the 217 wikis that have implemented it, this has never happened that I can recall. Before implementing a proposal, I ensure these proposals are on or linked from community discussion pages, and delay implementation longer on wikis with active users. Users have plenty of time to comment or request a translation.
I'm not strongly opposed to an opt-out process, but I think it is less open than the current opt-in process. —Pathoschild 04:15:29, 06 April 2009 (UTC)
You are currently effectively demanding a consensus to unimplement it, on any wiki where the local editors do not use their village pump or don't read policy pages every week. I am suggesting being more transparent about the effect this has, rather than claiming that silence = adoption. Since there are many people who want to see bot policy implemented on tiny wikis where noone knows what it is or how to comment on this idea, we should be up front about the fact that it is actually an opt-out policy for those wikis -- once they get large enough to have an opinoin about the policy, they should be able to discover that they have a choice and take control of bot approvals directly.
I agree implementation isn't the issue. Setting a precedent that silence on small wikis equals acceptance of a proposed change, or that hyper-active wikis can determine what is a reasonable amount of time to leave notices up on smaller ones, is what concerns me.
Communities new enough not to know how to accept bot policy or monitor their Village Pumps certainly won't know that they had a choice or that they /could/ complain even if they wanted to.
I would prefer opt-in, all else being equal. But people are not waiting for local acceptance, and there is some logic in not wanting bots to clog up recent changes for small wikis that don't yet know what bots are or how to review new bot editors. -- sj | help translate |+
Strictly speaking, robots should not be operating on these wikis in the first place. Certainly not en mass in any case. Hillgentleman 06:34, 8 April 2009 (UTC)
Well, incorrect interwiki links are harder to fix if some wikis are out of the reach of global bots. A newer look at the interlanguage link would be a better solution, but it doesn't seem to be progressing very fast... --Silvonen 06:52, 8 April 2009 (UTC)
I doubt it. Robots are double-edged. The interwiki-mess became a problem because the interwiki.py was so easy to use that people use it carelessly. It would only get better if the links are not added blindly. This is a very likely scenario - think of a new wiki who starts to write an article on the concept of "money" and happens to point it to en:currency. With the bots running around you will have a hard time fixing it. I have often times added a nobot-template just to make sure that interwiki bots don't screw up again. In four words, 寧缺毌濫 (better lack than excess). Hillgentleman 20:28, 8 April 2009 (UTC)
It happens a lot that a new article has wrong interwiki's. What do you think of the example that an article about the year 1988 point to en:1989. All the autonomous bots will add that wrong link. Until someone manual fixes it. The mess bots makes can sometimes only be solved by bot's with good operators and a lot of flags. The right to run as a global bot is one you have earn and you need to be skillfull. Carsrac 12:49, 13 May 2009 (UTC)
The opt-out option needs to be more public, because sometimes a wiki will accept the global bot policy only if you can step out of easily. Carsrac 12:49, 13 May 2009 (UTC)

[edit] Global bots vs. cosmetic changes.py

Hey folks, I've been running a global bot for about 11 months and I've recently noticed that the other global bot owners make the cosmetic changes together with the interwiki linking. That's why I started making these changes as well. Everything had been fine until yesterday when my bot was blocked on the Italian Wikiquote and all its edits were reverted (although there was nothing wrong with them). The admin who had blocked my bot just ignored my message and when I tried reverting the edits back, I got blocked for vandalism from him. By now, our small dispute is already over and we came to a conclusion that I will have to ask the locals for cosmetic changes approval. However, I would like to know the Wikimedia community's opinion on global bots making cosmetic changes. The bot policy does not allow them but it seems that the bot owners don't respect this policy. Thoughts? Ideas? --Mercy 18:14, 13 November 2009 (UTC)

The script is called cosmetic_changes.py for good reason. I see no reason additional permission should be needed for such trivial changes. I do also take issue with how this case in particular was handled, but you say the dispute is resolved, so I won't comment further on that.  — Mike.lifeguard | @en.wb 19:54, 13 November 2009 (UTC)
Cosmetic changes isn't just cosmetic. At least with no.wikipedia, it does changes that are against policy. (among other things changing – to –, when we have a policy about writing it in HTML, so that people don't misread it from -). Laaknor 20:56, 13 November 2009 (UTC)
Then the script has changed since I last used it :(
I should have pointed out initially, that the requests of the wiki are paramount - if the itwikiquote users, or nowiki, want it to not be used, then don't use it. Are such problems commonplace? They certainly weren't when I was operating my bot.  — Mike.lifeguard | @en.wb 22:20, 13 November 2009 (UTC)
The global bot flag must be used only for tasks specifically approved by the policy or local community. Communities enable the global bot flag on the assumption that there is no need to review their edits because they're not doing anything unexpected. If you'd like to perform any task aside from those specifically approved, you must first ask the local community whether they object.
If you see other bot operators performing unapproved tasks, please ask them to stop or let me know. —Pathoschild 23:25:40, 13 November 2009 (UTC)
Retrieved from "http://meta.wikimedia.org/wiki/Talk:Bot_policy"