Last modified: 2013-02-05 12:22:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T38484, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36484 - Increase $wgAbuseFilterEmergencyDisable* on zhwiki
Increase $wgAbuseFilterEmergencyDisable* on zhwiki
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: community-consensus-needed
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-03 16:11 UTC by Liangent
Modified: 2013-02-05 12:22 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Liangent 2012-05-03 16:11:01 UTC
We made https://zh.wikipedia.org/wiki/Special:%E9%98%B2%E6%BB%A5%E7%94%A8%E8%BF%87%E6%BB%A4%E5%99%A8/110 but they're hitting the filter so fast to make this filter auto-disabled. Afterwards we split it into two: http://zh.wikipedia.org/wiki/Special:%E9%98%B2%E6%BB%A5%E7%94%A8%E8%BF%87%E6%BB%A4%E5%99%A8/111 http://zh.wikipedia.org/wiki/Special:%E9%98%B2%E6%BB%A5%E7%94%A8%E8%BF%87%E6%BB%A4%E5%99%A8/112 to keep it working.

Now the same thing happens to http://zh.wikipedia.org/wiki/Special:%E9%98%B2%E6%BB%A5%E7%94%A8%E8%BF%87%E6%BB%A4%E5%99%A8/115 . In theory I can split any filter into twenty to make it never overload but it looks so hacky. People in #wikimedia-tech suggest me request a configuration change here but I don't have a known nice enough new value.
Comment 1 Sam Reed (reedy) 2012-05-03 17:34:05 UTC
Defaults are:

// Disable filters if they match more than X edits, constituting more than Y% of the last Z edits, if they have been changed in the last S seconds
$wgAbuseFilterEmergencyDisableThreshold = 0.05;
$wgAbuseFilterEmergencyDisableCount = 2;
$wgAbuseFilterEmergencyDisableAge = 86400; // One day.
Comment 2 Liangent 2012-05-03 19:40:35 UTC
(In reply to comment #1)
> Defaults are:
> 
> // Disable filters if they match more than X edits, constituting more than Y%
> of the last Z edits, if they have been changed in the last S seconds
> $wgAbuseFilterEmergencyDisableThreshold = 0.05;
> $wgAbuseFilterEmergencyDisableCount = 2;
> $wgAbuseFilterEmergencyDisableAge = 86400; // One day.

I know the defaults but dunno better values.
Comment 3 Nemo 2012-09-16 17:54:09 UTC
zh.wiki has too many filters and they are too aggressive, as I reported (and was partly fixed) before; I can't see the filter in question but raising limits seems a very bad idea in general, abusefilter is nasty enough.
It's also something which would require a wide consensus (which I don't see) after clear explanations of what filters are doing to the community (which is mostly unaware).
Comment 4 Andre Klapper 2013-02-05 11:37:13 UTC
(In reply to comment #3)
> It's also something which would require a wide consensus (which I don't see)
> after clear explanations of what filters are doing to the community (which is
> mostly unaware).

Liangent: Has there been any Village Pump discussion about this?
Comment 5 Liangent 2013-02-05 12:22:12 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > It's also something which would require a wide consensus (which I don't see)
> > after clear explanations of what filters are doing to the community (which is
> > mostly unaware).
> 
> Liangent: Has there been any Village Pump discussion about this?

No and this doesn't seem necessary for now.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links