Last modified: 2010-05-15 14:36:07 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 T3367, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 1367 - Preventing Wiki Link Spam
Preventing Wiki Link Spam
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: High enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.google.com/googleblog/2005...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-19 22:04 UTC by Tom
Modified: 2010-05-15 14:36 UTC (History)
0 users

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


Attachments

Description Tom 2005-01-19 22:04:42 UTC
I'm not terribly sure what this would be but I'd consider it a big
enhancement/fix.  Currently, as most of us know, the MediaWiki software is a
popular target among spammers for dropping their links into pages.  Logon-only
sites have this problem too, as accounts are created and then used to spam. 
While there is a MediaWiki spam fix, which blocks most of it, there's another
fix now from google.

The idea, mentioned at:
http://www.google.com/googleblog/2005/01/preventing-comment-spam.html, is to add
ref="nofollow" to external links automatically.  This means that there's no
profit, as even if the spam does get placed there and stays there long enough
for google to see it, it's not profitable.

If this could be included in mediawiki so that links were changed to NoFollow if
they aren't interwiki/intrawiki links, that may be a boon for the fight against
wikispam.
Comment 1 Antoine "hashar" Musso (WMF) 2005-01-19 22:09:21 UTC
Already included for REL1_4 . Have a look at the next beta :o)
Comment 2 Tom 2005-01-19 22:19:39 UTC
Wow, there was no bug on it and google only announced it yesterday, and it's
picked up by /. today.  That's probably the fastest turnaround ever.

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


Navigation
Links