Править фильтр злоупотреблений

Параметры фильтра

ID фильтра:	14
Описание: (общедоступное)
Срабатываний фильтра:	2 срабатывания
Условия:	!"confirmed" in user_groups & (article_namespace == 0 \| article_namespace == 3) & (match := "ABUSER\|\bA+SS+[- ]?H+O+L+E+\b\|BITCH\|\b(C+O+C+\|K+A+W+)K+S\b\|LOO+S+E+R+\|SOOO\|CONVICTED\|[KC]UNT\|DILDO\|D+O+U+C+H+E+\|EFF+ (Y+O+U+\|U+)\|F+U+(KK+\|C+K\|K+C)\|GARBAGE\|HAGGER\|HITLER\|JEWS\|MENTALLY SICK\|M(WA\|U)HAHA\|N+I+GG+(E+R+\|A+H)\|N[A4]ZI\|PEDOPHILE\|FAGG\|PEA?N[UI1][S5]\|S+L+U+T+\|POOO+P?\|W+H+O+R+E+\|PERVERT\|RACIST\|S+H+[1I]+T+\|SOCK[ \-]?PUPPET\|SUCK\|VAGINA\|VIAGRA\|WANK(A\|ER\|ING)\|(W\|WANKA)KNIGHT") & ((summary rlike match) \| ((added_lines rlike match) & !(removed_lines rlike match) & !(article_text rlike match)))
Примечания:	Creating per RFPP. - KoH Not working ... - KoH Re-enabling, disallow off. - KoH Too many false positives from added_lines in removed_lines. - KoH Could it be changed to prevent the creation of "Aaron Blakk"? - \ / First, why did you undo my last edit here? Second, why would you want to prevent the creation of user names that HELP us detect him? The user names themselves are not offensive, the edits are. - Wknight94 It was my first edit to the AF, must've inadvertantly done it - sorry. I see your point in re to that, it was only if we were blocking one we may as well block another. - \ / Okay, no problem on the inadvertent undo. Right, I don't think we should be preventing any user name creation. Like my earlier edit used to say, user name prevention is only when THE USER NAME ITSELF is offensive. In this case, they're not. That eliminated the first part of this filter. The second part is catching general vandalism that should be handled in one of the general vandalism filters, and was catching more non-GT than GT. That makes this filter mostly pointless so I had disabled entirely. - Wknight94 You know, I've actually found this filter to be quite useful, even if much of it is non-GT. There is almost no good reason to add obscenities in all caps. Currently we don't have a filter that checks for this and disallows the action. - KoH If it doesn't catch false positives, leave it running. For supportability, it should probably be merged into 52 though. (I changed the name here to reflect actual usage). - Wknight94 No, it's different. This checks not only for edit summaries, but also added content. (A more descriptive title would be "Adding obscenities in all caps," but that would be too obvious. If a vandal saw that in the log, they would know to put the obscenity in lowercase letters.) - KoH SUCKS, rearrange. - KoH Actually, not common enough to matter, so just alphabetize. - KoH Expand. - KoH Restrict to main namespace per FP on Jimbo's talk. - KoH Some more. - KoH Viagra, your mom. - KoH Define variable match for increased readability. - KoH please urgently fix so that it doesn't match PEACOCK (false positives) - Cen Added \b before COCK. - Ruslik Added ass with \b's. - KoH FP's on GAY. - KoH Renamed. - KoH No need to be private -Prodego Modified "RACIS" to "RACIS(T\|M)" per false positive +1 --NW +1, and change to better title. --NW +1 --NW 11/25 +2 --NW 11/26 +2 --NW 11/27 Extending to user talk, will revert if there are false positives. =TS +2 --NW 11/28 +1 --NW 12/7 +2 --NW 12/9 +2 --NW 12/13 Add \b to FAG for temporary fix (SFAGO) so that a user can create and/or edit an article. Would it be better to instead add & !(added_lines rlike "SFAGO") ? -- Soap removed \b to again be able to catch variants -- Soap Add FUKERS (but not FUK due to potential false positives) -- Shirik 1 Feb 2010 Word boundery added to beginning of FAG -- Shirik 5 Mar 2010 condom -- Soap autoconfirmed -> confirmed & autoconfirmed -- Shirik 21 Mar 2010 false positives -P don't disable entirely because of a few fp's, warn for now - KoH Adding EFF YOU - Someguy1221 Added some. made so things like 'PEEENNNISS' would stillmatch - TIm Changing to disallow: I reviewed some 100 edits flagged by this, and could find no False P's. --Tim Added looser, and Poooop, Tim Added AWESOME and SOOO, both things that I think shouldn't even be in the article space. --Tim remove FAG due to false positives which appear now and then (it's an acronym) ... previously this filter was warn-only, but now it's disallow -- Soap Just had a falsepositive where an IP reverted a user whose name was one of the proscribed strings ("WANKA") and was disallowed because it appeared in the edit summary. I think targeting the edit summary may be a tad overkill. -v-_-v rm AWESOME -- Soap adding FAGG (for faggot) back in. Can't match FAG because it is the name of a company. -- Soap Removing "your mom" section; disallowed by another filter. - Someguy1221 adding \>ASS, in order to allow editing of [[Liberty Bell]] (it will be present in removed_lines whenever \bA+SS+ is present in added_lines and thus nullifies itself). Probably temporary. -- Soap is douche commonly spelled without the u? I made it required. -- Soap false positive on FUK ( an airport in China) -- Soap ASS apparently is an acronym, has caused problems before, will remove for now rm GAY, will try for a while -- Soap Scunthorpe problem. - KoH This will match a page titled "SCUNTHROPE" not "Scunthrope". -Sole Soul Added "NAZI" and "JEWS". --Reaper 2012-02-29
Флаги:	Скрыть подробности этого фильтра от обычных участников Включить этот фильтр Отметить как удалённый
Последнее изменение фильтра:	12:21, 16 апреля 2012 — SirCotare (обсуждение \| вклад)
История:	Показать историю этого фильтра
Инструменты:	Экспортировать этот фильтр в другую вики{"row":{"af_id":"14","af_pattern":"!\"confirmed\" in user_groups \u0026\r\n(article_namespace == 0 \| article_namespace == 3) \u0026\r\n(match := \"ABUSER\|\\bA+SS+[- ]?H+O+L+E+\\b\|BITCH\|\\b(C+O+C+\|K+A+W+)K+S\\b\|LOO+S+E+R+\|SOOO\|CONVICTED\|[KC]UNT\|DILDO\|D+O+U+C+H+E+\|EFF+ (Y+O+U+\|U+)\|F+U+(KK+\|C+K\|K+C)\|GARBAGE\|HAGGER\|HITLER\|JEWS\|MENTALLY SICK\|M(WA\|U)HAHA\|N+I+GG+(E+R+\|A+H)\|N[A4]ZI\|PEDOPHILE\|FAGG\|PEA?N[UI1][S5]\|S+L+U+T+\|POOO+P?\|W+H+O+R+E+\|PERVERT\|RACIST\|S+H+[1I]+T+\|SOCK[ \\-]?PUPPET\|SUCK\|VAGINA\|VIAGRA\|WANK(A\|ER\|ING)\|(W\|WANKA)KNIGHT\") \u0026\r\n((summary rlike match) \|\r\n((added_lines rlike match) \u0026\r\n!(removed_lines rlike match) \u0026\r\n!(article_text rlike match)))","af_user":"15","af_user_text":"SirCotare","af_timestamp":"20120416112124","af_enabled":"1","af_comments":"Creating per RFPP. - KoH\r\nNot working ... - KoH\r\nRe-enabling, disallow off. - KoH\r\nToo many false positives from added_lines in removed_lines. - KoH\r\n\r\nCould it be changed to prevent the creation of \"Aaron Blakk\"? - \\ /\r\n\r\nFirst, why did you undo my last edit here? Second, why would you want to prevent the creation of user names that HELP us detect him? The user names themselves are not offensive, the edits are. - Wknight94\r\n\r\nIt was my first edit to the AF, must've inadvertantly done it - sorry. I see your point in re to that, it was only if we were blocking one we may as well block another. - \\ /\r\n\r\nOkay, no problem on the inadvertent undo. Right, I don't think we should be preventing any user name creation. Like my earlier edit used to say, user name prevention is only when THE USER NAME ITSELF is offensive. In this case, they're not. That eliminated the first part of this filter. The second part is catching general vandalism that should be handled in one of the general vandalism filters, and was catching more non-GT than GT. That makes this filter mostly pointless so I had disabled entirely. - Wknight94\r\n\r\nYou know, I've actually found this filter to be quite useful, even if much of it is non-GT. There is almost no good reason to add obscenities in all caps. Currently we don't have a filter that checks for this and disallows the action. - KoH\r\n\r\nIf it doesn't catch false positives, leave it running. For supportability, it should probably be merged into 52 though. (I changed the name here to reflect actual usage). - Wknight94\r\n\r\nNo, it's different. This checks not only for edit summaries, but also added content. (A more descriptive title would be \"Adding obscenities in all caps,\" but that would be too obvious. If a vandal saw that in the log, they would know to put the obscenity in lowercase letters.) - KoH\r\nSUCKS, rearrange. - KoH\r\nActually, not common enough to matter, so just alphabetize. - KoH\r\nExpand. - KoH\r\nRestrict to main namespace per FP on Jimbo's talk. - KoH\r\nSome more. - KoH\r\nViagra, your mom. - KoH\r\nDefine variable match for increased readability. - KoH\r\n\r\nplease urgently fix so that it doesn't match PEACOCK (false positives) - Cen\r\n\r\nAdded \\b before COCK. - Ruslik\r\n\r\nAdded ass with \\b's. - KoH\r\n\r\nFP's on GAY. - KoH\r\n\r\nRenamed. - KoH\r\n\r\nNo need to be private -Prodego\r\n\r\nModified \"RACIS\" to \"RACIS(T\|M)\" per false positive\r\n+1 --NW\r\n+1, and change to better title. --NW\r\n+1 --NW 11/25\r\n+2 --NW 11/26\r\n+2 --NW 11/27\r\n\r\nExtending to user talk, will revert if there are false positives. =TS\r\n+2 --NW 11/28\r\n+1 --NW 12/7\r\n+2 --NW 12/9\r\n+2 --NW 12/13\r\nAdd \\b to FAG for temporary fix (SFAGO) so that a user can create and/or edit an article. Would it be better to instead add \u0026 !(added_lines rlike \"SFAGO\") ? -- Soap\r\nremoved \\b to again be able to catch variants -- Soap\r\nAdd FUKERS (but not FUK due to potential false positives) -- Shirik 1 Feb 2010\r\nWord boundery added to beginning of FAG -- Shirik 5 Mar 2010\r\ncondom -- Soap\r\nautoconfirmed -\u003E confirmed \u0026 autoconfirmed -- Shirik 21 Mar 2010\r\n\r\nfalse positives -P\r\n\r\ndon't disable entirely because of a few fp's, warn for now - KoH\r\n\r\nAdding EFF YOU - Someguy1221\r\n\r\nAdded some. made so things like 'PEEENNNISS' would stillmatch - TIm\r\n\r\nChanging to disallow: I reviewed some 100 edits flagged by this, and could find no False P's. --Tim\r\n\r\nAdded looser, and Poooop, Tim\r\n\r\nAdded AWESOME and SOOO, both things that I think shouldn't even be in the article space. --Tim\r\nremove FAG due to false positives which appear now and then (it's an acronym) ... previously this filter was warn-only, but now it's disallow -- Soap\r\n\r\nJust had a falsepositive where an IP reverted a user whose name was one of the proscribed strings (\"WANKA\") and was disallowed because it appeared in the edit summary. I think targeting the edit summary may be a tad overkill. -v-_-v\r\nrm AWESOME -- Soap\r\nadding FAGG (for faggot) back in. Can't match FAG because it is the name of a company. -- Soap\r\n\r\nRemoving \"your mom\" section; disallowed by another filter. - Someguy1221\r\nadding \\\u003EASS, in order to allow editing of [[Liberty Bell]] (it will be present in removed_lines whenever \\bA+SS+ is present in added_lines and thus nullifies itself). Probably temporary. -- Soap\r\nis douche commonly spelled without the u? I made it required. -- Soap\r\nfalse positive on FUK ( an airport in China) -- Soap\r\nASS apparently is an acronym, has caused problems before, will remove for now\r\nrm GAY, will try for a while -- Soap\r\nScunthorpe problem. - KoH\r\nThis will match a page titled \"SCUNTHROPE\" not \"Scunthrope\". -Sole Soul\r\nAdded \"NAZI\" and \"JEWS\". --Reaper 2012-02-29","af_public_comments":"Vandalism in all caps","af_hidden":"0","af_hit_count":"2","af_throttled":"0","af_deleted":"0","af_actions":"disallow","af_global":"0","af_group":""},"actions":{"disallow":{"action":"disallow","parameters":[""]}}}

Действия, выполняемые при совпадении Применять меры только если участник превышает предел

Количество разрешённых действий:

Отрезок времени:

секунд

Сужение по группам:

(по одному на строке, соединения запятыми)

user

Принимать эти меры после предупреждения участника

Системное сообщение для предупреждений:

Название страницы другого сообщения:

(без префикса MediaWiki)

Действия:

Запретить участнику выполнить запрашиваемое действие

Снять с участника статус автоподтверждения

Заблокировать участника или IP-адрес

Исключить участника из всех привилегированных групп

Отметить правку для дальнейшей проверки

Применяемые метки (по одной на строку):

Материал из ЭнциклопАтис