Wikipedia bot

Wikipedia:List of bots by number of edits

No. User Edit count 1 WP 1.0 bot8,391,687 2 Cydebot 6,812,251 3 ClueBot NG5,990,507 4 AnomieBOT5,060,508 5 Yobot 4,732,723 6 InternetArchiveBot4,492,032 7 SmackBot 3,734,324 8 Monkbot3,070,445 9 Addbot 2,838,809 10 EmausBot2,481,175 11 MediaWiki message delivery2,461,110 12 SineBot2,450,409 13 Citation bot2,170,095 14 AAlertBot2,107,822 15 Xqbot1,925,576 16 InceptionBot1,844,453 17 Lowercase sigmabot III1,607,562 18 RjwilmsiBot 1,602,950 19 ClueBot 1,596,818 20 KasparBot 1,549,811 21 PrimeBOT1,530,195 22 GreenC bot1,517,609 23 COIBot1,424,997 24 Cyberbot I1,406,106 25 BattyBot1,373,372 26 RussBot1,337,988 27 Legobot1,326,818 28 AvicBot 1,227,735 29 DeltaQuadBot1,210,470 30 JJMC89 bot III1,172,045 31 KolbertBot 1,166,042 32 SporkBot1,103,155 33 FrescoBot1,032,285 34 The Anomebot21,008,449 35 BG19bot 1,005,055 36 ClueBot III979,139 37 Bender the Bot978,420 38 JJMC89 bot973,268 39 Fbot 960,904 40 BetacommandBot 931,490 41 Luckas-bot 929,662 42 CommonsDelinker809,672 43 Lightbot 791,863 44 AlexNewArtBot 778,467 45 MalnadachBot739,944 46 ZéroBot 704,777 47 XLinkBot701,494 48 Reports bot667,299 49 OrphanBot 654,820 50 ListeriaBot651,304 51 RMCD bot637,652 52 HBC AIV helperbot5602,068 53 MiszaBot III 597,462 54 Helpful Pixie Bot 571,497 55 TXiKiBoT 567,654 56 DPL bot566,210 57 VeblenBot 557,678 58 ListasBot 482,720 59 Thijs!bot 470,128 60 Cyberbot II468,098 61 WikiCleanerBot467,997 62 DatBot462,329 63 VolkovBot 447,718 64 Kingbotk 447,274 65 Erik9bot 439,480 66 Mathbot437,473 67 HasteurBot 436,622 68 Alaibot 434,501 69 BD2412bot 433,217 70 SieBot 421,891 71 HostBot399,531 72 BOTijo 398,373 73 B-bot395,855 74 TedderBot 395,775 75 Xenobot Mk V 393,887 76 D6 393,081 77 JL-Bot372,885 78 EdwardsBot 354,693 79 BU RoBOT 353,949 80 Bluebot 349,597 81 ImageRemovalBot339,640 82 CmdrObot 339,230 83 Full-date unlinking bot 324,022 84 RonBot 321,894 85 DASHBot 318,263 86 BotMultichill310,824 87 ShortDescBot 306,872 88 EarwigBot297,603 89 Magic links bot 291,110 90 YurikBot 278,165 91 VoABot II 274,019 92 BJBot 271,036 93 MiszaBot II 259,776 94 Eubot 259,670 95 ArthurBot 259,345 96 AntiVandalBot 258,750 97 VIAFbot 254,678 98 HBC AIV helperbot7 253,005 99 DumbBOT251,697 100 OAbot239,473 101 Escarbot 235,779 102 CorenSearchBot 235,712 103 SoxBot 235,195 104 MiszaBot I 234,552 105 ImageTaggingBot233,824 106 Amalthea (bot) 231,275 107 MetsBot 230,560 108 FlaBot 222,981 109 SuggestBot216,579 110 RFC bot 216,124 111 DYKUpdateBot213,854 112 DumZiBoT 212,289 113 Polbot 208,184 114 Ops Monitor (WMF) 207,617 115 Filedelinkerbot200,394 116 STBotI 199,275 117 Scsbot199,137 118 Xenobot 197,501 119 Alexbot 196,144 120 SDZeroBot196,112 121 KrimpBot 194,116 122 MartinBot 190,136 123 FastilyBot188,477 124 Dexbot188,130 125 ProteinBoxBot187,912 126 Kbdankbot 184,258 127 DeprecatedFixerBot 182,719 128 MGA73bot 178,674 129 MystBot 177,678 130 Femto Bot 174,552 131 MenoBot173,660 132 BracketBot 173,351 133 MusikBot169,427 134 Chobot167,683 135 YFdyh-bot 166,786 136 PearBOT II165,744 137 HBC Archive Indexerbot 165,272 138 Hazard-Bot164,617 139 Bot1058163,655 140 Tom.Bot 163,010 141 タチコマ robot 161,093 142 Theo's Little Bot 159,404 143 JAnDbot159,117 144 Kumi-Taskbot 158,176 145 Kotbot 157,583 146 SQLBot 153,194 147 DrilBot 152,046 148 Community Tech bot149,597 149 NihlusBOT 149,040 150 GrouchoBot 146,812 151 WikitanvirBot 144,145 152 FairuseBot 143,798 153 WildBot 142,891 154 Zorrobot 142,590 155 CheMoBot 141,565 156 HBC AIV helperbot3 140,330 157 Rambot 139,851 158 HotArticlesBot136,962 159 MartinBotIII 136,346 160 DodoBot 136,137 161 Cewbot134,874 162 TinucherianBot 134,614 163 H3llBot 134,512 164 BHGbot 132,943 165 RedBot 132,316 166 NoomBot 131,906 167 JarBot131,371 168 Tawkerbot2 131,306 169 Citation bot 1 130,044 170 ShepBot 128,863 171 Reedy Bot 128,293 172 GA bot 126,241 173 Detroiterbot 126,164 174 DYKHousekeepingBot125,708 175 SkiersBot 124,334 176 Chris G Bot 3 123,591 177 LaraBot 122,638 178 LaaknorBot 122,478 179 SatyrBot 121,099 180 Hmainsbot1 120,826 181 Ganeshbot 120,433 182 Invadibot 119,128 183 DannyS712 bot116,333 184 ArmbrustBot 115,683 185 Svenbot 114,365 186 BryanBot 112,878 187 PseudoBot 111,736 188 Tawkerbot 110,234 189 Pearle 109,696 190 BernsteinBot108,842 191 DarknessBot 106,029 192 OKBot 103,883 193 Makecat-bot 103,877 194 LucienBOT 103,060 195 Dreamy Jazz Bot101,952 196 Alphachimpbot 100,435 197 ChuispastonBot 100,206 198 718 Bot 99,574 199 Snotbot 98,645 200 WOSlinkerBot98,330 201 JCW-CleanerBot96,956 202 KLBot2 96,688 203 FireflyBot95,779 204 HagermanBot 95,722 205 Numbo3-bot 95,649 206 AlleborgoBot 94,853 207 Robbot94,607 208 28bot 93,387 209 Rei-bot 92,903 210 Josvebot 90,111 211 DFBot 89,742 212 Mr.Z-bot 89,315 213 RM bot 87,489 214 RobotG 86,515 215 Wikinews Importer Bot 86,016 216 QEDKbot 82,799 217 TheSandBot82,639 218 The wubbot 82,402 219 BotMultichillT81,809 220 MiszaBot 81,480 221 CactusBot 81,124 222 SdkbBot79,899 223 DSisyphBot 77,126 224 AvocatoBot 76,551 225 BrownBot 76,066 226 GimmeBot 75,273 227 EnterpriseyBot74,860 228 MilHistBot74,416 229 OgreBot74,322 230 ArticlesForCreationBot 74,117 231 CanisRufus 73,747 232 LivingBot73,264 233 Qbugbot 72,812 234 AdminStatsBot71,979 235 Ahechtbot71,592 236 PhotoCatBot 70,109 237 RibotBOT 69,737 238 TokenzeroBot69,346 239 Redirect fixer 69,018 240 MadmanBot 67,844 241 STBot 67,360 242 Ptbotgourou 66,481 243 HBC AIV helperbot 66,367 244 MoohanBOT 65,282 245 ArticleAlertbot 64,236 246 Erwin85Bot 62,731 247 MifterBot62,692 248 CitationCleanerBot 62,385 249 MastiBot62,165 250 Werdnabot 60,702 251 DemonDays64 Bot 57,803 252 Ralbot 57,708 253 SoxBot V 57,416 254 Thehelpfulbot 56,901 255 Amirobot 56,602 256 DragonBot 56,554 257 STTWbot 56,458 258 MelonBot 56,411 259 FoxBot 56,039 260 BAGBot 56,039 261 Sambot 55,853 262 ClueBot II 55,498 263 TuHan-Bot 55,347 264 MalafayaBot 55,269 265 Idioma-bot 55,031 266 Staeckerbot 54,978 267 CommonsNotificationBot 54,096 268 Acebot 53,978 269 HRoestBot 53,714 270 BogBot 53,132 271 JackieBot 53,084 272 Maelgwnbot 52,548 273 Pi bot52,414 274 KamikazeBot 52,375 275 VoxelBot 52,137 276 Uncle G's major work 'bot 51,901 277 Shadowbot3 51,520 278 Drinibot 51,324 279 PotatoBot 51,239 280 MarshBot 50,214 281 DefaultsortBot 48,995 282 Rezabot 48,194 283 ReferenceBot 48,157 284 SharedIPArchiveBot 46,643 285 Tangobot 46,250 286 Thadius856AWB 45,945 287 PixelBot 45,850 288 DyceBot 45,604 289 WatchlistBot 45,422 290 Stefan2bot 45,414 291 Gdrbot 45,158 292 ProcBot45,129 293 DOI bot 44,709 294 SashatoBot 44,607 295 TobeBot 44,321 296 HBC AIV helperbot11 44,166 297 AntiSpamBot 44,141 298 SDPatrolBot 44,001 299 SassoBot 43,862 300 Rubinbot 43,100 301 TPBot 43,054 302 JYBot 42,944 303 Bibcode Bot 42,789 304 People-photo-bot 42,484 305 DannyS712 bot III42,268 306 Lowercase sigmabot II42,240 307 SilvonenBot 41,981 308 Sandbot 41,821 309 MenasimBot 41,794 310 Muro Bot 41,441 311 DinoBot2 41,362 312 AP.BOT 41,147 313 BotanyBot 41,140 314 Sethbot 41,094 315 Jogersbot 40,997 316 WugBot40,763 317 Petan-Bot 40,696 318 Obersachsebot 40,640 319 WinBot 39,167 320 STBotD 39,144 321 Rick Bot39,081 322 ContinuityBot 38,824 323 SteveBot 38,566 324 MusikBot II38,452 325 HBC AIV helperbot2 38,338 326 Eskimbot 37,916 327 Ohms Law Bot 37,898 328 Δbot 37,802 329 D'ohBot 37,798 330 DHN-bot~enwiki 37,354 331 YiFeiBot36,626 332 J Milburn Bot 36,626 333 ChzzBot IV 35,991 334 Ripchip Bot 35,574 335 FeedBot 35,419 336 PipepBot 35,378 337 KingpinBot 35,361 338 Scepbot 34,828 339 MifterBot I 33,655 340 BOTarate 33,597 341 William Avery Bot32,979 342 One bot 32,540 343 Yapperbot32,356 344 FACBot32,343 345 Guanabot 32,249 346 CapitalBot 31,821 347 KevinBot 31,446 348 SPCUClerkbot 30,768 349 HBC NameWatcherBot 30,439 350 CSDWarnBot 30,410 351 AMbot 30,053 352 SoxBot III 29,833 353 AnomieBOT III29,772 354 VoABot 29,709 355 Curpsbot-unicodify 29,655 356 JeffGBot 29,639 357 TjBot 29,118 358 Merge bot28,989 359 Commander Keane bot 28,778 360 TaBOT-zerem 28,640 361 T13bot 28,565 362 ZackBot 27,860 363 Fluxbot 27,634 364 MerlIwBot 27,490 365 Android Mouse Bot 2 27,380 366 LyricsBot 27,368 367 Mjbmrbot 27,077 368 Whobot 26,807 369 PoccilScript 26,798 370 PbBot 26,750 371 Gnome (Bot) 26,658 372 BoxCrawler 26,608 373 KarlsenBot 26,553 374 IznoBot 26,524 375 JBradley Bot 26,473 376 COBot 26,326 377 Chartbot 26,135 378 Broadbot 26,088 379 Lowercase sigmabot 26,036 380 Phe-bot 25,877 381 A4bot 25,852 382 Comics-awb 25,748 383 DYKadminBot 25,702 384 JoeBot 25,683 385 .anacondabot 25,534 386 Dinamik-bot 25,456 387 JhsBot25,244 388 DASHBotAV 24,938 389 Snowbot 24,737 390 RonaldBot 24,323 391 AfDBot 24,257 392 RBot~enwiki 23,992 393 MPUploadBot 23,543 394 ^demonBot2 23,458 395 John Bot 23,415 396 ChzzBot II 23,315 397 RscprinterBot23,229 398 AWeenieBot 22,717 399 HBC AIV helperbot4 22,501 400 Pegasusbot 22,499 401 Synthebot 22,264 402 OverlordQBot 22,185 403 AndersBot 21,983 404 NekoDaemon 21,840 405 WikiStatsBOT 21,681 406 BOT-Superzerocool 21,402 407 Harej bot 21,332 408 CarsracBot 21,327 409 Tawkerbot4 21,149 410 Tom's Tagging Bot 20,787 411 PearBOT20,742 412 SpBot 20,713 413 NationalRegisterBot 20,687 414 EmxBot 20,479 415 ErfgoedBot20,297 416 PeerReviewBot 20,113 417 RileyBot 20,030 418 AlnoktaBOT 19,917 419 Vagobot 19,756 420 EranBot19,705 421 WelcomerBot 19,535 422 Legobot II 19,501 423 BenzolBot 19,420 424 SoxBot II 19,239 425 BorgardeBot 19,099 426 SoxBot IV 19,086 427 Vina-iwbot~enwiki 19,059 428 Seedbot 18,964 429 RoboMaxCyberSem 18,904 430 Zwobot 18,852 431 JaGaBot 18,801 432 Arbitrarily0Bot 18,588 433 Rschen7754bot 18,571 434 Grafikbot 18,549 435 Taxobot 1 18,394 436 MerlLinkBot 17,943 437 VWBot 17,907 438 SQLBot-Hello 17,883 439 CobraBot 17,825 440 Locobot 17,725 441 LordAnubisBOT 17,720 442 MBisanzBot 17,711 443 Kyle the bot 17,245 444 LostBot 17,136 445 EdoBot 16,918 446 SelketBot 16,870 447 OmniBot 16,811 448 Justincheng12345-bot 16,730 449 UnCatBot 16,725 450 Sagabot 16,603 451 XLerateBot 16,419 452 XyBot 16,275 453 Roboto de Ajvol 16,250 454 NW557Bot 16,135 455 NjardarBot 16,082 456 Alph Bot 16,072 457 Giggabot 15,945 458 UsuallyNonviolentBot 15,822 459 RobotE 15,723 460 UTRSBot 15,600 461 Citation bot 2 15,591 462 KnightRider~enwiki 15,538 463 DorganBot 15,527 464 KocjoBot~enwiki 15,464 465 WPArkansas Bot 15,268 466 TTObot 15,246 467 NetBot 15,210 468 GrinBot~enwiki 15,203 469 ST47Bot15,064 470 MondalorBot 14,786 471 CounterVandalismBot 14,742 472 DRN clerk bot 14,717 473 SSTbot 14,492 474 MauritsBot 14,490 475 WeggeBot 14,370 476 FlBot 14,324 477 Jumbuck 14,218 478 Zorglbot 13,933 479 MSBOT 13,809 480 KevinalewisBot 13,601 481 Muninnbot13,474 482 Lucasbfrbot 13,383 483 RebelRobot 13,364 484 Mdann52 bot 13,297 485 Taxobot 7 13,117 486 JdforresterBot 13,077 487 RaptureBot 13,074 488 DixonDBot 13,058 489 Chem-awb 12,956 490 ZhBot 12,919 491 TheMagikBOT 12,910 492 Tsca.bot 12,824 493 Anybot 12,812 494 Almabot 12,592 495 MDanielsBot12,590 496 LinkFA-Bot 12,478 497 ArkyBot 12,325 498 TechBot 12,222 499 AccReqBot 12,203 500 Mairibot 12,178 501 Qwerfjkl (bot)12,144 502 CopyToWiktionaryBot 12,043 503 RoryBot 11,939 504 Lonjers french region rename bot 11,910 505 SD5bot 11,897 506 Bota47 11,897 507 BotKung 11,896 508 Cerabot~enwiki 11,858 509 StatisticianBot 11,672 510 MajavahBot11,659 511 CocuBot 11,625 512 Jitse's bot 11,518 513 MenoBot II 11,500 514 Ligulembot 11,449 515 HersfoldArbClerkBot 11,398 516 BsherrAWBBOT 11,152 517 RockfangBot 11,130 518 Gerakibot 11,103 519 Chlewbot 11,087 520 SimplexityBot 11,005 521 HiW-Bot 10,986 522 AkhtaBot 10,976 523 Crypticbot 10,967 524 SteenthIWbot 10,638 525 Luasóg bot 10,638 526 SamatBot 10,493 527 Kasirbot 10,290 528 ThePhantomBot 10,244 529 MessageDeliveryBot 10,187 530 Syrcatbot 10,115 531 CrimsonBot 9,941 532 HerculeBot 9,923 533 YpnBot 9,805 534 StigBot 9,793 535 KslotteBot 9,759 536 EsquivalienceBot 9,656 537 Mentibot 9,642 538 John Bot III 9,588 539 DarafshBot 9,561 540 Darkicebot 9,549 541 Muhbot 9,528 542 Mz7 (bot)9,517 543 Anchor Link Bot 9,446 544 McM.bot 9,247 545 PkbwcgsBot 9,244 546 Chris G Bot 8,961 547 WebCiteBOT 8,940 548 Louperibot 8,903 549 El bot de la dieta 8,891 550 HtonlBot 8,869 551 JCbot 8,820 552 Peelbot 8,810 553 DefconBot 8,805 554 VVVBot 8,665 555 Pageview bot 8,659 556 GeneralBotability8,654 557 Wherebot 8,585 558 RotlinkBot 8,496 559 GargoyleBot 8,480 560 BrokenAnchorBot 8,349 561 KittyBot 8,201 562 ENewsBot 8,161 563 EarwigBot I 8,124 564 VixDaemonBot 8,090 565 Pokbot 8,088 566 FlagBot 8,062 567 SpellingBot 7,955 568 PDFbot 7,943 569 LatitudeBot 7,911 570 Aksibot 7,808 571 Estirabot 7,801 572 Maksim-bot 7,747 573 Nallimbot 7,620 574 TohaomgBot 7,553 575 AFD Bot 7,549 576 GurchBot 7,421 577 Galobot7,395 578 WoodwardBot7,394 579 ImageBacklogBot 7,297 580 ClueBot VI 7,185 581 Image-req-proj-bot 7,161 582 IluvatarBot 7,142 583 Uncle G's 'bot 7,072 584 PNG crusade bot 7,042 585 TPO-bot 7,022 586 DomBot 6,861 587 Ebrambot 6,852 588 Margosbot~enwiki 6,843 589 StatusBot 6,841 590 Jotterbot 6,715 591 AlanBOT 6,712 592 TweetCiteBot 6,685 593 Wiki Feed Bot 6,617 594 EarwigBot III 6,614 595 EBot IV 6,582 596 DeadBot 6,516 597 Purbo T 6,489 598 Le Pied-bot~enwiki 6,363 599 NedBot 6,336 600 NihiltresBot 6,276 601 Abotzi 6,249 602 BodhisattvaBot 6,242 603 CountryBot 6,217 604 FileBot 6,137 605 AfDStatBot 6,069 606 MTSbot~enwiki 5,937 607 ChenzwBot 5,869 608 EssjayBot 5,742 609 BenoniBot~enwiki 5,717 610 SEWilcoBot 5,680 611 VedeBOT 5,663 612 MediationBot 5,654 613 SeveroBot 5,647 614 YonaBot 5,580 615 Martin's bot 5,485 616 WikiDreamer Bot 5,464 617 NTBot~enwiki 5,404 618 WaldirBot 5,296 619 HasharBot~enwiki 5,288 620 LawBot 5,266 621 MMABot 5,265 622 Kakashi Bot 5,248 623 AnomieBOT II5,229 624 Milk's Favorite Bot 5,168 625 UcuchaBot 5,146 626 BotPuppet 5,110 627 Lt-wiki-bot 5,065 628 RichBot5,053 629 WolterBot 5,029 630 Android Mouse Bot 3 5,022 631 EBot II 4,957 632 XZeroBot 4,901 633 RefDeskBot 4,897 634 CohesionBot 4,843 635 PlangeBot 4,793 636 TuvicBot 4,784 637 Andrea105Bot 4,702 638 TinucherianBot II 4,683 639 Hxhbot 4,602 640 Skumarlabot 4,583 641 AmphBot 4,582 642 Beastie Bot 4,575 643 Movses-bot 4,513 644 ClickBot 4,448 645 GeorgeMoneyBot-status 4,426 646 JVbot 4,376 647 ZsinjBot 4,372 648 NukeBot 4,368 649 GhalyBot 4,330 650 KaiserbBot 4,276 651 PlankBot 4,267 652 Nobot~enwiki 4,252 653 AstRoBot 4,229 654 HBC AIV helperbot 8 4,228 655 NolBot 4,218 656 FRadical Bot 4,159 657 WuBot 4,125 658 Ugur Basak Bot~enwiki 4,096 659 Pathosbot 4,064 660 Mgmbot 4,045 661 FANSTARbot 4,041 662 Sahimrobot 4,017 663 MuZebot 4,002 664 SelectionBot 3,988 665 ARSBot 3,960 666 Ginosbot 3,951 667 JamietwBot 3,895 668 MediationBot1 3,850 669 Adlerbot 3,842 670 EleferenBot 3,833 671 Grammarbot 3,795 672 SundarBot 3,773 673 Jayden54Bot 3,769 674 EarwigBot II 3,699 675 Android Mouse Bot 3,650 676 SoxBot VI 3,640 677 AdambroBot 3,624 678 ClueBot Commons 3,608 679 OldMedcabBot 3,588 680 Image Screening Bot 3,583 681 WolfBot 3,497 682 WarddrBOT 3,438 683 ToePeu.bot 3,434 684 Emijrpbot3,432 685 PolarBot 3,417 686 SoxBot VIII 3,394 687 AstaBOTh15 3,367 688 People-n-photo-bot 3,364 689 PowerBOT 3,345 690 FA Template Protection Bot 3,295 691 NotifyBot 3,249 692 AvicBot2 3,248 693 SpaceFactsBot3,209 694 MonoBot 3,179 695 Zbot370 3,175 696 DYKBot 3,174 697 ChandlerMapBot 3,170 698 R Delivery Bot 3,162 699 Yonidebot 3,147 700 DcoetzeeBot~enwiki 3,108 701 N-Bot 3,085 702 Minsbot 3,052 703 VahurzpuBot3,047 704 VFD Bot 3,029 705 Albambot 2,977 706 VRTS Migration Bot 2,940 707 Swimmingbot-awb 2,920 708 Portal namespace initialisation script 2,838 709 MinusBot 2,813 710 Jmax-bot 2,811 711 DirlBot 2,806 712 Elissonbot 2,801 713 FiriBot 2,785 714 GurchBot 2 2,757 715 BepBot 2,752 716 LemmeyBOT 2,737 717 Citation bot 3 2,728 718 MartinBotIV 2,696 719 Vini 17bot5 2,690 720 KadaneBot 2,672 721 ClueBot IV 2,665 722 Taxobot 2 2,663 723 DisambigBot 2,662 724 AntiCompositeBot2,627 725 The Anomebot 2,596 726 PDBbot 2,565 727 Admrbot 2,532 728 ImageTagBot 2,513 729 EssjayBot III 2,492 730 Amolbot 2,488 731 Ryan Vesey Bot 2,465 732 H92Bot 2,439 733 Tanhabot 2,414 734 Diego Grez Bot 2,406 735 Lucia Bot 2,372 736 Signpost Book Bot 2,354 737 ProtectionTaggingBot 2,351 738 Byrialbot 2,339 739 Bot-Schafter 2,332 740 Bot523 2,310 741 NodBot 2,273 742 Philosopher-Bot 2,237 743 TestEditBot 2,228 744 DustyBot 2,225 745 Chrisbot 2,218 746 BetBot~enwiki 2,205 747 MahdiBot 2,183 748 Commons fair use upload bot (usurped) 2,141 749 Blood Oath Bot 2,122 750 RagesossBot 2,119 751 TottyBot 2,110 752 John Bot II 2,084 753 Kl4m-AWB 2,072 754 RFRBot 2,054 755 AmeliorationBot 2,006 756 CeraBot 1,977 757 Bikabot 1,967 758 LDBot 1,950 759 NrhpBot 1,922 760 TAP Bot 1,920 761 Bocianski.bot 1,889 762 SvickBOT 1,889 763 FaleBot 1,872 764 Zxabot 1,835 765 CrazynasBot 1,808 766 IPTaggerBot 1,808 767 Ver-bot 1,777 768 HarrivBOT 1,776 769 Rfambot 1,774 770 Kwjbot 1,738 771 Ocobot 1,730 772 KolBot 1,728 773 PascalBot 1,710 774 EjsBot 1,697 775 SpillingBot 1,690 776 CricketBot 1,676 777 SoxBot X 1,675 778 Snobot 1,660 779 John of Reading Bot 1,642 780 RobotJcb 1,631 781 JabbaTheBot 1,623 782 KonstableBot 1,587 783 ListGenBot 1,575 784 WikiBotas 1,556 785 Wybot 1,541 786 Peti610botH 1,526 787 Plasticbot 1,522 788 Ramaksoud2000Bot 1,522 789 FPBot 1,486 790 Robert SkyBot 1,483 791 Italic title bot 1,483 792 Texvc2LaTeXBot 1,462 793 Android Mouse Bot 4 1,448 794 GrooveBot 1,410 795 InfoboxBot 1,402 796 MagnusA.Bot 1,381 797 NekoBot 1,379 798 Redrocketbot 1,375 799 ABot 1,372 800 RoboServien 1,349 801 SMS Bot 1,344 802 SoxBot VII 1,340 803 AzaBot 1,321 804 BotdeSki 1,312 805 Slobot 1,297 806 Fetofsbot 1,292 807 Eivindbot 1,279 808 Snaevar-bot 1,275 809 AilurophobiaBot 1,269 810 DeadLinkBOT 1,256 811 Portal box bot 1,253 812 Yet Another Redirect Cleanup Bot 1,235 813 Kisbesbot 1,221 814 Citation bot 4 1,212 815 ExpertIdeasBot 1,206 816 O bot 1,198 817 Manishbot 1,172 818 BendelacBOT 1,168 819 AudeBot 1,144 820 SheepBot 1,126 821 EnzaiBot 1,103 822 Nixbot 1,102 823 MastersBot 1,081 824 GracenotesBot 1,080 825 AntiAbuseBot 1,075 826 WxBot 1,062 827 Janna Isabot 1,045 828 SantoshBot 1,035 829 7SeriesBOT 1,019 830 Analphabot 1,017 831 StefanBot 1,010 832 TolBot982 833 Legobot III 966 834 DinoBot 952 835 Botpankonin 950 836 Ficbot 950 837 SwiftBot 934 838 Rameshngbot 926 839 AndreasJSbot 908 840 SDPatrolBot II 900 841 EBot 896 842 Alirezabot 885 843 Razibot 883 844 Anibot 880 845 NobelBot 878 846 Nono le petit robot~enwiki 867 847 Mulder416sBot 867 848 TARBOT 855 849 MCBot 849 850 WODUPbot 840 851 NeuRobot 838 852 Antischmitzbot 834 853 Taxobot 828 854 VP-bot 820 855 Fetofsbot2 810 856 ChzzBot 804 857 Joe's Olympic Bot 797 858 Fajrbot 795 859 ElMeBot 785 860 Stwalkerbot 783 861 MedcabBot 760 862 AutocracyBot 759 863 MartinBotII 758 864 GnawnBot 724 865 JhealdBot 712 866 MandelBot 711 867 Xphoisbot 689 868 BaldBot 680 869 Caypartisbot 680 870 Planktonbot 673 871 ChessBOT 673 872 Botz~enwiki 662 873 DpmukBOT 657 874 GZ-Bot 655 875 PsychAWB 653 876 TypoBot 646 877 Fritzbot 643 878 Bitbotje643 879 Bot24 639 880 Newsletterbot 639 881 Danumber1bot 637 882 LinkBot 636 883 ArbClerkBot631 884 Bgbot 624 885 TheJoshBot 621 886 Robotic Garden 618 887 DrTrigonBot 615 888 Dark Shikari Bot 615 889 IndentBot609 890 DYKReviewBot 602 891 SprinterBot 589 892 BotCompuGeek 586 893 Innocent iwbot 575 894 DEagleBot 570 895 NeraBot 552 896 AMABot 551 897 AlptaBot 546 898 NotificationBot 545 899 Halibott 544 900 KiranBOT542 901 FireflyBot II 541 902 VsBot 536 903 JJMC89 bot II536 904 VandalCountBot 529 905 Diligent Terrier Bot 527 906 M7bot 525 907 Riccardobot 521 908 Kal-El-Bot 515 909 A-lú-mih-bot 508 910 HBC archive builderbot 506 911 UncatTemplateBot 505 912 Kurando-san 497 913 Botx 496 914 ListManBot 474 915 Naudefjbot~enwiki 474 916 DrFO.Tn.Bot 441 917 Tawbot~enwiki 439 918 Selmobot 437 919 DavidWSBot 435 920 HujiBot 433 921 BenjBot 432 922 BoricuaBot 430 923 AHbot 425 924 AsgardBot 425 925 Manubot 419 926 Sumibot 413 927 RoboDick~enwiki 410 928 PorthosBot 405 929 EgressBot 401 930 MelsaranAWB 393 931 Madhubot 391 932 JJBot 389 933 RSElectionBot 387 934 FritzpollBot 380 935 KaldariBot 378 936 NilfaBot 370 937 MalarzBOT367 938 SportsStatsBot 363 939 Simplebot 362 940 AloysiusLiliusBot 358 941 EddieBot 355 942 Gabrielchihonglee-Bot 344 943 OrophinBot 338 944 PockBot 337 945 AZatBot~enwiki 330 946 Denbot 329 947 Milk's Favorite Bot II 329 948 MercuryBot 326 949 Maintenance script325 950 Pfft Bot~enwiki 325 951 Krdbot321 952 SVGBot 320 953 VeinorBot 320 954 PALZ9000 315 955 Mobius Bot 309 956 Rtz-bot 309 957 QOTDBot 307 958 AswnBot 306 959 MrVanBot 306 960 PaievBot 303 961 Fz29bot 301 962 Eybot~enwiki 283 963 IcalaniseBot 282 964 QualiaBot 280 965 EdBot 267 966 Dapperbot 262 967 KuduBot 259 968 DeliveryBot 258 969 LSG1-Bot 253 970 Orphaned talkpage deletion bot 250 971 Egmontbot 249 972 PCbot 242 973 NohatBot 239 974 XeBot 237 975 Flow talk page manager 235 976 JMuniBot 232 977 BücherBot 226 978 SusBot~enwiki 224 979 Botryoidal 223 980 'zinbot220 981 PxBot 212 982 MichaelBillingtonBot 211 983 The Anonybot 209 984 ReigneBOT 201 985 ChzzBot III 193 986 CensusBot 192 987 HMBot~enwiki 192 988 Kgsbot 189 989 RetractionBot 188 990 DottyQuoteBot 178 991 OpenlibraryBot 173 992 SandgemBot 158 993 Kaspobot 157 994 Tuonela 156 995 Kumar Appaiah Bot 148 996 MauchoBot 142 997 WMUKBot 140 998 Rabbot 137 999 Seppi333Bot 137 1000 SharafBot 137
Sours: https://en.wikipedia.org/wiki/Wikipedia:List_of_bots_by_number_of_edits

