घर
बेतरतीब
निकट
लॉग-इन करें
सेटिंग्स
दान करें
विकिपीडिया के बारे में
अस्वीकरण
खोजें
Viewing abuse filter 30: Vandalism in all caps
घर
Recent filter changes
पूर्व बदलाव परीक्षा करें
दुरुपयोग लॉग
फ़िल्टर 30 सम्पादन
फ़िल्टर प्राचल
फ़िल्टर आइ॰डी:
30
वर्णन
फ़िल्टर हिट गिनती:
263 हिट
आँकड़े:
पिछले 817 कार्यों में से इस फ़िल्टर द्वारा 0 (0%) पकड़े गए हैं।
शर्तें:
!"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+(K+|C+K|K+C)|\bG+A+Y+\b|GARBAGE|HAGGER|HITLER|MENTALLY SICK|M(WA|U)HAHA|N+I+GG+(E+R+|A+H*)|PEDOPHILE|PE(ANUS|NIS|N15)|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|((YO)?U'?RE?|Y(ER|A'?|O'?)) ?(MOM(MY)?|MAMA|MOTHER)") & ((summary rlike match) | ((added_lines rlike match) & !(removed_lines rlike match)))
!"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+(K+|C+K|K+C)|\bG+A+Y+\b|GARBAGE|HAGGER|HITLER|MENTALLY SICK|M(WA|U)HAHA|N+I+GG+(E+R+|A+H*)|PEDOPHILE|PE(ANUS|NIS|N15)|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|((YO)?U'?RE?|Y(ER|A'?|O'?)) ?(MOM(MY)?|MAMA|MOTHER)") & ((summary rlike match) | ((added_lines rlike match) & !(removed_lines 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
झंडे:
सार्वजनिक दृश्य से इस फ़िल्टर का विवरण छिपाएँ
इस फ़िल्टर को सक्षम करें
हटाया गया चिन्हित करें
फ़िल्टर का अंतिम संशोधन:
Siddhartha Ghai
(
वार्ता
|
योगदान
)
द्वारा
19:31, 22 मार्च 2012
को
इतिहास:
इस फ़िल्टर का इतिहास देखें
उपकरण:
इस फ़िल्टर को किसी अन्य विकि को निर्यात करें
{"data":{"rules":"!\"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+(K+|C+K|K+C)|\\bG+A+Y+\\b|GARBAGE|HAGGER|HITLER|MENTALLY SICK|M(WA|U)HAHA|N+I+GG+(E+R+|A+H*)|PEDOPHILE|PE(ANUS|NIS|N15)|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|((YO)?U'?RE?|Y(ER|A'?|O'?)) ?(MOM(MY)?|MAMA|MOTHER)\") \u0026\r\n((summary rlike match) |\r\n((added_lines rlike match) \u0026\r\n!(removed_lines rlike match)))","name":"Vandalism in all caps","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","group":"default","actions":{"disallow":[]},"enabled":true,"deleted":false,"privacylevel":0,"global":false},"actions":{"disallow":[]}}
मिलान होने पर की जाने वाली कार्यवाही
सदस्य पर कार्यवाही निम्न सीमा लाँघ जाने के बाद करें
संख्या जितने कार्यों की अनुमति देनी है:
समय की अवधि (सेकेंड में):
Group throttle by:
user
See
the documentation on mediawiki.org
.
सदस्य को एक चेतावनी देने के बाद यह कार्यवाही करें
चेतावनी के लिये प्रयोग किया जाने वाला अंतरफल संदेश:
abusefilter-warning
अन्य संदेश
अन्य संदेश का पृष्ठ नाम:
(मीडियाविकी उपसर्ग के बिना)
चुने हुए सन्देश का पूर्वावलोकन करें
सदस्य को फ़िल्टर द्वारा पकड़ा कार्य करने से रोकें
System message to use for disallowing:
abusefilter-disallowed
Other message
Page name of other message:
(without "MediaWiki:" prefix)
Show/Hide preview of selected message
सदस्य को स्वत: स्थापित सदस्य समूह से हटाएँ
संपादन को आगे जाँच के लिये इस संदेश के साथ दर्शाएँ
लगाए जाने वाले
टैग
(एक प्रति पंक्ति)
Require the user to complete a CAPTCHA in order to proceed with the action. Users with permission to skip a CAPTCHA are exempt.
