24:
102:
180:, an off-wiki bot that tracks all link additions (in content areas of Knowledge) across the whole of WikiMedia (~830 wikis). LiWa3 will detect links that are only added by IPs, only added by one single user, that are redirect sites, or which have been reported to one of the spam-related noticeboards, and report them to COIBot.
625:
540:
Care should be taken when interpreting the data that is provided by COIBot. The bot has a mechanism which matches username against domain added or page edited, reporting significant overlap (its standard setting is to report all cases with more than 25% overlap). At the current state it can be seen
270:
Items on the whitelist make COIBot ignore the complete edit, so when the link 'example' <-> 'example.com' would be on the whitelist, COIBot would not report when user 'example' would add 'example.com' to a page (which would normally result in an overlap of 70%, well above the threshold). Users
352:
COIBot records additions of URLs on the monitorlist, except when the user is whitelisted or when a user is already reported via the blacklist or via overlap between username and domain-name. This functionality is used to find IP-ranges or sock-puppet accounts that add certain domains, but where the
477:
If the third number or the fourth number are high with respect to the first or the second, then that means that the user has at least a preference for using that link. Be careful with other statistics from these numbers (e.g. good user who adds a lot of links). If there are more statistics that
313:
Coibot has a table where usernames are linked to keywords. This gives the possibility to check whether certain accounts e.g. add a certain url (when a suspected or known conflict of interest exists). For example the blacklist rule 'COIBot' <-> 'example' would result in the following two
658:
101:
115:
80:
353:
full scope of the involved accounts is not (yet) clear. This function may result in numerous 'false positives' for domains which are, besides being spammed or pushed by certain accounts, also used as e.g. references.
271:
can also be whitelisted completely, which will result in them never being reported. Complete whitelisting of links will still result in them being reported, but such links will never be automonitored (see
124:
608:(though the overlap is now only the basic IRC-read and mediawiki-edit mechanism). It uses perlwikipedia, a module to read/write MediaWiki pages. A recent example of the code can be found on
356:
Addition of a link that has a large overlap with the username of the user that is adding the link will result in the link being added to the monitorlist automatically. COIBot also monitors
344:
The reverse is also checked, so 'example.com' can be linked to the keyword 'COI' or to IP-ranges, which makes it possible to find sock-puppets or check for additions by certain IP ranges.
291:
If you believe your name is wrongly on a report, please a) remove yourself from the reports (preferably using <s> and </s>-tags, providing a clear edit summary, and notify
592:
Therefore, all results should be, and will be, manually checked against the policies and guidelines. When wrong reports occur too often, these combinations can be whitelisted.
169:
user-IP (in case of IP users) in close range proximity of IP of domain (external link) a user is adding (IP of the domain as reported at time of addition by a DNS server).
153:
478:
would be useful, please notify me, and I will have a look if I can get the info out of the database and report it. This data is available in real-time on IRC.
547:
1. Editors with short usernames editing articles with short names easily exceed the 25% threshold since single characters have a high weight in short names:
571:
129:
541:
from the reports that more than 95% of the reported cases are 'correct' in terms of 'username indeed has a huge overlap with the pagename/url'.
705:
71:
229:#wikimedia-swmt-spam - all non-en.wikipedia specific coi and link addition reports (reads the non-English link addition feed from here).
553:
286:
wiki, another user on another wiki may have a conflict of interest. It may therefore be undesirable to whitelist certain usernames.
173:
Moreover, COIBot will track edits which it has been instructed to follow (e.g. certain username patterns or external link patterns).
436:
The lower list in the COIBot reports now have after each link four numbers between brackets (e.g. "www.example.com (0, 0, 0, 0)"):
183:
COIBot has access to the database of link additions created by LiWa3, and can save reports on data retrieved from that database:
424:
418:
412:
391:
390:). More information (monitoring or blacklisting reasons) can be found in the header of the specific reports on that link (see
300:
403:
386:
were spamming, but that there may (have) be(en) issues with that particular link or that there is an accidental overlap (see
255:
532:(the latter for privileged editors) COIBot will generate linkreports for the domains, and userreports for users and IPs.
204:
report all edits where COIBot perceived significant connection between username / user-IP and page edited / domain added.
201:
all link additions that have been performed by a certain user/IP (e.g. collect all domains spammed by a certain spammer);
575:
55:
59:
296:
695:
672:
Is presented to COIBot for automatically creating comprehensive spam reports which help users deal with spam.--
141:
23:
334:
323:
140:
is a bot that tries to track edits that are made by users who may have a conflict of interest ('COI', see
700:
223:#wikipedia-en-spam - all coi and link addition reports (reads the English link-addition feed from here)
262:. Specific user and link-reports are saved on both wikipedia, and contain in both cases all reports.
259:
557:
31:
584:
Of course a
ChocolateFan does not have a conflict of interest when adding important information to
108:
246:
COIBot here watches for page edits. Channels can be added or removed while COIBot is running.
193:
on domains hosted on one server-IP (server-IP as reported by a DNS server at time of addition).
609:
565:
2. An overlap does not necessarily mean that the editor has a conflict of interest. Example:
677:
585:
517:
357:
159:
COIBot tries to associate a users' username (or IP) with the material that they are editing:
67:
500:
490:
63:
8:
525:
521:
510:
372:
361:
46:
368:
for reported links, as well as the spam blacklists on the wikipedia it is monitoring.
341:
The second case has a ratio higher than the threshold, and COIBot would be reported.
578:
scores 75% (U->T) and 47.36% (T-U) (ratio 35.52%) on string chocolate_chip_cookie
303:) are generated automatically by COIBot, and may be regenerated before whitelisting.
282:
monitored wikis, which also means that while you have not a conflict of interest on
673:
605:
529:
216:
378:
When your name appears on the reports for a monitored link, then it does not mean
145:
123:
365:
278:
Please understand that whitelisting means that your username is whitelisted on
149:
35:
451:
link get added to wikipedia (for as far as the linkwatcher database goes back)
177:
689:
640:
407:
292:
62:
edits that would be extremely tedious to do manually, in accordance with the
42:
624:
79:
Administrators: if this bot is malfunctioning or causing harm, please
644:
337:
scores 100% (U->T) and 70% (T-U) (ratio 70%) on string example.com
232:#wikipedia-spam-t - main command channel, certain en-specific reports
215:
COIBot is at the moment listening and reporting to the IRC channels (
66:. The bot is approved and currently active – the relevant
299:
to request whitelisting. Please note that the link-reports (under
326:
scores 0% (U->T) and 0% (T-U) (ratio 0%) on string example.com
240:
314:
results when user COIBot would add the link 'www.example.com':
560:
scores 90% (U->T) and 60% (T-U) (ratio 54%) on string zyxwv
235:#wikipedia-spam-stats - used for some statistics and commands
657:
163:
Username similar to the name of the page the user is editing
154:
Knowledge:Best practices for editors with close associations
601:
415:- reports on suspected links (also automatically updated).
166:
Username similar to the external links a user is adding
639:This Barnstar is awarded to COIBot for identifying
465:fourth number, to how many different wikipedia did
371:All items on the monitor list are interpreted as a
198:Reports on all edits of a certain user/IP-editor:
254:All edits pertaining this wikipedia are reported
687:
130:Knowledge:Administrators' noticeboard/Incidents
113:Use this button if the bot is malfunctioning. (
249:
226:#wikimedia-swmt - all non-english reports.
655:
176:COIBot also works closely together with
394:for a list of generated link reports).
243:COIBot listens standard to ~830 wikis.
688:
622:
444:user add (is the same after each link)
425:Knowledge:WikiProject Spam/PageReports
419:Knowledge:WikiProject Spam/UserReports
413:Knowledge:WikiProject Spam/LinkReports
392:Knowledge:WikiProject Spam/LinkReports
301:Knowledge:WikiProject Spam/LinkReports
260:COIBot's account on meta.wikipedia.org
576:en:Special:Contributions/chocolatefan
404:Knowledge:WikiProject Spam/COIReports
382:have a conflict of interest, or that
187:Reports all external link additions:
16:Knowledge editing bot run by Beetstra
18:
706:Knowledge bots using MediaWiki::Bot
13:
604:, originally based on the code of
447:second number, how many times did
406:- reports on suspected cases of a
210:
14:
717:
535:
454:third number, how many times did
440:first number, how many links did
272:
656:
623:
100:
22:
347:
335:en:Special:Contributions/COIBot
324:en:Special:Contributions/COIBot
297:Knowledge talk:WikiProject Spam
387:
258:, everything gets reported to
142:Knowledge:Conflict of interest
54:It is used to make repetitive
1:
680:) 19:52, 18 March 2008 (UTC)
427:- reports on suspected pages.
421:- reports on suspected users.
615:
558:en:Special:Contributions/zxv
308:
265:
96:Emergency bot shutoff button
7:
595:
250:What is reported, and where
10:
722:
647:12:26, 28 July 2007 (UTC)
544:Some points of attention:
397:
662:
629:
481:
128:a malfunctioning bot to
633:The Technology Barnstar
122:Non-administrators can
600:The bot is written in
586:chocolate chip cookies
581:
563:
432:numbers in the reports
696:Active Knowledge bots
666:The Spamstar of Glory
641:conflicts of interest
570:<COIBot> TEST:
567:
552:<COIBot> TEST:
549:
610:m:User:COIBot/COIBot
572:en:User:chocolatefan
408:Conflict of Interest
241:IRC on wikimedia.org
190:on a certain domain;
68:request for approval
701:All Knowledge bots
643:on Knowledge! ----
373:regular expression
305:
217:IRC on libera.chat
118:
112:
97:
684:
683:
651:
650:
289:
133:
114:
107:
95:
92:
91:
86:
713:
660:
653:
652:
627:
620:
619:
530:User:COIBot/Poke
515:
509:
505:
499:
495:
489:
295:or a regular on
127:
121:
104:
85:
76:
53:
40:
26:
19:
721:
720:
716:
715:
714:
712:
711:
710:
686:
685:
618:
598:
538:
513:
507:
503:
497:
493:
487:
484:
400:
350:
311:
306:
288:
268:
252:
213:
211:What is watched
135:
120:
77:
75:
51:
38:
17:
12:
11:
5:
719:
709:
708:
703:
698:
682:
681:
669:
668:
663:
661:
649:
648:
636:
635:
630:
628:
617:
614:
597:
594:
590:
589:
580:
579:
562:
561:
537:
536:Interpretation
534:
483:
480:
475:
474:
463:
452:
445:
434:
433:
429:
428:
422:
416:
410:
399:
396:
349:
346:
339:
338:
331:en:User:COIBot
327:
320:en:User:COIBot
310:
307:
267:
264:
251:
248:
237:
236:
233:
230:
227:
224:
212:
209:
208:
207:
206:
205:
202:
196:
195:
194:
191:
171:
170:
167:
164:
150:Knowledge:Spam
146:m:Terms of use
109:Administrators
93:
90:
89:
87:
60:semi-automated
27:
15:
9:
6:
4:
3:
2:
718:
707:
704:
702:
699:
697:
694:
693:
691:
679:
675:
671:
670:
667:
664:
659:
654:
646:
642:
638:
637:
634:
631:
626:
621:
613:
611:
607:
603:
593:
587:
583:
582:
577:
573:
569:
568:
566:
559:
555:
551:
550:
548:
545:
542:
533:
531:
527:
523:
519:
516:templates to
512:
502:
492:
479:
472:
468:
464:
461:
457:
453:
450:
446:
443:
439:
438:
437:
431:
430:
426:
423:
420:
417:
414:
411:
409:
405:
402:
401:
395:
393:
389:
385:
381:
376:
374:
369:
367:
363:
359:
354:
345:
342:
336:
332:
328:
325:
321:
317:
316:
315:
304:
302:
298:
294:
293:Dirk Beetstra
287:
285:
281:
276:
274:
263:
261:
257:
247:
244:
242:
234:
231:
228:
225:
222:
221:
220:
218:
203:
200:
199:
197:
192:
189:
188:
186:
185:
184:
181:
179:
174:
168:
165:
162:
161:
160:
157:
155:
151:
147:
143:
139:
134:
131:
126:
117:
110:
105:
103:
98:
88:
84:
82:
73:
69:
65:
61:
57:
50:
48:
44:
37:
33:
28:
25:
21:
20:
665:
632:
599:
591:
564:
546:
543:
539:
514:}}
508:{{
504:}}
498:{{
494:}}
488:{{
486:When adding
485:
476:
470:
466:
459:
455:
448:
441:
435:
383:
379:
377:
370:
355:
351:
348:Monitor list
343:
340:
330:
319:
312:
290:
283:
279:
277:
273:monitor list
269:
253:
245:
238:
214:
182:
175:
172:
158:
137:
136:
106:
99:
94:
78:
70:can be seen
41:operated by
32:user account
29:
674:Otterathome
606:AntiSpamBot
554:en:User:zxv
501:UserSummary
491:LinkSummary
116:direct link
690:Categories
388:#Whitelist
275:, below).
64:bot policy
616:Barnstars
518:WT:WPSPAM
511:IPSummary
469:user add
458:user add
358:WT:WPSPAM
309:Blacklist
266:Whitelist
56:automated
596:Software
81:block it
43:Beetstra
506:and/or
398:Reports
366:WP:COIN
526:WT:SWL
522:WT:SBL
482:Poking
362:WT:SBL
329:TEST:
318:TEST:
138:COIBot
125:report
52:
39:
473:link.
178:LiWa3
34:is a
30:This
678:talk
645:Hu12
602:Perl
528:and
471:this
467:this
462:link
460:this
456:this
449:this
442:this
364:and
284:this
256:here
152:and
72:here
47:talk
384:you
380:you
280:all
239:On
219:):
156:).
58:or
36:bot
692::
612:.
524:,
520:,
496:,
375:.
360:,
148:,
144:,
119:)
74:.
49:).
676:(
588:.
574:/
556:/
333:/
322:/
132:.
111::
83:.
45:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