Wikipedia:Bot policy

Wikipedia policy page

This page in a nutshell: Automated editing processes, known as "bots", must be harmless and useful, have approval, use separate user accounts, and be operated responsibly. This wiki also allows global bots to be run, subject to local requirements.

Bot policy covers the operation of all bots and automated scripts used to provide automation of Wikipedia edits, whether completely automated, higher speed, or simply assisting human editors in their own work. It also covers the work of the Bot Approvals Group (BAG), which supervises and approves all bot-related activity from a technical and quality-control perspective on behalf of the English Wikipedia community. Other languages may have their own bot policies which differ from this one.

Definitions

Main page: Wikipedia:Bots/Dictionary

Shortcut

  • Bots (short for "robots") generally make automated changes or actions. After launching the bot, an assumption can be made that there is no further need for human decision-making.
  • Assisted or semi-automated editing covers specifically lower-speed tools and scripts that can assist users to make decisions but leave the actual decision up to the user (see Assisted editing guidelines below).
  • Scripts are personalized scripts (typically, but not always, written in JavaScript) that may automate processes, or may merely enhance the existing MediaWiki interface.
  • The Bot Approvals Group (BAG) is a group of users with appropriate technical skills and wiki-experience, whose members are approved by the community to oversee and make decisions on bot activity and on-wiki operation for the community. The BAG also determine the classification as bot or assisted editing, in ambiguous cases. Formal work by MediaWiki developers is outside the scope of this policy.

