Meta tags:

Headings (most frequently used words):

bot, approval, and, with, other, requirements, of, approvals, malfunctions, complaints, editing, bots, changes, wikipedia, policy, contents, definitions, usage, process, dealing, issues, related, matters, see, also, accounts, good, communication, configuration, tips, restrictions, on, specific, tasks, requests, for, appeals, reexamination, minor, improvements, major, like, blocking, group, assisted, guidelines, user, scripts, the, flag, activity, directed, to, edit, by, users, performance, categorization, people, context, sensitive, cosmetic, interwiki, links, mass, page, creation, valid, operations, without, administrative, rights,

Text of the page (most frequently used words):
the (280), bot (186), and (115), for (81), bots (70), are (60), that (60), #wikipedia (59), should (56), page (55), account (52), may (50), not (49), approval (47), user (44), edit (33), #editing (32), such (32), with (31), policy (28), this (28), operator (28), request (27), bag (27), changes (26), their (26), also (25), edits (25), community (24), any (23), will (23), can (23), accounts (22), shortcut (22), pages (21), task (21), which (21), consensus (20), group (20), tools (20), make (20), from (18), requests (18), other (18), without (18), they (18), approved (18), operators (18), but (17), tasks (17), use (16), approvals (16), template (16), human (16), help (16), must (16), you (15), automated (15), assisted (15), all (15), perm (14), talk (14), have (14), users (13), links (13), related (12), see (12), brfa (12), some (12), run (12), create (11), scripts (11), creation (11), example (11), ensure (11), cosmetic (11), need (11), actions (10), editors (10), process (10), considered (10), separate (10), has (10), than (10), its (10), speed (10), operation (10), english (10), administrator (9), requirements (9), main (9), interwiki (9), technical (9), adminbots (9), while (9), processes (9), operate (9), more (9), wish (9), discussion (9), logged (9), non (8), wiki (8), only (8), category (8), cases (8), require (8), own (8), required (8), semi (8), there (8), when (8), particular (8), wikidata (8), code (7), policies (7), new (7), mass (7), block (7), file (7), blocking (7), how (7), history (7), hide (7), activity (7), one (7), out (7), high (7), noticeboard (7), trial (7), sensitive (7), toggle (6), search (6), using (6), categories (6), guidelines (6), global (6), admin (6), guide (6), vandalism (6), administrators (6), information (6), mediawiki (6), shortcuts (6), time (6), used (6), usually (6), whether (6), content (6), members (6), like (6), issues (6), does (6), during (6), approve (6), flag (6), made (6), generally (6), typically (6), before (6), messages (6), contents (5), view (5), terms (5), bureaucrat (5), rights (5), general (5), sanctions (5), blocks (5), two (5), changing (5), username (5), templates (5), citation (5), tool (5), useful (5), html (5), special (5), images (5), files (5), function (5), contributions (5), access (5), large (5), source (5), addition (5), higher (5), first (5), summaries (5), after (5), following (5), would (5), good (5), being (5), them (5), performed (5), even (5), issue (5), another (5), either (5), demonstrate (5), could (5), context (5), rate (5), wikimedia (4), dispute (4), resolution (4), meta (4), quality (4), control (4), editor (4), message (4), personal (4), get (4), attention (4), further (4), navigation (4), creating (4), list (4), irc (4), wikitext (4), section (4), test (4), documentation (4), image (4), usage (4), what (4), here (4), recent (4), mechanism (4), encouraged (4), instead (4), necessary (4), contributors (4), clear (4), making (4), covers (4), include (4), operating (4), running (4), experience (4), matters (4), unapproved (4), ways (4), operates (4), disruptive (4), expected (4), quickly (4), outside (4), many (4), provide (4), malfunctions (4), complaints (4), minor (4), specific (4), change (4), speedily (4), deleted (4), articles (4), scope (4), via (4), into (4), reexamination (4), responsible (4), including (4), both (4), upon (4), appropriate (4), prior (4), each (4), relevant (4), whose (4), arise (4), people (4), within (4), allows (4), performance (4), move (4), sidebar (4), subsection (4), add (3), languages (3), table (3), contact (3), about (3), privacy (3), available (3), apply (3), registered (3), commons (3), license (3), faq (3), clerks (3), interface (3), filter (3), advanced (3), groups (3), temporary (3), extended (3), autowikibrowser (3), long (3), log (3), appeals (3), open (3), identity (3), security (3), alternative (3), login (3), unregistered (3), style (3), watchlists (3), tags (3), markup (3), archiving (3), project (3), resources (3), lua (3), sandbox (3), syntax (3), scale (3), graphics (3), improve (3), upload (3), tables (3), levels (3), name (3), reverting (3), merely (3), existing (3), permitted (3), less (3), doubt (3), determine (3), note (3), already (3), order (3), been (3), through (3), known (3), assist (3), years (3), posting (3), those (3), member (3), then (3), botpol (3), manner (3), assertion (3), botblock (3), who (3), method (3), blocked (3), however (3), short (3), itself (3), meatbot (3), still (3), prevent (3), action (3), needed (3), per (3), major (3), behavior (3), discussions (3), details (3), remove (3), mistakes (3), encyclopedia (3), your (3), dealing (3), themselves (3), conditions (3), removing (3), immediately (3), down (3), allowed (3), implementation (3), visible (3), take (3), demonstrated (3), adminbot (3), problems (3), provided (3), decline (3), period (3), controversial (3), especially (3), decision (3), comments (3), periods (3), these (3), driving (3), substantive (3), always (3), output (3), sup (3), parameter (3), identify (3), false (3), database (3), check (3), categorization (3), restrictions (3), read (3), directed (3), communication (3), way (3), botcomm (3), download (3), work (3), mobile (2), developers (2), text (2), under (2), organization (2), foundation (2), was (2), last (2), edited (2), 2026 (2), procedural (2), index (2), noticeboards (2), founder (2), oversight (2), formal (2), administration (2), governance (2), arbcom (2), response (2), team (2), pending (2), reviewer (2), mover (2), confirmed (2), helper (2), instructions (2), quiet (2), return (2), clean (2), purpose (2), standard (2), abuse (2), infinite (2), unblock (2), appealing (2), password (2), unified (2), reset (2), passwords (2), logging (2), why (2), metadata (2), script (2), features (2), mode (2), cleaning (2), preferences (2), common (2), css (2), module (2), design (2), simple (2), portal (2), article (2), substitution (2), limits (2), musical (2), symbols (2), math (2), charts (2), visual (2), sound (2), tag (2), uploading (2), tutorial (2), introduction (2), moving (2), media (2), trick (2), link (2), diffs (2), permanent (2), interlanguage (2), conditional (2), redirects (2), switch (2), parser (2), words (2), lists (2), watchlist (2), random (2), notifications (2), characters (2), software (2), notices (2), village (2), pump (2), effect (2), types (2), intended (2), commonly (2), kind (2), normally (2), botscript (2), authors (2), normal (2), speeds (2), volume (2), involvement (2), likely (2), full (2), treated (2), number (2), desired (2), unless (2), examples (2), correcting (2), errors (2), semiautomated (2), retired (2), week (2), notice (2), understand (2), bagreq (2), specified (2), added (2), choose (2), cause (2), stop (2), end (2), particularly (2), concerned (2), act (2), appeal (2), ask (2), examination (2), forms (2), causing (2), problem (2), disruption (2), followed (2), urgent (2), leave (2), requesting (2), notify (2), place (2), exceed (2), projects (2), might (2), directly (2), improvements (2), botissue (2), status (2), placing (2), denied (2), comment (2), botappeal (2), desysopped (2), same (2), circumstances (2), much (2), monitor (2), trials (2), marked (2), technically (2), level (2), sysop (2), recommended (2), keep (2), part (2), publicly (2), present (2), review (2), until (2), administrative (2), performing (2), compliance (2), small (2), completely (2), limited (2), low (2), otherwise (2), exemptbot (2), botuserspace (2), valid (2), operations (2), occasionally (2), having (2), declined (2), standards (2), expired (2), give (2), frequently (2), affected (2), proposed (2), correctly (2), reviewing (2), caused (2), drive (2), skills (2), botapproval (2), override (2), exists (2), cannot (2), linking (2), subject (2), subpage (2), local (2), interwikibot (2), mind (2), acceptable (2), report (2), cosmeticrevert (2), done (2), affect (2), browsers (2), maintenance (2), hidden (2), engine (2), external (2), readers (2), web (2), because (2), feed (2), most (2), cosmeticbot (2), unicode (2), manual (2), possible (2), positives (2), accepted (2), contextbot (2), spellbot (2), manually (2), potentially (2), botpcat (2), avoid (2), unnecessary (2), responsibility (2), protected (2), opting (2), botconfig (2), configuration (2), tips (2), email (2), notification (2), queries (2), able (2), meet (2), enquiries (2), where (2), allow (2), left (2), server (2), achieved (2), url (2), completed (2), botperf (2), runs (2), harmless (2), botrequire (2), directing (2), verification (2), methods (2), botmultiop (2), had (2), botinactive (2), botflag (2), designated (2), botacc (2), lower (2), botuse (2), decisions (2), dictionary (2), botdef (2), definitions (2), botp (2), documents (2), appearance (2), беларуская (2), donate (2), menu (2), topic, cookie, statement, statistics, conduct, legal, safety, contacts, disclaimers, additional, site, agree, trademark, profit, inc, creative, attribution, sharealike, rendered, parsoid, august, utc, retrieved, https, org, php, title, bot_policy, oldid, 1372438517, assisted_editing_guidelines, reforms, petitions, elections, wikiprojects, proposals, seat, board, editorial, spi, functionaries, arbitration, committee, committees, researcher, importer, manager, checkuser, rfb, rfa, volunteer, viewer, rollback, sender, exempt, event, coordinator, autopatrolled, auto, creator, permissions, deletion, start, courtesy, vanishing, retiring, enforcer, wikibreak, spam, sleeper, single, sockpuppetry, offer, term, indef, essay, contentious, topics, banning, proxies, ipv6, range, addresses, wizard, utrs, ticket, system, autoblock, bans, outed, compromised, confidentiality, discretion, committed, 2fa, awb, factor, authentication, practices, strength, sul, usernames, too, referencing, accessibility, inactive, stiki, igloo, wpcleaner, ultraviolet, twinkle, redwarn, popups, interceptor, huggle, hotcat, antivandal, afc, beta, cloud, services, optimum, set, browser, browsing, safe, techniques, customizing, skins, gadgets, customisation, styles, span, validation, classes, microformats, cascading, sheets, timedmediahandler, extension, bug, reports, feature, description, draft, namespaces, data, structure, parameters, scribbling, costs, benefits, labeled, transclusion, job, queue, purge, coding, modules, wikihiero, easytimeline, timeline, scores, formulas, barcharts, graphs, family, trees, lab, basic, bitmap, tutorials, gallery, svg, options, preparing, picture, urls, pipe, color, colon, colours, sortable, collapsing, formatting, basics, sections, tocs, expressions, beginners, magic, line, break, handling, columns, cheatsheet, linksearch, searching, import, curation, echo, moves, merging, logs, emailing, allpages, visualeditor, entering, editnotice, printing, multilingual, support, toolbar, conflict, charinsert, keyboard, bypass, cache, desk, teahouse, agents, language, models, agent, majority, personalize, simplify, functions, release, constitute, requires, intending, advised, indicate, adhere, multiple, repetitive, alter, interaction, fixing, stub, sorting, disambiguation, typographical, membership, rejoin, experienced, writing, programming, role, interested, joining, post, explaining, outlining, past, advertise, seven, days, uninvolved, close, botn, vpm, suspected, indefinitely, soft, counter, issued, similar, notified, broken, fashion, purely, aware, pay, sacrifice, pursuit, quantity, irrelevant, contrary, attentive, actually, programmatic, assistance, matter, discuss, try, neutral, mediators, formally, longer, established, significant, responded, several, mechanisms, means, disable, problematic, tried, malfunctioning, guideline, taking, button, tweaks, reviewed, reasonable, interpretation, original, mandate, instance, archive, wikiproject, thread, age, begin, probably, submit, originally, expand, noticed, complaint, suggestion, concerns, suggestions, please, bugs, happen, build, don, panic, assume, faith, responsive, authority, proper, venue, imposing, operational, maintain, granting, revoking, result, discussed, warranted, except, uncontroversial, voluntarily, stepped, destructive, potential, regular, closely, development, updates, shut, sign, incorrect, held, awry, neglect, constitutes, misuse, dry, bit, practical, clearly, satisfied, recommend, given, responds, acts, final, arbiter, adequate, publicity, underlies, assessment, elect, forum, want, put, hold, conducted, summarily, modify, extend, fix, unlikely, larger, implemented, carry, testing, very, frequency, restricted, affects, subpages, thereof, userspace, brfas, duplicates, trusted, similarly, once, conformance, correct, fails, perform, withdraw, mark, stale, closed, archived, preserved, future, reference, assigned, questions, feedback, above, formed, traffic, resulted, controversy, comes, wider, often, asked, areas, expertise, area, insight, monitored, extent, determined, supervised, addressed, repairing, initial, confident, state, well, sufficient, prospective, standing, demonstrable, proposes, precisely, headbomb, think, trouble, fine, doesn, right, over, 200, zone, gives, licenses, abused, revoked, accordingly, nor, creations, strictly, falls, considering, rather, namespace, transcluded, included, portion, comply, globally, applies, follow, guidance, reason, revert, exceptions, determines, though, formalized, substituted, egregiously, invalid, unclosed, display, fixed, sub, remexhtml, track, date, october, backlogs, facing, interfaces, listing, results, snippets, noindexing, sort, keys, audio, rendering, accessed, updating, blank, lines, formatted, wikicode, assistive, technology, pdfs, printed, screen, difference, something, consumers, clutter, histories, worth, spent, includes, sometimes, whenever, character, difficult, visually, entities, applying, weasel, word, converting, regional, variation, spelling, grammar, punctuation, unsupervised, accounting, unfeasible, exceptionally, complete, supervision, reversion, positive, dump, assignment, person, adding, publish, previously, providing, enabled, disabled, resorting, configured, value, finds, doing, bear, retain, honor, conflicts, checking, presence, states, honors, ignore, hours, since, actively, undergoing, prevented, interpreting, explanation, works, deliver, newsletters, critical, advertised, delivered, implement, depending, nature, enable, pings, expect, cordiality, backed, prompt, civil, care, communications, resulting, cordially, promptly, appropriately, handled, reachable, landing, confusing, speaker, sites, registration, compromise, supplement, replace, minimum, willing, address, sure, condition, anonymity, github, phabricator, italian, owners, substantial, portions, individual, databases, toolforge, dumps, adjusted, based, replica, lag, slowing, considerably, load, appending, extra, query, string, requested, maxlag, regulated, norm, maximum, twenty, minute, explicit, urgency, renaming, accomplished, slower, unflagged, slowly, flagged, permits, recognize, greater, average, contributor, careful, conservative, inform, significance, situations, directives, sysadmins, continuously, intermittently, intervals, automatically, userpage, uses, informative, wording, carefully, adheres, performs, consume, unnecessarily, competence, skill, knowledge, reliably, verified, easily, faked, bypassed, avoided, suitable, trivial, hostname, stronger, disclosure, disclosed, summary, direct, preferable, permissible, due, privileged, met, oauth, listed, deauthorized, flags, removed, reactivate, reduces, imposed, default, api, copyviobot, fall, respond, redirect, remain, prominently, identifiable, repair, damage, incorrectly, wishing, register, expects, prohibited, lead, effectively, severe, malfunction, misused, scrutiny, capable, far, faster, humans, oversee, classification, ambiguous, personalized, written, javascript, automate, enhance, specifically, actual, below, launching, assumption, robots, automation, simply, assisting, supervises, approves, perspective, behalf, differ, operated, responsibly, nutshell, various, newsletter, overview, redirected, free, item, wikivoyage, wikispecies, printable, version, pdf, print, export, legacy, shortened, isizulu, 閩南語, bân, lâm, winaray, tiếng, việt, українська, chitumbuka, türkçe, ไทย, тоҷикӣ, தமிழ், српски, srpski, chishona, සිංහල, سنڌي, русский, português, پښتو, ਪੰਜਾਬੀ, sesotho, leboa, मराठी, मैथिली, lietuvių, лезги, کٲشُر, 한국어, қазақша, адыгэбзэ, italiano, igbo, gaelg, bahasa, hulontalo, गोंयची, कोंकणी, gõychi, konknni, فارسی, eesti, español, esperanto, বাংলা, भोजपुरी, тарашкевіца, تۆرکجه, অসমীয়া, الدارجة, العربية, top, learn, contribute, current, events, jump,

