Jump to content

MediaWiki talk:Spam-blacklist

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Hu12 (talk | contribs) at 16:16, 10 January 2008 (→‎FinMath.com). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

    Mediawiki:Spam-blacklist is meant to be used by the spam blacklist extension. Unlike the meta spam blacklist, this blacklist affects pages on the English Wikipedia only. Any administrator may edit the spam blacklist. See Wikipedia:Spam blacklist for more information about the spam blacklist.


    Instructions for editors

    There are 4 sections for posting comments below. Please make comments in the appropriate section. These links take you to the appropriate section:

    1. Proposed additions
    2. Proposed removals
    3. Troubleshooting and problems
    4. Discussion

    Each section has a message box with instructions. In addition, please sign your posts with ~~~~ after your comment.

    Completed requests are archived. Additions and removals are logged, reasons for blacklisting can be found there.

    Addition of the templates {{Link summary}} (for domains), {{IP summary}} (for IP editors) and {{User summary}} (for users with account) results in the COIBot reports to be refreshed. See User:COIBot for more information on the reports.


    Instructions for admins
    Any admin unfamiliar with this page should probably read this first, thanks.
    If in doubt, please leave a request and a spam-knowledgeable admin will follow-up.

    Please consider using Special:BlockedExternalDomains instead, powered by the AbuseFilter extension. This is faster and more easily searchable, though only supports whole domains and not whitelisting.

    1. Does the site have any validity to the project?
    2. Have links been placed after warnings/blocks? Have other methods of control been exhausted? Would referring this to our anti-spam bot, XLinkBot be a more appropriate step? Is there a WikiProject Spam report? If so, a permanent link would be helpful.
    3. Please ensure all links have been removed from articles and discussion pages before blacklisting. (They do not have to be removed from user or user talk pages.)
    4. Make the entry at the bottom of the list (before the last line). Please do not do this unless you are familiar with regular expressions — the disruption that can be caused is substantial.
    5. Close the request entry on here using either {{done}} or {{not done}} as appropriate. The request should be left open for a week maybe as there will often be further related sites or an appeal in that time.
    6. Log the entry. Warning: if you do not log any entry you make on the blacklist, it may well be removed if someone appeals and no valid reasons can be found. To log the entry, you will need this number – 183417897 after you have closed the request. See here for more info on logging.

    Proposed additions


    abemadi.com

    See Special:Contributions/84.102.176.131 and Special:Contributions/Abemadi. --B (talk) 22:52, 5 January 2008 (UTC)[reply]

    Cross-wiki spam:
    Domain:
    If we blacklist him it should be on meta because it's cross-wiki. I suggest waiting to see if he stops, if not, then we take him to meta. (If you read the warning I left him, you'll see that meta blacklisting is a big deal for a site owner.)
    I'm out of time right now -- if you copy the user and domain data templates I used above and make a report at WT:WPSPAM, that will automatically trigger COIbot to watch this domain.
    Gotta run --A. B. (talk) 14:42, 6 January 2008 (UTC)[reply]
    I've made an entry at WT:WPSPAM. --A. B. (talk)
     Defer to WPSPAM --A. B. (talk) 03:47, 8 January 2008 (UTC)[reply]


    asianmediawiki.com lunapark6.com

    See WT:WPSPAM#spam.asianmediawiki.com spam.lunapark6.com. MER-C 03:50, 9 January 2008 (UTC)[reply]

    SmartCard Consultancy (Pound Ridge, NY) spam on Wikipedia

    Spam site
    westchestertowns.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:frSpamcheckMER-C X-wikigs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: searchmeta • Domain: domaintoolsAboutUs.com
    Article spamed
    Westchester County, New York
    Spam edits
    Virtually all of the edits from 68.198.203.213 (talk · contribs) [1]

    [2] [3] [4] [5] [6] [7] [8]

    --24fan24 (talk) 21:45, 9 January 2008 (UTC)[reply]

    There are additional domains and accounts. Let me gather all the data and I will blacklist. --A. B. (talk) 23:17, 9 January 2008 (UTC)[reply]
    Spam domain
    Google Adsense ID: 9665591883320014


    Related domains


    Other related domains
    Not blacklisted:


    Accounts


    Reference
    --A. B. (talk) 02:42, 10 January 2008 (UTC)[reply]
     Done --A. B. (talk) 04:47, 10 January 2008 (UTC)[reply]

    FinMath.com

    Spam site finmath.com
    Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:frSpamcheckMER-C X-wikigs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: searchmeta • Domain: domaintoolsAboutUs.com
    Evidence

    172.134.174.70 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
    172.163.205.149 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
    172.129.172.181 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
    172.134.128.193 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)

    These are all AOL anons and pointless to block.

    Ronnotel (talk) 15:46, 10 January 2008 (UTC)[reply]

    Agree, and  Done. thanks --Hu12 (talk) 16:15, 10 January 2008 (UTC)[reply]

    Proposed removals


    Troubleshooting and problems

    Problem with the blacklist: I want to use the db-copyvio speedy deletion tag to get an article deleted. The db-copyvio tag has as a parameter the url of the website which is being copied. The website being copied is a blacklisted one, ezinearticles. Oops, the spam filter kicks in. This is bad.--Xyzzyplugh (talk) 19:46, 11 December 2007 (UTC)[reply]

    Try adding without the http:, the checking admin will copy & paste to check it.--Hu12 (talk) 19:50, 11 December 2007 (UTC)[reply]
    Or don't provide the link in the db template, and add it below it (put <nowiki></nowiki> around). Or put it on my talk page and I'll have a look. -- lucasbfr talk 19:55, 11 December 2007 (UTC)[reply]

    Discussion

    archive script

    Eagle 101 said he had one running on meta, is it possible to get it up and going here?--Hu12 10:27, 15 November 2007 (UTC)[reply]

    Would be good - Eagle hasn't been working on Meta for a while though & I've not seen anything (there was supposed to be a logging script too!) --Herby talk thyme 12:10, 15 November 2007 (UTC)[reply]
    • Great news, Ive written a script that can archive this page given the templates that we use, I can create a approved archive along with a rejected archive if people are interested. βcommand 06:51, 4 January 2008 (UTC)[reply]
    "Interested" - bit of an understatement there :) Great news - please feel free to help/supply the script. I tend to leave stuff around a week in case anyone shouts or adds more (archives once done should be left alone). How would you handle the "discussion" type bits? Cheers --Herby talk thyme 09:40, 4 January 2008 (UTC)[reply]
    First question, do you want approved and rejected request in separate archives? as for the discussions we could get Misza bot over here for things older than 30 days. βcommand 17:13, 4 January 2008 (UTC)[reply]
    I would think one archive, seperate sections, like it is currently[9], not sure if the script can do that, but if so, doubt there would be objections in implementation...--Hu12 (talk) 00:24, 10 January 2008 (UTC)[reply]
    There is no simple way of editing sections using the bot. (section editting is evil). it would just be one large archive. βcommand 00:59, 10 January 2008 (UTC)[reply]

    blogspot.com

    I added countingcrowsnew.blogspot.com, freemodlife.blogspot.com, and googlepackdownload.blogspot.com to the blacklist. I made a previous report about the blogspot sites and they're being spammed by the same blocked sockpuppet who I filed a report about here. Spellcast (talk) 22:03, 28 November 2007 (UTC)[reply]

    Update: I've also added b5050-raffle.blogspot.com, gpd2008.blogspot.com, and itsleaked.blogspot.com. They were being spammed by the same blocked sock in that report. Spellcast (talk) 05:18, 29 November 2007 (UTC)[reply]

    I'm inclined to blacklist the domain then whitelist where needed but some heavy flak is likely to arrive? --Herby talk thyme 08:06, 29 November 2007 (UTC)[reply]
    From an en:Wikipedia mission perspective (though possibly not your personal perspective:) a bigger issue than the flak that will be generated is the disruption to editing. I believe a lot of pages, particularly biographies of living people, contain legitimate links to the subject's blog - many of which are hosted on blogspot. Simply blacklisting and then waiting for whitelisting requests will likely
    1. overwhelm the whitelist page here and on meta (which given you are one of the most active admins on both, may not be ideal for you!)
    2. be confusing and frustrating to a lot of editors especially newbies, but also any who are not familiar with the blacklist/whitelist set up
    3. lead to a loss of legitimate links and legitimate edits as people struggle to work out whether to keep their edit and lose the link or the other way round while any whitelist request is ongoing.
    I think a move like that will take some careful planning and preparation to avoid these issues (might also help cut down some of the heat). One way or another, I think we need human editors to assess the current blogspot links on article pages and enter appropriate ones on the whitelist before the blacklisting goes into effect. I don't think such a move will cut out most of the flak though, so we might want to ensure there are other admins involved to help spread the weight, and a nicely presented page of evidence of the issues the domain causes to point people to.
    Blogspot certainly gets spammed a lot more than most domains, and I support blacklisting. But It's still a domain that has a lot of good links and I think it's important to think through how a move like that will impact people, and to adjust to the situation. -- SiobhanHansa 13:54, 29 November 2007 (UTC)[reply]
    Briefly - needs quite a bit of thought but equally is worth that amount of thought --Herby talk thyme 13:55, 29 November 2007 (UTC)[reply]
    There are many, many legitimate links to the domain, not only to blogs belonging to article subjects but to blogs belonging to Wikipedia contributors. Better to blacklist individual blogs as needed. --bainer (talk) 16:23, 29 November 2007 (UTC)[reply]
    Not sure why Wikipedia contributors would be adding their own blogs? A very limited number of blogs actualy meet WP:RS and even fewer still meet the requirements of WP:EL or are a blog that is the subject of the article or an official page of the articles subject. There are currently 32,916 blogspot.com Blog links on Wikipedia, if whitelisting even a thousand "legitimate links", its worth it.--Hu12 (talk) 17:03, 29 November 2007 (UTC)[reply]
    You've presented some convincing reasons to leave certain blog links out of Wikipedia, but not a reason to leave all blog links out. Wikipedia contributors might want to link to their blogs because, you know, it is possible for said contributors to frequent websites on the internet other than Wikipedia :P See WP:COMMUNITY. There is also a performance cost to whitelisting and blacklisting; as far as I can tell, 1000 whitelisted entries costs more computationally than 1000 blacklisted entries (instead of using one large regex, which is how the blacklist works, you're doing 1000 individual regex replacements). GracenotesT § 18:04, 29 November 2007 (UTC)[reply]
    I was under the impression server load was something we were supposed to leave up to the developers to worry about. If they see an issue and ask for a reassessment that would be one thing, but its not a good argument against a tactic without their weight behind it.
    The suggestion isn't that all blogs should be banned. the suggestion is that this particular domain gets spammed so much it would be beneficial to the project to blacklist it and only white list the ones that are appropriate. -- SiobhanHansa 18:13, 29 November 2007 (UTC)[reply]
    Hu12 I think it's important not to overstate the case here. Not all of the ~32,000 links (assukming the 1K of good links estimate) that are not legitimate external links or citations will actually be harmful to Wikipedia. While editors' own blogs on their user pages aren't necessary to the project, in the vast majority of cases they do no harm and may help editors fell a bond that connects them to the project. Many more will be links from discussions and projects. While I don't think that's a reason for keeping a domain that is also being spammed so much - it's not the case that we do 32,000 links worth of "good" by removing them. For the most part we only really benefit from the spam and poorly placed article links that go. -- SiobhanHansa 18:08, 29 November 2007 (UTC)[reply]

    (unindent, crosspost my post from WT:WPSPAM)

    The rule \bblogspot\.com is (currently) not on COIBot's monitorlist. Some of the sub-domains have been added via WT:WPSPAM, or have been caught by the automonitoring of COIBot (mainly because the name of the editor is the same as the name of the subdomain on blogspot.com).

    Still, a linksearch on the resolved IP of blogspot.com (72.14.207.191) results in a mere 118 results (all COIBot linkreports)! Often the multiple use of the single subdomains is not a cause for blacklisting, as they may only have been used once or twice. Also, I suspect there are tens of thousands of blogspot sub-domains out there, but these are only the links that are caught because the wiki username overlaps with the domainname of the subdomain (or have been reported here). Would this cumulative behaviour warrant blacklisting of \bblogspot\.com .. here, or even on meta? --Dirk Beetstra T C 12:37, 30 November 2007 (UTC)[reply]

    Appropriate links may indeed be a problem, though the majority will fail some or many of the policies and guidelines here (or don't even have to be a notable fact, or do not need to be a working link while being mentioned; "Mr. X has a a blog on Blogspot.<ref>primary reliable source stating that the blog is the official blog</ref>"; we are not a linkfarm), and I would argue that the spam/coi part of the problem becomes a bit difficult to control... --Dirk Beetstra T C 14:23, 30 November 2007 (UTC)[reply]
    Crosspost spamlink template for blogspot.com to link this discussion to the linkreports from COIBot. --Dirk Beetstra T C 10:31, 3 December 2007 (UTC)[reply]
    Please try to remember how frustrating generic, unexpected spam blocks can be for new and incautious editors. Last time I "checked", if you make an edit with Internet Explorer and you post it directly without preview (two things you should never do), then if the spam blacklist comes up your text is gone. Back arrow gets you the original text of the article. Edits that die that way may not get remade, and they may sour the editor on further contributions. I don't think there should be any blocks on top-level domains or large general purpose Internet sites. 70.15.116.59 23:46, 3 December 2007 (UTC)[reply]
    I have to disagree in this case - there's concern that the dynamic IP spamming it is using it to perpetrate scams or send out computer bugs. -Jéské (Blah v^_^v) 04:55, 4 December 2007 (UTC)[reply]
    There's no way we can realistically do this. blogspot has an Alexa traffic rank of 12 - it's higher than Amazon.com - and has well over 30,000 links on en.wp alone. Adding this would be incredibly disruptive to thousands of articles. Unless someone wants to go through all 32,000 links to find the ones that can be kept so we can whitelist them, there's no way we can do this. The ones that are spam should be removed and blacklisted, but WP:EL and WP:RS are not very good reasons to completely forbid links to a domain. Mr.Z-man 16:47, 8 December 2007 (UTC)[reply]

    No edit box in the Spam filter notice

    Why does the "Spam filter notice" not contain an edit box? This necessitates pressing the back button which in IE (I'm reluctantly using it at the moment) means all edits are lost. There's a possible way around it, to open the article in a new tab, remove the spam link, save it, and then hit refresh in the "Spam filter notice" window to resubmit, but this is a hack and we shouldn't be inconveniencing innocent users like this. (Has happened to me twice already today, once I was adding a new section to a talk page and couldn't save because the existing talk page had a blacklisted link it... like wtf?!) --kingboyk (talk) 14:13, 29 December 2007 (UTC)[reply]

    I put the header in a template to reduce size of this request page and included MediaWiki:Spam-blacklist/Indicators which is loosly based off of RCU's indicators.--Hu12 (talk) 15:58, 30 December 2007 (UTC)[reply]

    Google "I'm feeling lucky"

    Would the following regexes work?

    • \bgoogle.com/search?.*&btnI
    • \bgoogle.com/search?btnI

    Random832 20:09, 2 January 2008 (UTC)[reply]

    Blacklist logging

    {{WPSPAM|0#section_name}} →(replacing '0' with the correct "oldid" (ie. permalink) example shown here).

    For example:

    {{WPSPAM|182725895#Blacklist_logging}}

    results in:

    See WikiProject Spam report

    This should aid in requests originating from Wikipedia_talk:WikiProject_Spam and for use with the entry log here. I've added a snipit in the header--Hu12 (talk) 15:20, 4 January 2008 (UTC)[reply]