Bot usage

Shortcut

Because bots

  • are potentially capable of editing far faster than humans can; and
  • have a lower level of scrutiny on each edit than a human editor; and
  • may cause severe disruption if they malfunction or are misused;

the community expects bots to meet high standards before they are approved for use on designated tasks. The operation of unapproved bots, or use of approved bots in ways outside their approved conditions of operation, is prohibited and may in some cases lead to blocking of the user account and possible sanctions for the operator. Note that high-speed semi-automated editing may effectively be considered bots in some cases (see WP:MEATBOT), even if performed by a human editor. If in doubt, check.

Bot accounts

Shortcut

See also: Wikipedia:Username policy

Contributors should create a separate account in order to operate a bot. The account's name should identify the bot function (e.g. <Task>Bot), or the operator's main account (e.g. <Username>Bot). In all cases, it should be immediately clear that the edits are made by an automated account, which is usually achieved by including Bot at the end of the account name. Bots must edit only while logged into their account. Tools not considered to be bots do not require a separate account, but some users do choose to make separate accounts for non-bot but high-speed editing.

The contributions of a bot account remain the responsibility of its operator, whose account must be prominently identifiable on its user page. In particular, the bot operator is responsible for the repair of any damage caused by a bot which operates incorrectly. All policies apply to a bot account in the same way as to any other user account. Bot accounts are considered alternative accounts of their operator. To ensure compliance with WP:BOTCOMM, IP editors wishing to operate a bot must first register an account before operating a bot.

