Knowledge

:Bots/Requests for approval/Cydebot 2 - Knowledge

Source 📝

214:
and keeping it in a history page on-wiki, it is easily accessible and understandable by all regular Wikipedians. The lists will prove useful to, among other things, identify pages which have been removed from proposed deletion categories without actually being deleted, allow an easy way to analyze the churn rate of maintenance categories, provide a semi-static list view of these categories which some editors prefer to use, and allows long-term auditing of requests for unblock that doesn't require database access to view all old contributions to parse for
488: 243: 44: 213:
The purpose of this is to keep track of the members of these categories over time. This is a useful analytical tool, as the way categories are implemented on-wiki, they only display what is in the category at the exact moment, not what was in it, say, minutes or hours ago. By doing this all on-wiki
418:
page-gets as far as server impact is concerned? I'd assume these have more implications for db queries than the same number of article (etc) page fetches due to different caching, but I'm entirely hazy on the details of how that's implemented. Anyhoo, that's just a matter of tuning, as Cyde says.
393:
Well, the list of what has been added and removed is already in the diffs between revisions, so it isn't really that necessary to also display it explicitly within each revision. I was, however, thinking of breaking out the number of entries per diff, which doesn't really tell the whole story. For
303:
actually be deleted. As such, they'll open the article, review it, and then they might as well click the "delete" tab. I may have missed something, but it would seem that the "delete" button in the list would be redundant and possibly even foster non-sighted deletion, which is a Very Bad Thing. Just
381:
Excellent, I've been waiting for that. I find these useful to use, but if someone is going to use this for analysis wouldn't it make sense to divide the list into 3 sections (new items added since the last update, items carried over from last update, and items removed since last update (which would
335:
I don't particularly see the value of delete links, although I will look into putting the current number of items in the list into the edit summary. That's something that can easily be done, and should add some value. Unfortunately, because Cydebot is a bot, his edits won't by default show up in
471:
I know zilch about same, but I should have inferred as much from the structure of the job queue handling of large category changes. Fair enough then, aforementioned 'tuning' on the basis of the write-rate seems perfectly sufficient. I'll note that the "not a problem by analogy" argument isn't
428:
Getting a category page takes just as much server "effort" (as it were) as getting an article page. What requires a little bit of extra effort with categories is updating them when the text of another page changes to add or remove the category from it. But the category page itself is entirely
398:
while ten are deleted, yet someone just tracking the # of entries in the edit summaries would see it as going down by one, and wouldn't think to view the diff to see that some new stuff has actually been added. Thus I'm looking into putting numbers into the edit summary like (100 current, 10
350:
There are situtions where CSD gets loaded with pages that you can delete simply on title alone, but it is rare enough that it would more likely cause the bad practice mentioned above for those not familiar enough with the situation. (Discussion withdrawn) —
231:
be changed as necessary. I haven't yet figured out the final values I want to settle with, as I've only just started experimenting with the trade-off between keeping the lists up to date and the resources used in committing an edit.
187:
A test run has already been completed without malfunction or incident. Basically, the bot automatically updates the following four pages at given intervals (each page is a listification of a category):
472:
entirely sound, since replication of numerous reasonable loads isn't necessarily itself reasonable. (More of a problem if there were umpteen AVBs, though, rather than in this case.)
382:
be red links in the case of the deletion lists)). I guess it depends on how you intend to use the output (other than as an alternate way to see what's in the category).
367:
I have modified the edit summary in pyWikipediaBot to include the number of entries in the listified category. This addresses the suggestion that was made above. --
452:
From what I know of the Mediawiki software, I think Cyde is right about category pages being cached, and having a server load on par with loading a cached article.
310: 256: 327: 294: 533: 476: 458: 361: 429:
cached. Once every five minutes is going to have a completely negligible effect on the servers. Hell, look at AntiVandalBot: it compares the diffs of
441: 423: 407: 197: 264: 284:
Looks like they are replacing, in that case care to add some functionality to them , perhaps (delete) links next to the CSD's or old prods? —
250: 207: 279: 505: 336:
watchlists, so someone has to specifically choose to view bot edits before this edit summary stuff will really be all that useful. --
375: 344: 202: 69: 192: 317:
Unless you have a tabbed browser in which case you might open the article and the delete page at the same time. I do that on
21: 227:
As the bot is set up right now, it edits the pages at intervals of 20, 5, 20, and 10 minutes, respectively. This can
84: 414:
Sounds good to me. The intervals sound quite short though: can anyone comment on the implications of frequent
79: 383: 299:
Admins are expected to check the articles before deleting, even if they are expired prods, to make sure it
114: 321:
all the time, if the user does not need to be blocked I close the page, if he does the page is ready.
99: 109: 89: 104: 235: 8: 269:
Will these pages reflect the current entries as of point in time, or be ever apending? —
94: 306: 304:
my thoughts, and if I've gone off on a totally wrong tangent, please tell me. Cheers,
500: 74: 247: 218: 54: 17: 527: 453: 352: 322: 318: 285: 270: 149:
Automatically listifies certain maintenance categories at regular intervals.
496: 55: 433:
edit made to Knowledge, live, and it's not really a problem either. --
242: 473: 434: 420: 400: 368: 337: 125: 43: 395: 512:
The above discussion is preserved as an archive of the debate.
255:
The lists look exceptional (particularly the PROD ones) --
246:
Bot trial run approved for the duration of one week.
518:
Subsequent comments should be made in a new section.
39:
Subsequent comments should be made in a new section.
525: 198:User:Cyde/List of candidates for speedy deletion 137:Automatic, runs every xx minutes as a cron job. 33:The following discussion is an archived debate. 394:instance, nine new entries could be added to 167:See below for full description, this varies. 534:Approved Knowledge bot requests for approval 208:User:Cyde/List of current proposed deletions 203:User:Cyde/List of old proposed deletions 14: 526: 193:User:Cyde/List of requests for unblock 156:(e.g. Continuous, daily, one time run) 399:removed, 9 added) or some such. -- 27: 28: 545: 41:The result of the discussion was 486: 241: 42: 135:Automatic or Manually Assisted: 13: 1: 390:18:03, 25 January 2007 (UTC) 506:19:51, 7 February 2007 (UTC) 477:07:31, 31 January 2007 (UTC) 459:17:05, 28 January 2007 (UTC) 442:16:59, 28 January 2007 (UTC) 424:23:57, 26 January 2007 (UTC) 408:21:30, 25 January 2007 (UTC) 376:17:40, 25 January 2007 (UTC) 362:03:27, 25 January 2007 (UTC) 345:05:10, 24 January 2007 (UTC) 328:22:05, 23 January 2007 (UTC) 311:06:54, 23 January 2007 (UTC) 295:05:27, 22 January 2007 (UTC) 280:15:13, 21 January 2007 (UTC) 265:12:38, 19 January 2007 (UTC) 251:03:47, 19 January 2007 (UTC) 7: 143:pyWikipediaBot and crontab 10: 550: 515:Please do not modify it. 141:Programming Language(s): 36:Please do not modify it. 171:Already has a bot flag 22:Requests for approval 165:Edit rate requested: 457: 326: 262: 183:Function Details: 147:Function Summary: 541: 517: 504: 490: 489: 456: 439: 405: 388: 373: 358: 342: 325: 291: 276: 260: 245: 223: 217: 130: 46: 38: 549: 548: 544: 543: 542: 540: 539: 538: 524: 523: 522: 513: 495: 487: 435: 401: 384: 369: 357: 354: 338: 290: 287: 275: 272: 238: 221: 215: 126: 120: 59: 34: 26: 25: 24: 12: 11: 5: 547: 537: 536: 521: 520: 484: 483: 482: 481: 480: 479: 464: 463: 462: 461: 447: 446: 445: 444: 412: 411: 410: 365: 364: 355: 333: 332: 331: 330: 315: 314: 313: 288: 273: 267: 253: 237: 234: 211: 210: 205: 200: 195: 153:Edit period(s) 119: 118: 112: 107: 102: 97: 92: 87: 82: 77: 72: 70:Approved BRFAs 67: 60: 58: 53: 52: 51: 29: 18:Knowledge:Bots 15: 9: 6: 4: 3: 2: 546: 535: 532: 531: 529: 519: 516: 510: 509: 508: 507: 502: 498: 493: 478: 475: 470: 469: 468: 467: 466: 465: 460: 455: 451: 450: 449: 448: 443: 440: 438: 432: 427: 426: 425: 422: 417: 413: 409: 406: 404: 397: 392: 391: 389: 387: 380: 379: 378: 377: 374: 372: 363: 360: 359: 349: 348: 347: 346: 343: 341: 329: 324: 320: 319:Knowledge:AIV 316: 312: 309: 308: 307:Daniel.Bryant 302: 298: 297: 296: 293: 292: 283: 282: 281: 278: 277: 268: 266: 263: 259: 254: 252: 249: 244: 240: 239: 233: 230: 225: 220: 209: 206: 204: 201: 199: 196: 194: 191: 190: 189: 185: 184: 180: 178: 175: 172: 168: 166: 162: 160: 157: 154: 150: 148: 144: 142: 138: 136: 132: 131: 129: 124: 116: 113: 111: 108: 106: 103: 101: 98: 96: 93: 91: 88: 86: 83: 81: 78: 76: 73: 71: 68: 66: 62: 61: 57: 49: 45: 40: 37: 31: 30: 23: 19: 514: 511: 491: 485: 436: 430: 415: 402: 385: 370: 366: 353: 339: 334: 305: 300: 286: 271: 257: 228: 226: 212: 186: 182: 181: 176: 173: 170: 169: 164: 163: 158: 155: 152: 151: 146: 145: 140: 139: 134: 133: 127: 122: 121: 64: 47: 35: 32: 386:NoSeptember 248:Betacommand 161:Continuous 236:Discussion 110:rights log 100:page moves 492:Approved. 437:Cyde Weys 403:Cyde Weys 371:Cyde Weys 340:Cyde Weys 128:Cyde Weys 123:Operator: 105:block log 528:Category 454:HighInBC 416:category 356:xaosflux 323:HighInBC 289:xaosflux 274:xaosflux 80:contribs 48:Approved 20:‎ | 497:Mets501 396:CAT:CSD 219:unblock 56:Cydebot 301:should 229:easily 431:every 258:Samir 174:(Y/N) 85:count 16:< 501:talk 474:Alai 421:Alai 261:धर्म 179:Yes 115:flag 95:logs 75:talk 65:BRFA 90:SUL 530:: 224:. 222:}} 216:{{ 503:) 499:( 494:— 177:: 159:: 117:) 63:( 50:.

Index

Knowledge:Bots
Requests for approval

Cydebot
BRFA
Approved BRFAs
talk
contribs
count
SUL
logs
page moves
block log
rights log
flag
Cyde Weys
User:Cyde/List of requests for unblock
User:Cyde/List of candidates for speedy deletion
User:Cyde/List of old proposed deletions
User:Cyde/List of current proposed deletions
unblock

Betacommand
03:47, 19 January 2007 (UTC)
Samir धर्म
12:38, 19 January 2007 (UTC)
xaosflux
15:13, 21 January 2007 (UTC)
xaosflux
05:27, 22 January 2007 (UTC)

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.