Last modified: 2007-07-06 13:01:09 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 10478 - Spam blacklist
Spam blacklist
Status: RESOLVED DUPLICATE of bug 8492
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-06 12:53 UTC by Huji
Modified: 2007-07-06 13:01 UTC (History)
0 users

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


Attachments

Description Huji 2007-07-06 12:53:25 UTC
I think a local spam blacklist could have its own benefits. For example, there are many weblogs hosted on famous Persian bloggers, and every now and then, someone appears to post links to his personal weblog on Persian Wikipedia, with IP. It would be a time consuming process to ask for it being added to the Meta spam blacklist, and in the mean time, he will have time to add many links and waiste our time by reverting his edits, blocking his IPs for 2 hours, etc.

A fast solution would be to add the address to the local spam list, and remove it after a few days, if needed.

The list could be protected, just as in Meta, so only sysops could edit that.

What do you think?
Comment 1 Brion Vibber 2007-07-06 13:01:09 UTC

*** This bug has been marked as a duplicate of bug 8492 ***

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


Navigation
Links