Bot accounts should not be used for contributions that do not fall within the scope of the bot's designated tasks. In particular, bot operators should not use a bot account to respond to messages related to the bot. Bot operators may wish to redirect a bot account's discussion page to their own.

The "bot" flag

Shortcut

Bot accounts will be marked by a bureaucrat as being in the "bot" user group upon BAG request. This flag reduces some of the technical limits imposed by the MediaWiki software. Edits by such accounts are hidden by default within recent changes. Bot accounts may also be added to the "copyviobot" user group upon BAG request; this flag allows use of the API to add metadata to edits for use in the new pages feed.

Activity requirements

Bot accounts that have had no logged actions or edits for two years, where the listed operator has also had no logged actions or edits for two years, will be deauthorized. Following a one-week notification period on the bots noticeboard, and the operator's talk page, prior task approvals will be considered expired and bot flags will be removed. Should the operator return and wish to reactivate the bot, a new request for approval must be completed.

Bots directed to edit by other users

Shortcut

Some bots allow other editors to direct the bot to make an edit or other action. It is recommended and preferable to use OAuth to make the edit on the user's account directly. However, it can be permissible to instead make these edits via a bot account (particularly if necessary due to the actions being privileged), provided the following conditions are met:

  1. Disclosure: The identity of the Wikipedia user directing the edit/action must be publicly disclosed, typically by linking the username in the edit summary.
  2. Verification: The identity of the Wikipedia user must be reliably verified to the bot in a manner not easily faked, bypassed or avoided. Suitable methods include a non-trivial password, IP restrictions, wiki login or IRC hostname. If the bot is used to make sensitive actions stronger methods of verification may be required.
  3. Competence: All users directing a bot must have the required skill and knowledge to ensure their actions are within community consensus.

Bot requirements

Shortcut

In order for a bot to be approved, its operator should demonstrate that it:

  1. is harmless
  2. is useful
  3. does not consume resources unnecessarily
  4. performs only tasks for which there is consensus
  5. carefully adheres to relevant policies and guidelines
  6. uses informative messages, appropriately worded, in any edit summaries or messages left for users

The bot account's user page should identify the bot as such using the {{bot}} tag. The following information should be provided on, or linked from, both the bot account's userpage and the approval request:

  • Details of the bot's task (or tasks)
  • Whether the bot is manually assisted or runs automatically
  • When it operates (continuously, intermittently, or at specified intervals), and at what rate

Performance

Shortcut

While performance is not generally an issue, bot operators should recognize that a bot making many requests or editing at a high speed has a much greater effect than the average contributor. Operators should be careful not to make unnecessary Web requests, and be conservative in their editing speed. Sysadmins will inform the community if performance issues of any significance do arise, and in such situations, their directives must be followed.

  • Bots in trial periods, and approved bots performing all but the most urgent tasks, should be run at a rate that permits review of their edits when necessary.
  • Unflagged bots should edit more slowly than flagged bots, as their edits are visible in user watchlists.
  • The urgency of a task should always be considered; tasks that do not need to be completed quickly (for example, renaming categories) can and should be accomplished at a slower rate than those that do (for example, reverting vandalism).
  • Bots' editing speed should be regulated in some way; subject to approval, bots doing non-urgent tasks may edit approximately once every ten seconds, while bots doing more urgent tasks may edit approximately once every five seconds.
  • Bots editing at a high speed should operate more slowly during peak hours (12:00–04:00 UTC), and days (middle of the week, especially Wednesdays and Thursdays) than during the quietest times (weekends).
  • Bots' editing speed may also be adjusted based on replica database server lag; this allows bots to edit more quickly during quiet periods while slowing down considerably when server load is high. This can be achieved by appending an extra parameter to the query string of each requested URL; see mw:Manual:Maxlag parameter for more details.

Bots that download substantial portions of Wikipedia's content by requesting many individual pages are not permitted. When such content is required, download database dumps instead. Bots that require access to run queries on Wikipedia databases may be run on Wikimedia Toolforge; such processes are outside the scope of this policy.

Good communication

Shortcut

See also: General notice to bot owners about edit summaries

Users who read messages or edit summaries from bots will generally expect a high standard of cordiality and information, backed up by prompt and civil help from the bot's operator if queries arise. Bot operators should take care in the design of communications, and ensure that they will be able to meet any enquiries resulting from the bot's operation cordially, promptly, and appropriately. Issues and enquiries are typically expected to be handled on the English Wikipedia. Pages reachable via unified login, like a talk page at Commons or at Italian Wikipedia could also be acceptable, so long at it is clear on both the bot page and the bot's talk page that this is where comments should be directed, and that the landing page is not confusing to an English speaker. External sites like Phabricator or GitHub (which require separate registration or do not allow for IP comments) and email (which can compromise anonymity) can supplement on-wiki communication, but do not replace it. At a minimum, the operator should ensure that other users will be willing and able to address any messages left in this way if they cannot be sure to do so themselves. This is a condition of operation of bots in general.

Note that you can enable email notifications of pings and talk page messages in the notification section of your bot account's preferences.

Configuration tips

Shortcut

