Last modified: 2009-03-11 12:46:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 4205 - Edit alert instead of blocking
Edit alert instead of blocking
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Normal enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 2508
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-07 16:08 UTC by Peter Gervai (grin)
Modified: 2009-03-11 12:46 UTC (History)
3 users (show)

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


Attachments

Description Peter Gervai (grin) 2005-12-07 16:08:20 UTC
[I did not analyse the feasibility of this feature, nor I state that there isn't
a better solution, to which I am open to hear]

Blocking some idiots are tough: they're using large netblocks, which isn't
really possible to ban without alienating lots of nice people. 

It would be nice to have the possibility to "mark" netblocks, which could be
listed as "show only marked" in Recentchanges, or to show them in red (or
whatever emphasizing is active in the skin) in Recent changes / Watchlists. It
would make it easier to see and follow known anon vandals without having to
resort to banning a large subnet.

I would show these marked nets when a new user is created from them, but
probably not the general non-anon edits (this is probably to be discussed, it
may or may not prove useful and/or insecure). So sockpuppet creation could be
followed more easily.
Comment 1 Peter Gervai (grin) 2006-12-19 10:54:03 UTC
see bug#2508
Comment 2 Siebrand Mazeland 2009-02-02 12:04:17 UTC
Should be resolvable using the extension AbuseFilter and the recently added Tags feature. Recategorising to the extension, so it can be assessed there.
Comment 3 Andrew Garrett 2009-03-11 12:46:17 UTC
Doable with the extension.

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


Navigation
Links