Text of the page (random words):
troversial either in themselves or because they clutter page histories watchlists and the recent changes feed with edits that are not worth the time spent reviewing them such changes should not usually be done on their own but may be allowed in an edit that also includes a substantive change changes that are typically considered substantive affect something visible to readers and consumers of wikipedia such as the output text or html in ways that make a difference to the audio or visual rendering of a page in web browsers screen readers when printed in pdfs or when accessed through other forms of assistive technology e g removing a deleted category updating a template parameter removing blank lines from lists formatted in wikicode the user facing interfaces of wikipedia such as category listing or on wiki and external search engine results e g changing category sort keys noindexing search engine summaries snippets or page images the administration of the encyclopedia such as the maintenance of hidden categories used to track maintenance backlogs e g changing citation needed to citation needed date october 2026 or egregiously invalid html such as unclosed tags even if it does not affect browsers display or is fixed before output by remexhtml e g changing sup sub to sup sup while changes that do not are typically considered cosmetic minor edits are not usually considered cosmetic but still need consensus to be done by bots consensus can as always create exceptions for particular cosmetic edits for example the community frequently determines that a particular template should be substituted so it can be deleted even though the substitution does not change the output of the page consensus for a bot to make any particular cosmetic change must be formalized in an approved request for approval shortcut wp cosmeticrevert wp cosmeticrevert keep in mind that reverting a cosmetic edit is also a cosmetic edit if the changes made in a cosmetic edit would otherwise be acceptable as part of a substantive edit there is no reason to revert them report the issue to the bot operator instead while this policy applies only to bots human editors should also follow this guidance if making such changes in a bot like manner interwiki links shortcut wp interwikibot wp interwikibot see also help interlanguage links and wikipedia wikidata interwiki bots should add interwiki links on wikidata rather than on the english wikipedia unless the task cannot be performed on wikidata such as linking to a section interwiki bots may remove interwiki links from english wikipedia articles only if already present on wikidata globally approved interwiki bots are permitted to operate on english wikipedia subject to local requirements interwiki bots running in the template namespace must ensure links are not transcluded on all pages using the template by placing them in the appropriate documentation subpage section or non included portion of the template if no documentation subpage exists bots running on wikidata need to comply with wikidata s bot policy mass page creation main page wikipedia editing policy mass page creation mass page creation may require approval by the community in addition to a brfa if the method of that creation falls under this bot policy bag may require that community approval for any mass content creation exists before considering bot approval approval of a bot for mass creation does not override the need for community consensus for the creation itself nor does community consensus for a creation override the need for approval of the bot itself bot operators must ensure that all creations are strictly within the terms of their approvals approval process shortcut wp botapproval wp botapproval requests for approval you can more or less think of a brfa as being a driving license if you drive without one you can get in trouble even if your driving skills are fine and if you have a license it still doesn t give you the right to run over people or drive 200 km h in a 50 km h zone bag gives out these driving licenses if they are abused they can be and are revoked and bots are blocked accordingly headbomb all bots that make any logged actions such as editing pages uploading files or creating accounts must be approved for each of these tasks before they may operate bot approval requests should be made at wikipedia bots requests for approval brfa requests should state precisely what the bot will do as well as any other information that may be relevant to its operation including links to any community discussions sufficient to demonstrate consensus for the proposed task s in addition prospective bot operators should be editors in good standing and with demonstrable experience with the kind of tasks the bot proposes to do during the request for approval a member of the bot approvals group bag will typically approve a short trial during which the bot is monitored to ensure that it operates correctly the terms and extent of such a trial period may be determined by the bag bots should be supervised during trial periods so that any problems may be addressed quickly the bot operator is responsible for reviewing the edits and repairing any mistakes caused by the bot the bag may also approve extended trials should problems arise with the initial trial and until the community is confident the bot will function correctly the request will generally be open for some time during which the community and bag members may comment or ask questions and give feedback on the trial the decision to approve or decline a request should take into account the requirements above relevant policies and guidelines and discussions of the request consensus formed by a small group on a low traffic talk page has frequently resulted in controversy when it comes to the attention of the wider community bot operators are encouraged and often asked to notify the relevant noticeboards whose areas may be affected or whose expertise in the area could provide useful comments and insight into the proposed task once the request has demonstrated its conformance with the community standards and correct technical implementation the bag may approve the task the bag may also decline a request which fails to demonstrate community consensus to perform the task occasionally the operator may wish to withdraw the task or the bag may mark a stale request as expired closed requests are archived and preserved for future reference should the task be approved the bot user group flag will be assigned by any bureaucrat and the operator may run the bot as intended the bag may also occasionally speedily approve or decline brfas without having a trial period non controversial technically simple tasks or duplicates of existing tasks especially if performed by trusted bot operators can be speedily approved similarly controversial or commonly declined tasks especially by new editors may be speedily declined valid operations without approval shortcuts wp botuserspace wp botuserspace wp exemptbot wp exemptbot operators may carry out limited testing of bot processes without approval provided that test edits are very low in number and frequency and are restricted to test pages such as the sandbox such test edits may be made from any user account in addition any bot or automated editing process that affects only the operator s or their own userspace user pages user talk pages user s module sandbox pages and subpages thereof and which are not otherwise disruptive may be run without prior approval should bot operators wish to modify or extend the operation of their bots they should ensure that they do so in compliance with this policy small changes for example to fix problems or improve the operation of a particular task are unlikely to be an issue but larger changes should not be implemented without some discussion completely new tasks usually require a separate approval request bot operators may wish to create a separate bot account for each task accounts performing automated tasks without prior approval may be summarily blocked by any administrator bots with administrative rights shortcut wp adminbot wp adminbot bots with administrator rights a k a adminbots are also approved through the general process the bot operator must already be an administrator as with any bot the approval discussion is conducted on two levels community approval for the bot s task this discussion should take place at an appropriate forum such as the administrators noticeboard or the village pump prior to the brfa without a demonstrated need want for such an adminbot the brfa will either be put on hold until this is demonstrated or the bot will be denied approval the technical assessment of the bot s implementation it is recommended that the source code for adminbots be open but should the operator elect to keep all or part of the code not publicly visible they must present such code for review upon request from any bag member or administrator to demonstrate the implementation adminbots should either be run dry without a sysop bit if practical or be run on the operator s main account with its edits clearly marked as such when bag is satisfied that the bot is technically sound they will approve the bot and recommend that it be given both bot and sysop rights the bureaucrat who responds to the flag request acts as a final arbiter of the process and will ensure that an adequate level of community consensus including publicity of approval discussion underlies the approval as adminbots have much more destructive potential than regular bots their operators are expected to monitor them closely during development and trials including after code updates adminbots should be immediately shut down at the first sign of incorrect behavior administrators are allowed to run semi automated admin tools on their own accounts but will be held responsible if those tools go awry neglect while running adminbots and tools constitutes tool misuse if an administrator responsible for one or more adminbots is desysopped their bots should be immediately desysopped at the same time except if the administrator voluntarily stepped down in uncontroversial circumstances appeals and reexamination of approvals shortcut wp botappeal wp botappeal requests for reexamination should be discussed at wikipedia bots noticeboard this may include either appeal of denied bot requests or reexamination of approved bots in some cases requests for comment may be warranted such an examination can result in granting or revoking approval for a bot task removing or placing the account into the bot user group imposing further operational conditions on the bot to maintain approval status bag has no authority on operator behavior or on the operators themselves dispute resolution is the proper venue for that dealing with issues shortcut wp botissue wp botissue minor malfunctions complaints and improvements see also wikipedia bots how to hide a specific bot from your watchlist if you have noticed a problem with a bot have a complaint or have a suggestion to make you should contact the bot operator directly via their user talk page or via the bot account s talk page bot operators are expected to be responsive to the community s concerns and suggestions but please assume good faith and don t panic bugs and mistakes happen and we re all here to build an encyclopedia minor changes and tweaks to the bot behavior usually do not need to be reviewed by the community at large so long as they do not exceed a reasonable interpretation of the bot s original mandate brfa and have consensus for instance a bot approved to archive discussions on a specific wikiproject s page does not need another brfa to change the details of the archiving e g thread age or activity requirements however to begin archiving another projects page the operator should probably submit another brfa which might be speedily approved as another example a bot originally approved to remove deleted categories from articles would need approval to expand its scope to remove deleted files major malfunctions and complaints if the bot is causing a significant problem or the bot operator has not responded and the bot is still causing issues several mechanisms are available to prevent further disruption many bots provide a stop button or means to disable the problematic task on their bot user page this should be tried first followed by a discussion of the issue with the bot operator if no such mechanism is available or if urgent action is needed leave a message at the administrators noticeboard requesting a block for a malfunctioning bot per the noticeboard s guideline you are required to notify the bot operator of the discussion taking place at the noticeboard if you are concerned that a bot is operating outside the established consensus for its task discuss the issue with the bot operator first or try other forms of dispute resolution bag members can act as neutral mediators on such matters if you are concerned that a bot no longer has consensus for its task you may formally appeal or ask for re examination of a bot s approval bot like editing shortcut wp meatbot wp meatbot human editors are expected to pay attention to the edits they make and ensure that they do not sacrifice quality in the pursuit of speed or quantity for the purpose of dispute resolution it is irrelevant whether high speed or large scale edits that a are contrary to consensus or b cause errors an attentive human would not make are actually being performed by a bot by a human assisted by a script or even by a human without any programmatic assistance no matter the method the disruptive editing must stop or the user may end up blocked however merely editing quickly particularly for a short time is not by itself disruptive editors who choose to use semi automated tools to assist their editing should be aware that processes which operate at higher speeds with a higher volume of edits or with less human involvement are more likely to be treated as bots if there is any doubt you should make a bot approval request in such cases the bot approvals group will determine whether the full approval process and a separate bot account are necessary purely cosmetic changes performed by a human editor in a bot like fashion may also be considered disruptive blocking a bot shortcut wp botblock wp botblock administrators may block bot accounts that operate without approval operate in a manner not specified in their approval request or operate counter to the terms of their approval or the bot policy a block may also be issued if a bot operates without being logged in to an account or is logged in to an account other than its own bots which are known to edit while logged out should have assertion or a similar function added to them operators can be notified with bot block message for approved bots that are broken or uw botblock after blocking unapproved bots administrators blocking a user account suspec...