Bot operators may wish to implement the following features, depending on the nature of the bot's tasks:

  • Bots which deliver notices and newsletters are encouraged to provide a method of opting out of non-critical messages, especially when posting on user talk pages. Instructions for opting out can then be advertised both on the bot user page (example) and on the message delivered (example).
  • Bots which edit many pages, but may need to be prevented from editing particular pages, can do so by interpreting {{Bots}}; see the template page for an explanation of how this works.
  • Bots which "clean up" in response to non-vandalism user edits may honor {{in use}} to help avoid edit conflicts, either by checking for the presence of that template (and redirects) or the category Category:Pages actively undergoing a major edit. The template's documentation states that a bot that honors {{in use}} may ignore the template if it has been more than 2 hours since the last edit.
  • Providing some mechanism which allows contributors other than the bot's operator to control the bot's operation is useful in some circumstances – the bot can be enabled or disabled without resorting to blocks, and could also be configured in other ways. For example, the bot could check the contents of a particular page and act upon the value it finds there. If desired, such a page could then be protected or semi-protected to prevent abuse. Bot operators doing this should bear in mind that they retain all responsibility for their bot account's edits.
  • To avoid unnecessary blocks, the bot may use assertion to prevent editing if it is logged out. New bots, and bots which have previously edited while logged out, are required to use assertion.

Authors of bot processes are encouraged, but not required, to publish the source code of their bot.

Restrictions on specific tasks

Categorization of people

Shortcut

Assignment of person categories should not be made using a bot. Before adding sensitive categories to articles by bot, the input should be manually checked article by article, rather than uploaded from an existing list in Wikipedia. (See Wikipedia:Categorization of people.)

Context-sensitive changes

Shortcuts

Unsupervised bot processes should not make context-sensitive changes that would normally require human attention, as accounting for all possible false positives is generally unfeasible. Exceptionally, such tasks may be allowed if – in addition to having consensus – the operator can demonstrate that no false positives will arise (for example, a one-time run with a complete list of changes from a database dump) or there is community consensus to run the task without supervision (for example, vandalism reversion with a community-accepted false positive rate).

Examples of context-sensitive changes include, but are not limited to:

  • Correcting spelling, grammar, or punctuation mistakes.
  • Converting words from one regional variation of English to another.
  • Applying context-sensitive templates, such as {{weasel word}}.
  • Changing HTML entities to Unicode characters whenever the Unicode character might be difficult to identify visually in edit-mode, per the Manual of Style.

Cosmetic changes

Shortcut

Cosmetic changes to the wikitext are sometimes the most controversial, either in themselves or because they clutter page histories, watchlists, and/or 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, changing whitespace in bulleted vertical lists);
  • 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 to ); 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 to )

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.

While this policy applies only to bots, human editors may also wish to follow this guidance for the reasons given here, especially if making such changes on large scales. 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.

Interwiki links

Shortcut

See also: Help:Interlanguage links, Wikipedia:Wikidata, and m:Interwiki bot

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

See also: Wikipedia:Bot created articles

Shortcuts

Any large-scale automated or semi-automated content page creation task must be approved at Wikipedia:Bots/Requests for approval. This requirement initially applied to articles, but has since been expanded to include all "content pages", broadly meaning pages designed to be viewed by readers through the mainspace. These include articles, most visible categories, files hosted on Wikipedia, mainspace editnotices, and portals. While no specific definition of "large-scale" was decided, a suggestion of "anything more than 25 or 50" was not opposed. It is also strongly encouraged (and may be required by BAG) that community input be solicited at WP:Village pump (proposals) and the talk pages of any relevant WikiProjects. Bot operators must ensure that all creations are strictly within the terms of their approval.

Alternatives to simply creating mass quantities of content pages include creating the pages in small batches or creating the content pages as subpages of a relevant WikiProject to be individually moved to public facing space after each has been reviewed by human editors. While use of these alternatives does not remove the need for a BRFA, it may garner more support from the community at large.

Note that while the WP:MEATBOT-like creation of non-content pages (such as redirects from systematic names, or maintenance categories) is not required to go through a formal BRFA by default, WP:MEATBOT still applies.

Approval process

Shortcut

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 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

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

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:

  1. 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.
  2. 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

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

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

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.

Blocking a bot

Shortcut

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 suspected of operating an unapproved bot or an approved bot in unapproved ways should soft-block indefinitely.

Other bot-related matters

Bot Approvals Group

Main page: Wikipedia:Bot Approvals Group

Shortcut

Members of the group are experienced in writing and running bots, have programming experience, understand the role of the Bot Approvals Group (BAG) in the BRFA process, and understand Wikipedia's bot policy. Those interested in joining the group should make a post at WT:BAG explaining why they would be a good member of the team and outlining past experience, and then should advertise the discussion at WP:AN, WP:VPM, WT:BOTPOL and WP:BOTN. After seven days, an uninvolved bureaucrat will close the discussion.

After two years without any bot-related activity (such as posting on bot-related pages, posting on a bot's talk page, or operating a bot), BAG members will be retired from BAG following a one-week notice. Retired members can re-apply for BAG membership as normal if they wish to rejoin the BAG.

Assisted editing guidelines

Shortcuts

Assisted editing, also known as semi-automated editing, covers the use of tools which assist with repetitive tasks, but do not alter Wikipedia's content without some human interaction. Examples of this include correcting typographical errors, fixing links to disambiguation pages, cleaning up vandalism, and stub sorting.

Contributors intending to make a large number of assisted edits are advised to first ensure that there is a clear consensus that such edits are desired. Editors may wish to indicate consensus for the task, if it is not already clear, in edit summaries and/or on the user or talk page of the account making the contributions. Contributors may wish to create a separate user account in order to do so; such accounts should adhere to the policy on multiple accounts. A bot account should not be used for assisted editing, unless the task has been through a BRFA.

While such contributions are not usually considered to constitute use of a bot, semi-automated processes that 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 an approval request. In such cases, the Bot Approvals Group will determine whether the full approval process and a separate bot account are necessary. Note that any large-scale semi-automated content page creation requires a BRFA.

Authors of assisted editing tools are permitted to create their own approval mechanism for that tool; if bot approval is required for use of the tool, this is in addition to, not instead of, the normal approval request process. AutoWikiBrowser is an example of a tool with such a mechanism. Release of the source code for assisted editing tools is, as with bots, encouraged but not required.

User scripts

Shortcut

The majority of user scripts are intended to merely improve or personalize the existing MediaWiki interface, or to simplify access to commonly used functions for editors. Scripts of this kind do not normally require BAG approval.

See also

Sours: https://en.wikipedia.org/wiki/Wikipedia:Bot_policy
  1. Kaiba yugioh
  2. Rar brewing
  3. Just add water package norwex

Internet bot

For other uses, see Automated bot.

For bot operation on Wikipedia, see Wikipedia:Bots.

Software that runs automated tasks over the Internet

An Internet bot, web robot, robot or simply bot, is a software application that runs automated tasks (scripts) over the Internet.[1] Typically, bots perform tasks that are simple and repetitive much faster than a person could. The most extensive use of bots is for web crawling, in which an automated script fetches, analyzes and files information from web servers. More than half of all web traffic is generated by bots.[2]

Efforts by web servers to restrict bots vary. Some servers have a file that contains the rules governing bot behavior on that server. Any bot that does not follow the rules could, in theory, be denied access to or removed from, the affected website. If the posted text file has no associated program/software/app, then adhering to the rules is entirely voluntary. There would be no way to enforce the rules or to ensure that a bot's creator or implementer reads or acknowledges the robots.txt file. Some bots are "good" – e.g. search engine spiders – while others are used to launch malicious attacks on, for example, political campaigns.[2]

IM and IRC[edit]

Some bots communicate with users of Internet-based services, via instant messaging (IM), Internet Relay Chat (IRC), or other web interfaces such as Facebook bots and Twitter bots. These chatbots may allow people to ask questions in plain English and then formulate a response. Such bots can often handle reporting weather, zip code information, sports scores, currency or other unit conversions, etc.[citation needed] Others are used for entertainment, such as SmarterChild on AOL Instant Messenger and MSN Messenger.

Bots are very commonly used on social media. A user may not be aware that they are interacting with a bot.

Additional roles of an IRC bot may be to listen on a conversation channel, and to comment on certain phrases uttered by the participants (based on pattern matching). This is sometimes used as a help service for new users or to censor profanity.

Social bots[edit]

Main article: Social bot

Social networking bots are sets of algorithms that take on the duties of repetitive sets of instructions in order to establish a service or connection among social networking users. Among the various designs of networking bots, the most common are chat bots, algorithms designed to converse with a human user, and social bots, algorithms designed to mimic human behaviors to converse with patterns similar to those of a human user. The history of social botting can be traced back to Alan Turing in the 1950s and his vision of designing sets of instructional code approved by the Turing test. In the 1960s Joseph Weizenbaum created ELIZA, a natural language processing computer program. considered an early indicator of artificial intelligence algorithms. ELIZA inspired computer programmers to design tasked programs that can match behavior patterns to their sets of instruction. As a result, natural language processing has become an influencing factor to the development of artificial intelligence and social bots. And as information and thought see a progressive mass spreading on social media websites,[3] innovative technological advancements are made following the same pattern.

Reports of political interferences in recent elections, including the 2016 US and 2017 UK general elections,[4] have set the notion of bots being more prevalent because of the ethics that is challenged between the bot's design and the bot's designer. Emilio Ferrara, a computer scientist from the University of Southern California reporting on Communications of the ACM,[5] said the lack of resources available to implement fact-checking and information verification results in the large volumes of false reports and claims made about these bots on social media platforms. In the case of Twitter, most of these bots are programmed with search filter capabilities that target keywords and phrases favoring political agendas and then retweet them. While the attention of bots is programmed to spread unverified information throughout the social media platforms,[6] it is a challenge that programmers face in the wake of a hostile political climate. The Bot Effect is what Ferrera reported as the socialization of bots and human users creating a vulnerability to the leaking of personal information and polarizing influences outside the ethics of the bot's code, and was confirmed by Guillory Kramer in his study where he observed the behavior of emotionally volatile users and the impact the bots have on them, altering their perception of reality.

Commercial bots[edit]

There has been a great deal of controversy about the use of bots in an automated trading function. Auction website eBay took legal action in an attempt to suppress a third-party company from using bots to look for bargains on its site; this approach backfired on eBay and attracted the attention of further bots. The United Kingdom-based bet exchange, Betfair, saw such a large amount of traffic coming from bots that it launched a WebService API aimed at bot programmers, through which it can actively manage bot interactions.

Bot farms are known to be used in online app stores, like the Apple App Store and Google Play, to manipulate positions[7] or increase positive ratings/reviews.[8]

A rapidly growing, benign form of internet bot is the chatbot. From 2016, when Facebook Messenger allowed developers to place chatbots on their platform, there has been an exponential growth of their use on that app alone. 30,000 bots were created for Messenger in the first six months, rising to 100,000 by September 2017.[9] Avi Ben Ezra, CTO of SnatchBot, told Forbes that evidence from the use of their chatbot building platform pointed to a near future saving of millions of hours of human labor as 'live chat' on websites was replaced with bots.[10]

Companies use internet bots to increase online engagement and streamline communication. Companies often use bots to cut down on cost; instead of employing people to communicate with consumers, companies have developed new ways to be efficient. These chatbots are used to answer customers' questions: for example, Domino's developed a chatbot that can take orders via Facebook Messenger. Chatbots allow companies to allocate their employees' time to other tasks.[11]

Malicious bots[edit]

One example of the malicious use of bots is the coordination and operation of an automated attack on networked computers, such as a denial-of-service attack by a botnet. Internet bots or web bots can also be used to commit click fraud and more recently have appeared around MMORPG games as computer game bots. Another category is represented by spambots, internet bots that attempt to spam large amounts of content on the Internet, usually adding advertising links. More than 94.2% of websites have experienced a bot attack.[2]

There are malicious bots (and botnets) of the following types:

  1. Spambots that harvest email addresses from contact or guestbook pages
  2. Downloaded programs that suck bandwidth by downloading entire websites
  3. Website scrapers that grab the content of websites and re-use it without permission on automatically generated doorway pages
  4. Registration bots that sign up a specific email address to numerous services in order to have the confirmation messages flood the email inbox and distract from important messages indicating a security breach.[12]
  5. Viruses and worms
  6. DDoS attacks
  7. Botnets, zombie computers, etc.
  8. Spambots that try to redirect people onto a malicious website, sometimes found in comment sections or forums of various websites
  9. Viewbots create fake views[13][14]
  10. Bots that buy up higher-demand seats for concerts, particularly by ticket brokers who resell the tickets.[15] These bots run through the purchase process of entertainment event-ticketing sites and obtain better seats by pulling as many seats back as it can.
  11. Bots that are used in massively multiplayer online role-playing games to farm for resources that would otherwise take significant time or effort to obtain, which can be a concern for online in-game economies.[citation needed]
  12. Bots that increase views for YouTube videos
  13. Bots that increase traffic counts on analytics reporting to extract money from advertisers. A study by Comscore found that over half of ads shown across thousands of campaigns between May 2012 and February 2013 were not served to human users.[16]
  14. Bots used on internet forums to automatically post inflammatory or nonsensical posts to disrupt the forum and anger users.

in 2012, journalist Percy von Lipinski reported that he discovered millions of bots or botted or pinged views at CNNiReport. CNN iReport quietly removed millions of views from the account of iReporter Chris Morrow.[17] It is not known if the ad revenue received by CNN from the fake views was ever returned to the advertisers.

The most widely used anti-bot technique is the use of . Examples of providers include , Minteye, Solve Media and . circumvented

Human interaction with social bots[edit]

There are two main concerns with bots: clarity and face-to-face support. The cultural background of human beings affects the way they communicate with social bots. Many people believe that bots are vastly less intelligent than humans and so they are not worthy of our respect.[1]

Min-Sun Kim proposed five concerns or issues that may arise when communicating with a social robot, and they are avoiding the damage of peoples' feelings, minimizing impositions, disproval from others, clarity issues, and how effective their messages may come across.[1]

Social robots also take away from the genuine creations of human relationships.[1]

See also[edit]

References[edit]

  1. ^ abcdDunham, Ken; Melnick, Jim (2009). Malicious Bots: An outside look of the Internet. CRC Press. ISBN .
  2. ^ abcZeifman, Igal. "Bot Traffic Report 2016". Incapsula. Retrieved 1 February 2017.
  3. ^"Twitter Followers Guide". 20 November 2019
  4. ^Howard, Philip N (18 October 2018). "How Political Campaigns Weaponize Social Media Bots". IEEE Spectrum.
  5. ^Ferrara, Emilio; Varol, Onur; Davis, Clayton; Menczer, Filippo; Flammini, Alessandro (2016). "The Rise of Social Bots". Communications of the ACM. 59 (7): 96–104. arXiv:1407.5225. doi:10.1145/2818717. S2CID 1914124.
  6. ^Alessandro, Bessi; Emilio, Ferrara (2016-11-07). "Social Bots Distort the 2016 US Presidential Election Online Discussion". SSRN 2982233.
  7. ^"Touch Arcade Forum Discussion on fraud in the Top 25 Free Ranking".
  8. ^"App Store fake reviews: Here's how they encourage your favourite developers to cheat". Electricpig. Archived from the original on 2017-10-18. Retrieved 2014-06-11.
  9. ^"Facebook Messenger Hits 100,000 bots". 2017-04-18. Retrieved 2017-09-22.
  10. ^Murray Newlands. "These Chatbot Usage Metrics Will Change Your Customer Service Strategy". Retrieved 2018-03-08.
  11. ^"How companies are using chatbots for marketing: Use cases and inspiration - MarTech Today". MarTech Today. 2018-01-22. Retrieved 2018-04-10.
  12. ^Dima Bekerman: How Registration Bots Concealed the Hacking of My Amazon Account, Application Security, Industry Perspective, December 1st, 2016, In: www.Imperva.com/blog
  13. ^Carr, Sam (July 15, 2019). "What Is Viewbotting: How Twitch Are Taking On The Ad Fraudsters". PPC Protect. Retrieved 19 September 2020.
  14. ^Lewis, Richard (March 17, 2015). "Leading StarCraft streamer embroiled in viewbot controversy". Dot Esports. Retrieved 19 September 2020.
  15. ^Safruti, Ido (June 19, 2017). "Why Detecting Bot Attacks Is Becoming More Difficult". DARKReading.
  16. ^Holiday, Ryan (January 16, 2014). "Fake Traffic Means Real Paydays". BetaBeat. Archived from the original on 2015-01-03. Retrieved 2014-04-28.
  17. ^von Lipinski, Percy (28 May 2013). "CNN's iReport hit hard by pay-per-view scandal". PulsePoint. Archived from the original on 18 August 2016. Retrieved 21 July 2016.

External links[edit]

  • Media related to Bots at Wikimedia Commons
Sours: https://en.wikipedia.org/wiki/Internet_bot

Wikipedia:Bots

Automated programs on Wikipedia

"WP:B" redirects here. For other uses, see Wikipedia:Bureaucrats, Wikipedia:Blocking policy, Wikipedia:Wikipedia is not a bureaucracy, Wikipedia:Be bold, Wikipedia:Backlog, and Wikipedia:Content assessment/B-Class criteria.

"WP:BOT" redirects here. For other uses, see Wikipedia:Bot policy, WikiProject British Overseas Territories, and Wikipedia:Wikimedia Foundation § Board of Trustees.

Wikipedia information page

This page in a nutshell: On Wikipedia, bots are computer-controlled user accounts performing various tasks in order to maintain the encyclopedia. Bots are used for many purposes, for instance removing obvious vandalism and archiving talk pages. All bots must be approved by a special group before they are put into use.
A man is shaking hands with a bot

A bot (a common nickname for software robot) is an automated tool that carries out repetitive and mundane tasks to maintain the 54,476,399 pages of the English Wikipedia. Bots are able to make edits very rapidly, but can disrupt Wikipedia if they are incorrectly designed or operated. For these reasons, a bot policy has been developed.

There are currently 2,534 bot tasks approved for use on the English Wikipedia; however, not all approved tasks involve actively carrying out edits. Bots will leave messages on user talk pages if the action that the bot has carried out is of interest to that editor. Some bots can be excluded from leaving these messages by using the {{bots}} tags. There are 198 exclusion-compliant bots, which are listed in this category. There are 323 bots flagged with the "bot" flag right now (and over 400 former bots). There is also a range of tools that allow semi-automated editing of large numbers of articles.

History

Main page: Wikipedia:History of Wikipedia bots

Bots have been used in the past to create large numbers of articles that were uploaded to Wikipedia within a short timeframe. Some technical problems were experienced and this led to the formulation of a bot policy, as well as a restriction on the automated, large-scale, creation of articles.

Bot policy

Main page: Wikipedia:Bot policy

Wikipedia policy requires that bots be harmless and useful, have approval, use separate user accounts, and be operated responsibly.

Bot Approvals Group

Main page: Wikipedia:Bot Approvals Group

The Bot Approvals Group (BAG) supervises and approves all bot-related activity from a technical and quality-control perspective on behalf of the English Wikipedia community. On the English Wikipedia, the right to flag a bot is limited to bureaucrats.

Running an automated bot on a separate account requires approval, which may be requested at Wikipedia:Bots/Requests for approval.

How to create a bot

Main page: Help:Creating a bot

Some programming experience generally is needed to create a bot, and knowledge of regular expressions is useful for many editing tasks. However, some of the more user-friendly tools, such as AutoWikiBrowser or JavaScript Wiki Browser, can be used for some tasks.

The Chicken Scheme, Common Lisp, Haskell, Java, Microsoft .NET, Perl, PHP, Python, and Ruby programming languages all have libraries available for creating bots. Pywikibot is a commonly used Python package developed specifically for creating MediaWiki bots.

Dealing with bot issues

Main page: Wikipedia:Bot policy § Dealing with issues

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.

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.

How to hide a specific bot from your watchlist

Shortcuts

While it is easy to hide all bots from your watchlist, there is no way of hiding specific bots through user preferences or default watchlist settings. However, it is possible with a user script by following these simple steps.

Main steps

  1. Go to your Special:MyPage/common.js page (or your Special:MyPage/skin.js), and add the following line (diff):
  2. Remember to bypass your browser's cache.
  3. Go to your watchlist. There should be a box with several options. Tick the 'Enable hide user buttons' box. This will let you hide specific bots (and users) from your watchlist.
    Note: You might want to untick the 'Enable hide user buttons' box after you ignore a bot to ensure that you don't accidentally click 'hide user' when browsing your watchlist.

Optional steps

  1. If you find the 'Enable hide user buttons' box annoying, go to your Special:MyPage/common.css page (or Special:MyPage/skin.css) and add the following line (diff):
  2. Remember to bypass your browser's cache.
  3. If you want to show the box again, for example to reset your ignore list, go to your Special:MyPage/common.css page and remove the line you added in optional step #1 (remembering to again bypass your browser's cache). Redoing optional steps #1 and #2 will hide the box again.

While you are completely free to ignore any bots (or users) you want, it is a good idea to only ignore bots with well-defined tasks, which you trust to not make any mistakes.

How to hide AWB edits from your watchlist

Shortcut

There is no way of hiding AutoWikiBrowser (AWB) edits through user preferences or default watchlist settings. However, it is possible with a user script by following these steps:

Steps

  1. Go to your Special:MyPage/common.js page (or your Special:MyPage/skin.js), and add the following two lines (diff):
    importScript('User:Evad37/Watchlist-hideAWB.js');// Backlink: [[User:Evad37/Watchlist-hideAWB]]varawbHiddenByDefault=true;
  2. Bypass your browser's cache.

Any edit with "AWB" in its edit summary will now default to hidden for you. You may reveal them by clicking on the "show AWB" tab at the top of your watchlist (next to "Special page" for Monobook skin, or in the "More" dropdown for Vector skin).

Notes:

  • If you leave out , AWB edits will be shown by default, but you will have the option of hiding AWB edits by clicking on the "hide AWB" tab at the top of your watchlist.
  • While you are completely free to ignore AWB edits, remember that many of them will contain substantial changes from human editors, not just minor edits from bots or meatbots.
  • When hiding edits with a script, earlier edits can be forced to appear. Using the preference option is necessary to see other non-hidden watchlist hits for a page.

How to stop specific bots from editing the article

Main page: Template:Bots

It's rare that a mainspace article needs to not be edited by a specific bot. No article needs to stop all bots from editing, since antivandal bots such as ClueBot NG need to be able to edit all mainspace articles. The template {{bots}} can stop a bot from editing an article under the rare circumstance it's needed.

Examples

Some examples of bots are:

See also

Articles

Categories

Meta

Barnstar

Userbox and top icon

Sours: https://en.wikipedia.org/wiki/Wikipedia:Bots

Bot wikipedia

Meet the 'bots' that edit Wikipedia

By Daniel Nasaw
BBC News Magazine, Washington

Wikipedia is written and maintained by tens of thousands of volunteers across the world. Those, in turn, are assisted by hundreds of "bots" - autonomous computer programmes that keep the encyclopaedia running.

"Penis is the male sex organ," the Wikipedia page in question read.

While that statement is undeniably true and thus may merit inclusion in Wikipedia, it belongs nowhere in the site's article on national supreme courts and their legal roles.

When an anonymous Wikipedia reader in South Carolina offered that contribution to the globally popular online encyclopaedia last week, it took just seconds for the blemish to be discovered and deleted.

The vandalism was caught not by a reader, but by a simple artificial intelligence programme called a bot - short for robot.

ClueBot NG, as the bot is known, resides on a computer from which it sallies forth into the vast encyclopaedia to detect and clean up vandalism almost as soon as it occurs.

It is one of several hundred bots patrolling Wikipedia at any given time. Its role in repairing the Supreme Court article illustrates how bots have quietly become an indispensable - if virtually invisible - part of the Wikipedia project.

"Wikipedia would be a shambles without bots," a Wikipedia administrator known on the site as Hersfold writes in an email.

English Wikipedia alone surpassed four million articles this month. It contains an estimated 2.5 billion words, equivalent to millions of pages, and it is 50 times larger than the Encyclopaedia Britannica.

Wikipedia is maintained across all languages by tens of thousands of editors - about 77,000 of whom make more than five edits a month.

But the project is so vast, and its maintenance so labour-intensive that it defies the capability of its human administrators and editors to keep it in order.

That is where the bots come in.

"We had a joke that one day all the bots should go on strike just to make everyone appreciate how much work they do," says Chris Grant, a 19-year-old student in Perth, Australia who is on the Wikipedia committee that supervises the bots.

"The site would demand much more work from all of us and the editor burnout rate would be much higher."

The bots perform a wide range of editorial and administrative tasks that are tedious, repetitive and time-consuming but vital.

They delete vandalism and foul language, organise and catalogue entries, and handle the reams of behind-the-scenes work that keep the encyclopaedia running smoothly and efficiently and keep its appearance neat and uniform in style.

In brick-and-mortar library terms, bots are akin to the students who shelve books, move stacks from one range to another, affix bar codes to book spines and perform other grunt tasks that allow the trained librarians to concentrate on acquisitions and policy.

"Wikipedia has just grown so much that I don't know how well people would handle it if all the bots went away," says Brad Jorsch, a computer programmer in North Carolina who runs a bot that tracks the tags reminding editors to add citations to articles.

Bots have been around almost as long as Wikipedia itself.

The site was founded in 2001, and the next year, one called rambot created about 30,000 articles - at a rate of thousands per day - on individual towns in the US.

The bot pulled data directly out of US Census tables. The articles read as if they had been written by a robot. They were short and formulaic and contained little more than strings of demographic statistics.

But once they had been created, human editors took over and filled out the entries with historical details, local governance information, and tourist attractions.

In 2008, another bot created thousands of tiny articles about asteroids, pulling a few items of data for each one from an online Nasa database.

Today, the Wikipedia community remains divided on the value of bot-written entries. Some administrators say a stub of an article listing only a few points of data is of little value; others say any new content is good.

The upshot of the disagreement is bots are no longer permitted to write whole articles. But their ability to perform rote maintenance frees up human editors to do research and write entries and check one another's work to ensure accuracy.

"I don't think people realise how much maintenance and meta work goes on in Wikipedia," says Grant.

Some administrators fear a renegade bot will one day inflict catastrophic damage on the encyclopaedia. Think Skynet in the Terminator films.

Those fears are unfounded, says Grant.

For one, a bot is not like an automobile - if a part fails while in operation it will shut down rather than careen into something.

"You'd have to have someone actually have someone programme the bot to go crazy and delete everything," Grant says.

Bots with the rights to delete pages, block editors and take other drastic actions could only be run by editors already entrusted with administrative privileges, Grant says.

The bots do make mistakes, however, if they encounter a new circumstance their programming cannot account for. ClueBot NG, the anti-vandalism bot, has a small rate of false positives - edits it mistakes for vandalism, but which are in fact legitimate.

Since Wikipedia closely tracks edits, however, mistakes can be repaired almost as quickly as they happened, administrators say.

Human writers need not fear they will one day be replaced by bots, the bot masters say.

"It takes human judgement to write an article or proof an article or even clean up grammar and spelling," says Jorsch.

Sours: https://www.bbc.com/news/magazine-18892510

Lsjbot

Ambox current red Americas.svg

This article needs to be updated. The reason given is: Article contains contradictory statements apparently due to the lack of updating. Please help update this article to reflect recent events or newly available information.(October 2020)

Wikipedia article creation bot

Lsjbot is an automated Wikipedia article-creating program, or Wikipedia bot, developed by Sverker Johansson for the Swedish Wikipedia. The bot primarily focuses on articles about living organisms and geographical entities (such as rivers, dams, and mountains).

According to its description page on the Swedish Wikipedia, Lsjbot was active in the Swedish and Waray Wikipedias and is currently active in the Cebuano Wikipedia, and has created most Wikipedia articles in those languages[1] (between 80% and 99% of the total[2]).

During 2020, Lsjbot was only performing maintenance on the Cebuano Wikipedia, with no major article creation projects underway.[3]

History[edit]

Sverker Johansson, the developer of Lsjbot

The program is responsible for 2.7 million articles as of July 2014[update], two-thirds of which appear in the Cebuano language Wikipedia (the native language of Johansson's wife); the other third appear in the Swedish Wikipedia. The bot can produce up to 10,000 articles per day.[4]

On June 15, 2013, the Swedish Wikipedia hit one million articles, the eighth language on Wikipedia to reach that goal. The millionth article was created by Lsjbot – which at that point had created 454,000 articles, almost half of the entire article count of the Swedish Wikipedia.[5] Lsjbot was also responsible for helping the Swedish Wikipedia become the second edition of Wikipedia to reach 2 million articles, which subsequently became the second-largest edition of Wikipedia behind only its English counterpart.[citation needed]

In February 2020, Vice reported that Lsjbot was responsible for over 24 million of 29.5 million edits at Cebuano Wikipedia, now the world's second-largest Wikipedia, with bots comprising all but five of the site's top 35 editors and no human editors in the top 10. However, Lsjbot is no longer creating new articles at the Cebuano, Swedish, and Waray-Waray Wikipedias. Sverker Johansson explained that "opinions shifted" within the Swedish Wikipedia community and Waray-Waray editors were unable to form a consensus about the automatic creation of articles.[3]

On the Swedish Wikipedia, since early 2017, around 900,000 articles written by Lsjbot have been deleted, due to a lack of adequate documentation or because of other reasons.[citation needed] Apart from these already-deleted articles, as of 24 May 2021, a further number of approximately 400,000 articles await deletion.

Overall, starting in 2017, there was an initial pace of approximately 20,000 to 40,000 deletions of Lsjbot-made articles per year, but since July 2020 the pace of deletions has greatly accelerated. In just one year, from July 2020 to July 2021, Swedish Wikipedia fell from 3.72 million articles to 2.99 million articles. Furthermore, since July 2020, the deletion rate has occasionally exceeded 5,000 per day.

Media coverage[edit]

Its operation has generated some criticism, from those who suggest the stub articles lack meaningful content and a human touch.[6] The Sydney Morning Herald compared the bot to Phil Parker, allegedly the most published author in human history, who has published over 85,000 books, each of which is completed in less than an hour using computers.[7]Popular Science compared the bot to the announcement in July 2014 by the Associated Press that it planned to use bots to write articles.[4] Johansson countered attacks on his methods by noting that if the bot does not write articles, "otherwise they're mainly written by young, white, male nerds and reflect male interests."[8]

References[edit]

  1. ^The bot’s user page on the Swedish Wikipedia, translated to English using Google Translate.
  2. ^stats:EN/BotActivityMatrixCreates.htm
  3. ^ abWilson, Kyle (February 11, 2020). "The World's Second Largest Wikipedia Is Written Almost Entirely by One Bot". Retrieved February 8, 2021.
  4. ^ abMain, Douglas (14 July 2014). "This Bot Has Written More Wikipedia Articles Than Anybody". Popular Science. Retrieved 13 December 2020.
  5. ^Gulbrandsson, Lennart (17 June 2013). "Swedish Wikipedia surpasses 1 million articles with aid of article creation bot". Wikimedia Blog. Archived from the original on 24 February 2018. Retrieved 24 February 2018.
  6. ^Jervell, Ellen Emmerentze (13 July 2014). "For This Author, 10,000 Wikipedia Articles Is a Good Day's Work". Wall Street Journal. Archived from the original on 24 February 2018. Retrieved 24 February 2018.
  7. ^Bagshaw, Eryk (16 July 2014). "This is how Sverker Johansson wrote 8.5 per cent of everything published on Wikipedia". Sydney Morning Herald. Archived from the original on 24 February 2018. Retrieved 24 February 2018.
  8. ^"Swedish Wiki vet sets new content record". The Local. 18 July 2014. Archived from the original on 24 February 2018. Retrieved 24 February 2018.

External links[edit]

Wikimedia Commons has media related to Lsjbot.
Sours: https://en.wikipedia.org/wiki/Lsjbot

You will also be interested:

Wikipedia:AutoWikiBrowser

Semi-automated MediaWiki editor

Warning: You take full responsibility for any action you perform using AutoWikiBrowser. You must understand Wikipedia policies and use this tool within these policies, or risk losing access to the tool or even being blocked from editing.
  • Home
    Introduction and rules
  • User manual
    How to use AWB
  • Discussion
    Discuss AWB, report errors, and request features
  • User tasks
    Request or help with AWB-able tasks
  • Technical
    Technical documentation

AutoWikiBrowser is not an automatic bot—edits made using this software are the responsibility of the editor using it. Although AWB does have an automatic mode enabled for some bot accounts, it normally just assists a human.

Shortcuts


AutoWikiBrowser (AWB) is a semi-automated MediaWiki editor designed to make tedious or repetitive editing tasks quicker and easier. It is, essentially, a browser that follows a user-generated list of pages to modify, presenting changes to implement within each of those pages, then progressing to the next page in the list once the changes are confirmed or skipped by the user. When set to do so, it suggests some changes (typically formatting) that are generally meant to be incidental to the main change.

AWB is written for Windows operating system versions Vista and newer. It also functions reasonably well under Wine on Mac and some versions of Linux (though not Linux Mint), but is not officially supported.

At present, AWB can create a list of pages from single or multiple categories, "what links here", the wiki links on a page, a text file, a Google search, a user's watchlist, or a user's contributions. AWB also comes with an integrated program to scan Wikipedia database dumps. The edit box of AWB supports the Microsoft Text Services Framework for use with speech recognition/handwriting applications.

The sources are available under the GPLv2 (see Documentation page). It is written in C# using Microsoft Visual C# Express Edition/Visual Studio, which is freely available at Microsoft downloads.

There is an AWB IRC channel at #AutoWikiBrowserconnect.

Usergroup No. approved
Admins All (1,077)
Bots 96
Users 1,767

Rules of use

See also: Wikipedia:Bot policy § Bot-like editing

Shortcut

  1. You are responsible for every edit made. You are expected to review every edit, just as if you were making an edit using Wikipedia's edit form when editing by hand. Do not sacrifice quality for speed, and review all changes before saving.
  2. Abide by all Wikipedia guidelines, policies and common practices.
  3. Do not make controversial edits with it. Seek consensus for changes that could be controversial at the appropriate venue; village pump, WikiProject, etc. "Being bold" is not a justification for mass editing lacking demonstrable consensus. If challenged, the onus is on the AWB operator to demonstrate or achieve consensus for changes they wish to make on a large scale.
  4. Do not make insignificant or inconsequential edits. An edit that has no noticeable effect on the rendered page is generally considered an insignificant edit. If in doubt, or if other editors object to edits on the basis of this rule, seek consensus at an appropriate venue before making further similar edits.
Repeated abuse of these rules could result, without warning, in your software being disabled. If you wish to run a bot, see Wikipedia:Bots; bots must be approved by the bot approvals group.

Using this software

(1) Register

Request permission at Wikipedia:Requests for permissions/AutoWikiBrowser if you would like to use the software. Once your username is added to the list on the check page, you can then use AutoWikiBrowser on the English Wikipedia.

Anyone can be registered, but only if an admin approves your registration. As a general rule, only users with more than 250 non-automated mainspace editsor500 total mainspace edits will be registered. You will probably not be contacted when your registration has been approved, so look at the check page periodically for your name or watchlist the page. Admin accounts are automatically approved for using the software, even without being registered. Admins with pseudo-bot or flooder (not available on the English Wikipedia) will still need to add themselves into the bots section of the CheckPage to be able to use the Bots tab.

If you are planning to use only the "Make list" or "List comparer" options, then there is no need to register. These parts of the software do not prompt for a username or check the account permissions.

(2) Download

Download the release version . Please ensure that you click on the correct download button on the Sourceforge page, as there may be more than one. The correct button is green and inside the box containing the description, just above the screenshots.

If you want to run the latest SVN version, see Wikipedia:AutoWikiBrowser/Sources.

Running on Windows

AutoWikiBrowser requires Windows Vista or newer to edit on Wikimedia wikis. AutoWikiBrowser does not work on Windows XP as XP does not meet Wikimedia's security standards. On other wikis, AutoWikiBrowser may work with Windows XP, although the tool is likely no longer maintained.

AWB comes in a zip file, and it is recommended that it be unzipped to a new directory, rather than running, for example, straight from the desktop. AWB is not installed on the PC and runs mostly as a standalone application: AutoWikiBrowser.exe (the provided WikiFunctions.dll file is also required). AWB can be unzipped to any directory; however, on some machines there can be permissions problems that stop AWB working correctly if the directory used is on a network drive. If you're unsure, unzip AWB to somewhere on the machine's C: drive, for example, within 'Downloads'.

Running on Linux or Mac

Main page: Wikipedia:AutoWikiBrowser/Mono and Wine

On Linux, AWB mostly works with Wine with .NET 4.5 installed and is suitable for use for regular editing. The installation process is the same as Wikipedia:Huggle/Wine.

AWB can also be started on Mono, albeit with some strange errors, and the web browser component does not yet work under Mono. AWB under Mono is not yet suitable for use for regular editing.

On macOS, AWB is not natively available, but one option is to use virtualisation with Parallels Desktop for Mac (subject to meeting supported operating systems requirements) and then run Microsoft Windows virtually with AWB as the Windows instructions above. A paid license is required for both Parallels Desktop for Mac and Microsoft Windows. Another option is to use Boot Camp to install Windows, although it is not supported on Apple Silicon Macs. An alternative is to use the free VirtualBox, although a paid license for Microsoft Windows is still required. AWB can also be used under Wine on a Mac. WineHQ has a page on Wine under MacOS X. A package manager such as Homebrew can be used to install Wine; see Wine on a Mac using homebrew.

Alternatively, JavaScript Wiki Browser may be used on any major operating system.

(3) Get started

A default screen arrangement for standard AWB editing
A dual-monitor screen arrangement for more complex AWB diffs

See also: Wikipedia:AutoWikiBrowser/User manual

  1. Select "Make from Category", then enter a category name.
  2. Click "Make list", then let the list load up.
  3. Set any options, such as find and replace, edit summary, etc.
  4. Click "Start!", it will load up the page, automatically make any changes, and then go to the diff.
  5. Change anything in the page you want in the Edit box on the lower right, not the normal website textbox in the browser, then click "Save" or "Skip / Ignore", the next page will load up automatically.

Refer to the FAQ for more information, including problems with other software and Wikipedia skins.

Features

AutoWikiBrowser's main feature is to easily make the same type of edit to a large number of pages. For example, fixing a typo, adding a navbox, or adding a category to dozens or hundreds of pages.

  • Create a list of pages, files, categories to run edits on. Criteria for list building include:
    • CheckWiki errors
    • items in category
    • Google search results
    • links or categories on target page
    • links or a simple list of titles in a text file
    • watchlist contents
    • special page results
    • pages that link, transclude or redirect to target
    • Wikipedia search results
  • Search and replace wikitext – plain text or regular expressions
  • Add material to the beginning or end of each page
  • Add, remove, or replace categories and files
  • Rules-based page skipping
  • Custom user scripts

AutoWikiBrowser also has some other features.

Database scanner

See also: Wikipedia:AutoWikiBrowser/Database Scanner

AWB includes a database scanner that can be used to create lists of pages to be checked, without causing extra unnecessary load on Wikimedia servers.

Database dumps are created from time to time (more info here) and are available for free download. As the page states, the best/most useful dump is the enwiki-latest-pages-articles.xml.bz2 (dir). Visiting the database dump progress site allows you to view the status of the current dump and easily browse to the downloads in it.

After downloading, the archive needs to be uncompressed; this will turn it from a ~18 GB bz2 archive into an XML database dump around 79 GB.

A scannable .xml file of selected files can also be generated by visiting Special:Export.

Plugins

Main page: Wikipedia:AutoWikiBrowser/Plugins

AWB can load and use fully customized plugins. These plugins can process page text and extend the user interface, and are in the form of libraries (.dll files) which can be made in any .NET language such as C# or Visual Basic .NET. When AWB loads, it automatically checks to see if there are any plugins in the folder from which it was executed. Any plugins found are loaded and initialized without further intervention by the user.

AWB ships with WikiFunctions.dll, which can be referenced by other standalone projects. The DLL includes a wiki-ready web browser control, a simple page editor, a listmaker, and other tools and components.

See also

  • Javascript Wiki Browser – A user script with similar functionality to the downloadable AutoWikiBrowser, but loaded within the web browser
  • AutoEd – A user script that helps to automatically make certain changes in articles
  • autoFormatter – A user script that semi-automatically fixes more than 200 common errors in wiki markup
  • WPCleaner – A tool designed to help with various maintenance tasks, especially repairing links to disambiguation pages, checking Wikipedia, fixing spelling and typography
  • Wikiget – A Unix command-line tool to generate a list of articles from categories, templates, backlinks, etc.
  • WP:HIDEAWB – Instructions on how to hide AWB edits from your watchlist.
  • – Userbox to show AutoWikiBrowser userright
  • {{AWB topicon}} – a top icon template to indicate you have the AutoWikiBrowser user right – adds a category to page automatically

External links

Sours: https://en.wikipedia.org/wiki/Wikipedia:AutoWikiBrowser


454 455 456 457 458