MediaWiki talk:Spam-blacklist
MediaWiki:Spam-blacklist is a page in the MediaWiki namespace, which only administrators may edit. To request a change to it, please follow the directions at Wikipedia:Spam blacklist. |
Spam blacklists |
---|
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.
There are 4 sections for posting comments below. Please make comments in the appropriate section. These links take you to the appropriate section:
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.
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.
- Does the site have any validity to the project?
- 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.
- 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.)
- 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.
- 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.
- 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 – 332736073 after you have closed the request. See here for more info on logging.
- →Snippet for logging: {{/request|332736073#section_name}}
- →Snippet for logging of WikiProject Spam items: {{WPSPAM|332736073#section_name}}
- →A user-gadget for handling additions to and removals from the spam-blacklist is available at User:Beetstra/Gadget-Spam-blacklist-Handler
Proposed additions
Instructions for proposed additions
Please provide diffs ( e.g. [[Special:Diff/99999999]] ) to show that there has been spamming! Completed requests should be marked with {{done}}, {{not done}}, or another appropriate indicator, and then archived. |
maltagenealogy.com and saidvassallo.com
maltagenealogy.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- Related site that the sockpuppet attempted to add.
saidvassallo.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- Tancarville (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Mobile historian (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Vassallo5448 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
This link has historically been spammed. We've got a probable sockpuppeteer. I'd like this site blacklisted to take the wind out of his sails. This will save much volunteer time. Jehochman Talk 22:46, 19 November 2009 (UTC)
- I've also, in the course of looking over the links from the suspect site, discovered User:Vassallo5448, who works with the same site, shares a similar name to Tancarville's (whose real name is Charles Said-Vassallo, the owner of the suspect website), and who started his Wikipedia account in September, within three days of Mobile historian's. The common link of all three editors is in their heavy interest in Maltese aristocracy, in their use of this website, and in the website's promotion on Wikipedia. RGTraynor 15:17, 20 November 2009 (UTC)
- SAID-VASSALLO GROUP PTY LTD
- Possibly related;
- (saidvassallo.com/contact.htm {edited}@optusnet.com.au)
- optusnet.com.au: Linksearch en - meta - de - fr - simple - wikt:en - wikt:fr • MER-C Cross-wiki • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced • COIBot-Local - COIBot-XWiki - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.org • Live link: http://www.optusnet.com.au
- Vassallo Industries Industrias Vassallo, (zoominfo.com/Search/PersonDetail.aspx?PersonID=778139155 Webmaster)
- vassalloindustries.com: Linksearch en - meta - de - fr - simple - wikt:en - wikt:fr • MER-C Cross-wiki • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced • COIBot-Local - COIBot-XWiki - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.org • Live link: http://www.vassalloindustries.com
- Clear abuse re maltagenealogy.com and saidvassallo.com, spam sock(meat)puppetry Added--Hu12 (talk) 19:10, 27 November 2009 (UTC)
signsvisualny.com
signsvisualny.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com -- user has spammed this url to signage unabatedly. semi prot was denied as it was said that the site should be added to the blacklist instead, since it's one spam site and multiple IPs Theserialcomma (talk) 17:52, 26 November 2009 (UTC)
- Signs Visual Industries, Inc. /Spammed
- signsvisual.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- signsnewyork.net: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- largeformatprintingnewyork.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- Related /spammed
- bannersnewyork.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- Accounts
- 207.38.189.31 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
199.219.144.53 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
208.125.3.245 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
Added--Hu12 (talk) 19:34, 27 November 2009 (UTC)
earlywarningsys.com
earlywarningsys.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com - Various IPs have spammed this site onto the article for Civil defense siren for months, resuming as soon as the various rounds of semi-protection have lapsed. Dayewalker (talk) 02:58, 28 November 2009 (UTC)
- Accounts (just a sampling of the IPs)
- Accounts (just a sampling of the IPs)
- 174.39.248.106 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.171.51 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.236.30 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.218.122 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.193.12 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.252.65 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Redirect page
- disastersirens.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- More spam IP's
- 174.39.208.254 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 98.135.158.68 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.142.172 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 69.146.138.235 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.145.107 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.210.207 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.245.56 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Trainman11185 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- 174.39.219.214 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.224.185 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.157.247 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Serious spamming including editwarring and bouts of vandalism[1][2][3][4], thanks for the report Added--Hu12 (talk) 04:54, 28 November 2009 (UTC)
- Attempting to curcumvent, spamming text links[5][6] under;
- 174.39.242.73 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.242.73 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- These are the ranges;
- 174.39.192.0/18 (talk • contribs • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.128.0/17 (talk • contribs • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 98.135.158.68/32 (talk • contribs • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 69.146.138.235/32 (talk • contribs • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- If disruption continues we can consider range blocking as needed--Hu12 (talk) 15:35, 1 December 2009 (UTC)
- Back at it;
- Was spammed previously and is related to current activity; adding youtube.com/watch?v=9JDLl1CMuNs
- 174.39.205.251 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 174.39.246.231 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Also range blocked 174.39.192.0/18 for a month--Hu12 (talk) 05:08, 3 December 2009 (UTC)
- Attempting to curcumvent, spamming text links[5][6] under;
worldphototour.org
worldphototour.org: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
Persistent spamming over two years. See WikiProject Spam report. MER-C 02:44, 30 November 2009 (UTC)
- Added--Hu12 (talk) 07:11, 30 November 2009 (UTC)
triond.com
- links
- triond.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- computersight.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- healthmad.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- quazen.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- authspot.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- gameolosophy.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- notecook.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- socyberty.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- gomestic.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- trifter.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- bizcovering.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- sportales.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- telewatcher.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- cinemaroll.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- webupon.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- bookstove.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- musicouch.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- writinghood.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- purpleslinky.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- accounts
- 202.138.102.144 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- related report
All listed sites are part of the triond.com network. An account with Triond.com allows a user to upload a story to any of these sites, all of which are within the triond.com network. The network allows anyone to self-publish material, with no editorial oversight. A handful of the articles may have some degree of research - but the authors are unknown, and most appear to be using these sites to publish material that would fail WP:NOR if posted directly to Wikipedia.
From triond.com/info/how-it-works :
"Triond helps showcase your content so your work gets maximum readership and you earn recognition. As soon as your content is published, it begins generating revenue from several income sources, such as display and contextual advertising that appears on the pages of your content. We share with you 50% of the revenue generated by your content."
Given the content and the "how-it-works" evidence, this site appears to be a variant of the ehow concept. Some links may be reasonable to be white-listed if established editors find quality links to request; but most are simply allow original research to be disguised as a reliable source. --- Barek (talk • contribs) - 18:47, 1 December 2009 (UTC)
- Thanks for the indepth report. Additionaly seems theres plenty of Spam evidence (COIBot in links), and would appear the sites are nothing more than vehicles for a pay-per-spam link-building scheme. Done--Hu12 (talk) 18:26, 2 December 2009 (UTC)
whoguideline.blogspot.com
Repeatedly added to multiple articles by many different IPs. -- Ed (Edgar181) 18:30, 3 December 2009 (UTC)
- whoguideline.blogspot.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
Some of the IPs:
- 59.184.147.36 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.94.133.231 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.95.76.138 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 120.60.133.167 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.95.80.87 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.95.78.65 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.95.77.245 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.95.81.129 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.95.80.49 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.94.130.203 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.95.82.178 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 129.7.222.204 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.95.75.134 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 59.93.80.115 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 118.94.130.60 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Done. good work--Hu12 (talk) 04:36, 8 December 2009 (UTC)
brownplanet.com
- brownplanet.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
Actually, having checked the archives, this was blacklisted by Beetstra a day or so ago. However, there are a lot - a lot - of URLs that redirect to brownplanet. They all seem to have been added by the same IP, 76.168.240.25.
- 76.168.240.25 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
I had actually gone through and checked most of the IP's edits, and the vast majority of the URLs a) all redirect to brownplanet, and b) all originate from the same IP (according to WHOIS). I'd almost finished blacklisting them when my computer crashed (grrr) so I'll have to settle for posting this note for now. If anyone wants to take on the task of blacklisting these URLs before I get back to it, that would be great. I've indef-blocked the IP, as they're the only one using it. Cheers. --Ckatzchatspy 10:45, 4 December 2009 (UTC)
- I'll generate a userreport for you. Top 10: romeoaventura.com (11), luisguzman.com (9), jacquelinebracamontes.com (8), (7), chicanorap.net (6), rocketeria.com (5), gracielitabeltran.com (5), espinosapaz.com (5), tonydice.com (4), elcompachalino.com (4). --Dirk Beetstra T C 22:15, 7 December 2009 (UTC)
- I have added brownplanet.com also to XLinkBot. The bots do an attempt to see if the site is a redirect site (loading header information), and XLinkBot reverts if a site redirects to a revertlisted site. This detection is not fail-save (it depends on how the redirect site is working), but it does catch some, and may help in finding more redirect sites. --Dirk Beetstra T C 08:47, 8 December 2009 (UTC)
www.scribd.com/doc/21733512/Principles-101 and www.manhood101.com
Multiple editors have been spamming these related links, sometimes as "M a n h o o d 1 0 1 . c o m" of a totally non-notable men's rights website. Most of the accounts have been blocked for spamming, but replacements are recreated every few days to continue the edits, as well as making some disputed assertions on the Fort Hood shootings page.
- Wik09wik (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Payjacks7 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Bean007 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Dan23tss (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
Thanks.--Slp1 (talk) 18:28, 7 December 2009 (UTC)
- Clear abuse and sock-spamming. Both Added. Thanks for reporting Slp1--Hu12 (talk) 20:00, 7 December 2009 (UTC)
- Thanks for the speedy work! --Slp1 (talk) 20:31, 7 December 2009 (UTC)
- Some More (older)
- Sunoforange (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- 74.212.221.218 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Hatrundo (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Added for th record--Hu12 (talk) 05:08, 8 December 2009 (UTC)
- Thanks for the speedy work! --Slp1 (talk) 20:31, 7 December 2009 (UTC)
winkstreaming.com
- link
- winkstreaming.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- accounts
- 190.241.146.212 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Worldcupsailing (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Jim22a948 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- 71.7.226.30 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 190.241.144.217 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 196.40.37.220 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- spam report
Edit warring to add link to the Content delivery network article. Attempts have been continuous for more than a year - and escalated to 3RR violations in September ([7]). I had originally reported this here in September, but removed it when the spammer finally posted to a talk page. Recently, the linkspamming has resumed, with no further attempt to discuss (the most recent IP has even resorted to vandalism to user pages of those who revert the spam [8]). --- Barek (talk • contribs) - 04:34, 8 December 2009 (UTC)
- Another (older)
- 71.7.226.96 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Articlespam
- Winkstreaming (edit | talk | history | protect | delete | links | watch | logs | views)
- Wink Streaming (edit | talk | history | protect | delete | links | watch | logs | views)
- Looks like page protection and warnings haven't stop it, Added.--Hu12 (talk) 04:54, 8 December 2009 (UTC)
paperspoint.net
- link
paperspoint.net: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- accounts
- 117.102.32.85 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 117.102.37.204 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 117.102.35.100 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 115.186.34.213 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Zrt1992 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
Paperspoint.net appears to hold pirate copies of exam papers, mark schemes etc (e.g. CHEMISTERY 5070 [sic] has Cambridge University copyright material), so fails the Linking to copyrighted works test.
The link is being added to exam articles, so far by four Worldcall Telecom dynamic IP addresses in Pakistan and a newly registered account (Zrt1992). In each case I've warned with spam1 or spam2. Examples: GCE Ordinary Level (diff 1, diff 2, diff 3), International General Certificate of Secondary Education (diff) and GCE Advanced Level (diff 1, diff 2, diff 3). - Pointillist (talk) 12:23, 9 December 2009 (UTC), updated 18:30, 9 December 2009 (UTC)
- Also the domain was created 18-Nov-2009 and all the papers I checked have "© UCLES 2009" (University of Cambridge Local Examinations Syndicate (UCLES)). No evidence of copyright permission or fair-use disclaimers on paperspoint.net, so per WP:COPYRIGHT (external Web site appears to be carrying work in violation of the creator's copyright), this is Done. Thanks for the report--Hu12 (talk) 20:17, 9 December 2009 (UTC)
10webhostingservices.com
- link
- 10webhostingservices.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- account
- 93.114.141.244 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
Repeated addition of link over past three months. Has continued despite warnings from multiple users and a block for repeatedly adding the link. --- Barek (talk • contribs) - 22:50, 13 December 2009 (UTC)
- 92.82.173.189 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- ro:Special:Contributions/93.114.141.244
- Re-blocked for a month, came off previous and continued. Old spam case (reference) Not done (for now)--Hu12 (talk) 16:01, 14 December 2009 (UTC)
www-src.nowpublic.com/culture/guy-fawkes-day-november-5-1605
Sorry if this isn't the right place to ask this but could someone check out this site? It was used in the Guy Fawkes Night article but Norton Safe Search flags it up as a malaware site. I've removed the link from the article but I'm concerned someone may put it back in. Richerman (talk) 00:12, 14 December 2009 (UTC)
- I don't see anything weird on the page you linked, and Google says they're clean. Probably a false positive! Zetawoof(ζ) 00:31, 14 December 2009 (UTC)
- OK thanks, I'll put it back in the article. Richerman (talk) 00:38, 14 December 2009 (UTC)
"mbtmvp.com", "nikecoo.com"
Links to mbtvp.com and nikecoo.com have been appearing on articles relating to footwear. Users have been replacing existing references and links with the business website.
- Links
- mbtmvp.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- nikecoo.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- Users
- 20091207chen (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Kitty20091208 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- + one other user who was blocked a while ago, but I can't recall the username.
-Reconsider! 03:33, 15 December 2009 (UTC)
- Other accounts
- Henryyexm (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Cinderellachen (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Chencinderella (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- 121.204.217.124 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Kitty20091201 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Cinderella20091209 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Spam Articles
- MBT shoes (edit | talk | history | protect | delete | links | watch | logs | views)
- MBTMVP (edit | talk | history | protect | delete | links | watch | logs | views)
- Famolare (edit | talk | history | protect | delete | links | watch | logs | views)
- MBT shoes-"the world's smallest gym." (edit | talk | history | protect | delete | links | watch | logs | views)
- 2010 Xiamen International Marathon and MBT shoes (edit | talk | history | protect | delete | links | watch | logs | views)
- MBT and Yoga (edit | talk | history | protect | delete | links | watch | logs | views)
- Messi wins Golden Ball award (edit | talk | history | protect | delete | links | watch | logs | views)
- Continuing
- 2009mbtmvp (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Sock spamming with a considerable ammount of link vandalism Added --Hu12 (talk) 04:46, 15 December 2009 (UTC)
justtollywood.com
- justtollywood.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- just-tollywood.blogspot.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- justanushka.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- nagachaitanya.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- akkineninagarjuna.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- pavan-kalyan.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- ntrjr.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- princemahesh.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- justtollywood.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
Use of frames for spamdexing. See WikiProject Spam report I'm sick of cleaning this up. MER-C 09:22, 15 December 2009 (UTC)
- Spammers
- Dannykingofdark (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Srchalla (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- 124.123.49.84 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Spammer replaced existing links.
- Samdrinkhappy (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- 122.169.165.39 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- 202.153.32.138 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Pretending to remove spam is never a sign of good faith.
- 124.123.49.29 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Spammer removed other links.
- Spammer replaced existing links.
- 124.123.241.200 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
- Spammer removed other links.
- Iam.spark55 (talk · contribs · deleted contribs · blacklist hits · AbuseLog · what links to user page · count · COIBot · Spamcheck · user page logs · x-wiki · status · Edit filter search · Google · StopForumSpam)
- Appears to be a genuine contributor, but shares above patterns including iframe redirect abuse.
- Citation spammer, see [9]
- Some older IP's not mentioned; See WikiProject Spam report
- 122.169.166.64 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
122.169.136.129 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
122.169.145.151 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
122.169.153.253 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
122.169.133.52 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
122.169.147.71 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
122.169.147.48 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
59.92.156.218 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot)
124.123.49.137 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • RDNS • tracert • robtex.com • StopForumSpam • Google • AboutUs • Project HoneyPot) - Added, thanks for the report--Hu12 (talk) 20:25, 15 December 2009 (UTC)
- ram-charan.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- megastarchiru.info: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
Some more frame redirect sites. MER-C 03:03, 16 December 2009 (UTC)
- Kissmenot (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- Hatemenot143 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- Touchmenot143 (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- Ramakrishnarama (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- KrishnaramaKrishna (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- Pingponghyd (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- Mamaisthebest (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- Ysrisgreat (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- Babuiswast (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- Venkatvsdon (talk • contribs • deleted contribs • blacklist hits • AbuseLog • what links to user page • COIBot • Spamcheck • count • block log • x-wiki • Edit filter search • WHOIS • robtex.com • Google)
- See also
- Done--Hu12 (talk) 04:22, 16 December 2009 (UTC)
Proposed removals
Use this section to request that a URL be unlisted. Please add new entries to the bottom of this section. You should show where the link can be useful and give arguments as to why it should be unlisted. Completed requests should be marked with {{Done}} or {{Notdone}} or other appropriate Indicator then archived. Once you have added a listing, please check back here from time to time to get the result of your request, or to answer any additional questions that administrators may have. We will not email you or otherwise notify you about your request, and if no answer is received to a question, the request will be presumed to be abandoned. |
cais-soas.com
This site (CAIS-SPAS) was apparently added a couple of years ago due to somewhat dubious reasons. It is an important and credible reference site for Iranian archeological sites as well as related publications.--Mehrshad123 (talk) 20:16, 18 November 2009 (UTC)
- Not dubious. This site was blocked at Meta after being identified as carrying images and content in violation of copyrights [10]. This site violates WP:Copyrights, Linking to copyrighted works. Declined --Hu12 (talk) 06:18, 19 November 2009 (UTC)
- The reference in question is a massive web site maintained by dozens of scholars from the University of London. There may be unresolved issues with a small number of the articles, (as is also the case with Wikipedia and many other large sites) but this is not a valid reason for blanket blocking of the entire site - especially one that is a major source of credible research and reference materials. In any case, the article that I wanted to include as a reference does not have any copyright issues. It can be found here: cais-soas.com/CAIS/Religions/iranian/anahita.htm I strongly suggest that the material form CAIS be treated on a case by case basis rather than blanket removal of the entire site.—Preceding .--Mehrshad123 (talk) 23:51, 20 November 2009 (UTC)
- Has the requested reference link been evaluated yet?--Mehrshad123 (talk) 22:05, 25 November 2009 (UTC)
- The reference in question is a massive web site maintained by dozens of scholars from the University of London. There may be unresolved issues with a small number of the articles, (as is also the case with Wikipedia and many other large sites) but this is not a valid reason for blanket blocking of the entire site - especially one that is a major source of credible research and reference materials. In any case, the article that I wanted to include as a reference does not have any copyright issues. It can be found here: cais-soas.com/CAIS/Religions/iranian/anahita.htm I strongly suggest that the material form CAIS be treated on a case by case basis rather than blanket removal of the entire site.—Preceding .--Mehrshad123 (talk) 23:51, 20 November 2009 (UTC)
- First, you may want to consider internet archives such as the Wayback Machine, which host unmodified archived copies of webpages taken at various points in time, or search google, which may have sites (such as http://flh.tmu.ac.ir/hoseini/prehist/200.htm) that would be of interest to you.
- In any case, cais-soas.com is known for carrying a works in violation of the creator's copyright. Linking to copyrighted works, Knowingly and intentionally directing others to a site that violates copyright has been considered a form of contributory infringement in the United States (Intellectual Reserve v. Utah Lighthouse Ministry [11]).[12]. Additionaly wikipedias servers are located in the United States, it's of no benefit, nor in wikipedias intrest to link this site. Closing as Not done.--Hu12 (talk) 07:52, 27 November 2009 (UTC)
associatedcontent.com
Here: Here: associatedcontent.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com Why is this site blocked? Argues spam. Please remove this site of the blacklist. Associated content is a site recognized. Thanks! (Mago266 (talk) 04:27, 25 November 2009 (UTC))
- Not a valid reason for D-Listing the domain. Having an article on wikipedia does not make for an exception when Significant long term history of abuse and major breaches of official Wikipedia policy. Aditionaly, associated content fails Wikipedias specific inclusion requirements of our Verifiability Policy and Reliable Source guidelines. If a specific link is needed as a citation, an etablished editor can request it on the whitelist on a case-by-case basis, where the url can be demonstrated as an appropriate source (in an appropriate context) when there are no other reasonable alternatives available. Not done--Hu12 (talk) 16:24, 25 November 2009 (UTC)
HU12, thanks for attention, but I need very much this source.(Mago266 (talk) 19:05, 25 November 2009 (UTC))
- Why? For what article, and what link are you proposing is a reliable source? Kuru talk 14:37, 29 November 2009 (UTC)
Art rock article, but no longer need because they are not considering the article. If I need, then I ask here. Thank's (Mago266 (talk) 02:57, 1 December 2009 (UTC))
- Stale Stifle (talk) 11:23, 2 December 2009 (UTC)
fiero.nl
For some reason this site is listed here and blocked as spam. I can see no reason why this site is blocked as it has a large archive of useful information on the Fiero... from maintenance information on stock engines to build-up threads for engine swaps and body modifications. The userbase is extremely knowledgeable and, for the most part, quite friendly. If you would, please remove this site from the blacklist so that others interested in learning more about this car can do so.
Thanks. 76.114.90.132 (talk) 06:33, 29 November 2009 (UTC)skuzzboomer
- Not done This appears to simply be yet another fan forum related to the car; those links are often removed from the Fiero article. There is nothing there that can be used as a reliable source. The site was added when it was repeatedly spammed in 2006, see here. At any rate, this is not blacklisted here on the english wikipedia, but on the meta spam list which stretches across all languages. You'll need to go there, but I would not expect action. Kuru talk 14:50, 29 November 2009 (UTC)
www.army-guide.com
- Okay then, here are my suggestions: Unblacklist pages about BTR-60, TAB-71, BTR-40, BMP-1, BMP-2, T-55, BRDM-1, T-62 and BRDM-2. All of them are beneficial to Wikipedia. Regards. - SuperTank17 (talk) 00:01, 4 December 2009 (UTC)
- It's been a week since I've given my suggestions for the parts of the website to be unblacklisted. And apparently people who took part in this discussion decided to ignore them. Well I didn't and that's why I'm repeating them: Unblacklist pages about BTR-60, TAB-71, BTR-40, BMP-1, BMP-2, T-55, BRDM-1, T-62 and BRDM-2. Also I've come up with a few new suggestions as well: TR-580, TR-85, TR-85M1 Bizon, BRM-1K, PT-76, T-72, BTR-70, BTR-80, BMD-1 and BMD-2 All of them are beneficial to Wikipedia. Regards. - SuperTank17 (talk) 16:18, 11 December 2009 (UTC)
- To request specific pages to whitelist, use WT:WHITELIST. That page allows specific links, while this page is only for the full domain only - which is likely why the request wasn't acted upon here.
- Also, at that page, be sure to provide enough information to allow whitelisting. Just saying which subject won't work. See other requests on that page for examples. --- Barek (talk • contribs) - 16:39, 11 December 2009 (UTC)
- Okay than I'll post my suggestions there while here I once again would like to say that I don't see why this site should be blacklisted. The sites on the blacklist either have malware on them or are being used for spamming which on Wikipedia would mean adding links or references to articles even though they don't have any useful information on them. www.army-guide.com doesn't fall into either category. There's no malware on the site and the information on it is very useful for writing articles about AFVs.
- The original reason for blacklisting it was because it was thought to be used for spamming. But I'm willing to bet that the "spamming" happened because the site hosted a lot of useful information about various AFVs (mostly about their operators as well as numbers in service). To this day you can find the remnants of this "spamming" in the lists of operators of various AFVs.
- By using the same reasoning you could say that I'm spamming the link to SIPRI Arms Tranfers Database. Regards. - SuperTank17 (talk) 16:19, 13 December 2009 (UTC)
- It's been a week since I've given my suggestions for the parts of the website to be unblacklisted. And apparently people who took part in this discussion decided to ignore them. Well I didn't and that's why I'm repeating them: Unblacklist pages about BTR-60, TAB-71, BTR-40, BMP-1, BMP-2, T-55, BRDM-1, T-62 and BRDM-2. Also I've come up with a few new suggestions as well: TR-580, TR-85, TR-85M1 Bizon, BRM-1K, PT-76, T-72, BTR-70, BTR-80, BMD-1 and BMD-2 All of them are beneficial to Wikipedia. Regards. - SuperTank17 (talk) 16:18, 11 December 2009 (UTC)
colombopro. com
This site is in the spam list for some reason. Actually doesn't know why this is in there.
I'm admin and I haven't engage with Wikipedia before.
I suggest this site to be included in the section of Google wave. because this site giving Google Wave Invites to people: colombopro[.]com/12/01/google-wave-invites/.
Site is even not containing any ads or materials that are inappropriate. I'm proposing you to remove the site from blacklist and enlist it in the section of Google Wave, because many people be able to get Google Wave Invites. Thank You.
—Preceding unsigned comment added by Wickumsiha (talk • contribs) 13:32, 2 December 2009 (UTC)
- Seems there was considerable amount of site related spamming, See report. It does appear you are the same as this previous account, which was involved in adding these links. This is your first edit on your new account and as the Admin you have a conflict of interest. Typically, we do not remove domains from the blacklist in response to site admins or those who where involved in spamming them. Instead, we de-blacklist sites when trusted, high-volume editors request the use of blacklisted links because of their encyclopedic value in support of our encyclopedia pages. If a specific link is needed as a citation, an etablished editor can request it on the whitelist on a case-by-case basis, where the url can be demonstrated as a source. Declined--Hu12 (talk) 18:51, 2 December 2009 (UTC)
Seems strange that we would have this site on the blacklist when we have an article about it. I've used it as a source in a few articles, so this must be a fairly recent addition. I noticed this when I was editing Boo Boo Stewart to re-include a source that was in an older revision [15], only to get a note from the filter. In any case, unless there's been misusage of the links somehow, I'd like to request a removal. GlassCobra 20:04, 2 December 2009 (UTC)
- For reference, here's the log related to the blacklisting of the url: MediaWiki talk:Spam-blacklist/archives/October 2009#Examiner.com.
- In the case of the specific link you're wanting to restore ... it appears to be a story that consolidates news from other sites/articles. To me, I think the source articles would better serve as reliable sources, as well as being more genuine as to the actual source of the material. --- Barek (talk • contribs) - 20:21, 2 December 2009 (UTC)
- Hmm, interesting. So when we add a link to the blacklist, do we not check to see if any articles link to it? GlassCobra 20:29, 2 December 2009 (UTC)
- Unfortunatly the Twilight Examiner site content you previously added (which also was previously spammed over multiple articles) appears to be scraped content from a reliabe source, Summit Entertainment, the film studio. Here is a reliable, verifiable link you might be interested in; http://www.summit-ent.com/news.php?news_id=122. Not done--Hu12 (talk) 06:16, 3 December 2009 (UTC)
- GlassCobra: we do, and we would look to remove them in due course. Stifle (talk) 09:49, 8 December 2009 (UTC)
- Hmm, interesting. So when we add a link to the blacklist, do we not check to see if any articles link to it? GlassCobra 20:29, 2 December 2009 (UTC)
Examiner.com.au
I have seen the block page a few times. It bothers me how poorly explained it is, and how it is not linked to a suitable explanation for the block. Editors can and do use webcitation and other backup services to avoid these restrictions, if it were properly explained we might be less inclined to route around this damage.
We could get into a whole other discussion about the quality and credibility of news sources, there are definitely some good articles on Examiner.com and blocking it doesn't seem like the right solution to improving article quality or encouraging editors to go to the real source.
Personally I try to avoid linking to sites that have content that is likely to disappear behind a paywall or have a noarchive/norobots policy since they are a severe detriment to easy WP:Verifiability and a cause of excessive link rot.
Despite those flaws in the blocklist there is a much bigger flaw, examiner.com.au a Tasmanian newspaper and a site not affiliated with the Examiner.com network has been blocked and is flagged by the blocklist. This block needs to be lifted as soon as possible and frankly the whole block on Examiner.com should be lifted if it cannot be done properly. -- Horkana (talk) 23:05, 5 December 2009 (UTC)
- This is indeed a mistake, the .com.au should not be blocked. I will whitelist it shortly.
- examiner.com, however, is not behind a paywall, there is not a noarchive or norobots policy, the problem is that examiner.com is basically a free web host, providing a pay-per-view service. That is why it is on there. --Dirk Beetstra T C 23:21, 5 December 2009 (UTC)
- I get that. Journals, blogs and sites with largely user published content (like IMDB) aren't considered good sources but are often used for lack of better sources.
- This large scale block of Examiner.com seems inappropriate, but if it were a warning encouraging editors to find a better source I'd be okay with it. My point was not that Examiner.com is Paywalled but that sites which are more harm and harder to spot than poorly written news sites trying to drive up traffic and they are something I'd really appreciate automated warnings to help me avoiding them. -- Horkana (talk) 23:31, 5 December 2009 (UTC)
- Theoretically, an edit filter in warn mode could be written to warn editors that they are including a site which is not a reliable source. Problem is that such a filter is likely to be very heavy on the servers. And again, it is not that they are badly written (there is good information on it), a bigger problem is the pay-per-view, which is a huge incentive to spam (it is a way for the man in the street to earn some money). The good faith but misplaced use of some (most?) of these documents as a reference is a lesser problem, and the good documents which need to be used are now a problem because of the spam.
- The warning that the spam filter gives is a text we can adapt. If you think that it can be improved, then we should try. It should however also not be a huge wall of text. --Dirk Beetstra T C 06:34, 6 December 2009 (UTC)
- I forgot, I already whitelisted examiner.com.au. --Dirk Beetstra T C 06:34, 6 December 2009 (UTC)
So I had a look at the error message and now that I'm not just being annoyed and blocked from making the edit I wanted to make I can see the error message is not so bad for what it is.
Unfortunately the error message is far too generic, it explains only that a site might be banned without giving any reason why[citation needed]. I'm supposed to take your word for it? In all other things I'm supposed to be skeptical and expect references and the people who have blocked this site have failed to provide an adequate relevant explanation in context. If this was an article it would be rejected so fast it would have skid marks.
I do sincerely appreciate Dirk Beetstra taking the time to explain why the site was banned but it is not something he should have to do, and it is not something I should have to come here and ask about to find out about either. When a site is blocked the reason for it being blocked and necessary context should be linked/referenced and directly included in the relevant context of the error message. Page deletions include a message to the deletion discussion and blacklisting should be just as transparent.
This will hopefully be my last comment on the issue, I much prefer to be adding and editing. -- Horkana (talk) 19:16, 9 December 2009 (UTC)
- The message can't know why a site is being blocked, that would be difficult to implement.
- The only thing indeed is take our word for it that it has been abused (or that there is an error, like here, which may be a too wide filter). I am afraid that the only two things that you can do are looking in the logs (the most efficient is to look for fragments of the domain name, as that is generally the thing that is blocked), or ask here. In principle the log should link to discussions why a site is banned so we don't have to explain, sometimes the log is a bit less useful, or discussions are less useful (some things get abused in such a bad way, that one editor manages to get things on there, and other methods are just ignored, though that does not happen too often. Sometimes there is a bit of WP:BEANS or protection of people involved as well). Maybe the block-message should link to the log, that at least may lead faster to block-reasons. --Dirk Beetstra T C 16:19, 14 December 2009 (UTC)
- Horkana there is a discussion regarding this at Wikipedia:Requests_for_comment/Reliability_of_sources_and_spam_blacklist. Gigs (talk) 22:33, 17 December 2009 (UTC)
UNONIC.com
I don't know why this is on the blacklist, but I am writing an article about it, so I am requesting it be removed. Thank you. — Preceding unsigned comment added by Borninlyoko (talk • contribs)
- Its a domain registrar for URL shortening/redirection sites. If an article is writen which passes inclusion criteria, perhaps we can reconsider this request for use in that article only. For now this is Declined--Hu12 (talk) 04:34, 3 December 2009 (UTC)
zunzun.com
www.wsraf.co.cc
This is the official website for a Royal Air Force section that is higly relevant to the article Wellingborough School CCF. Please whitelist the link. Regards. —Preceding unsigned comment added by 0o-JayParmar-o0 (talk • contribs) 11:38, 6 December 2009 (UTC)
- Not even close, the website does not exist. Declined. --Dirk Beetstra T C 14:19, 6 December 2009 (UTC)
- Probably meant ws-raf.co.cc, which is a redirect to http://ws-raf.66ghz.com/ (which is not blacklisted). Zetawoof(ζ) 07:48, 12 December 2009 (UTC)
- Then I would suggest to use the non-redirect per our external link guideline. --Dirk Beetstra T C 09:53, 12 December 2009 (UTC)
kitchen-gadgets.suite101.com
There is a useful page on this site which describes the types of Instant hot water dispenser available (the article originally described only one type); the page has useful factual information although it also displays advertisements. The specific http is kitchen-gadgets.suite101.com/article.cfm/home_electric_instant_hot_water_dispensers. I would suggest that this site, or at least this page, be unblocked, or alternatively that a page with equivalent content be found. I couldn't find either "gadgets" or "suite101" on the local or global spam blacklists, but that may be because I'm not familiar with spam filtering on Wikipedia. I have put a reference to the page (without leading "http://") in the article for now. Pol098 (talk) 07:24, 12 December 2009 (UTC)
- Suite101 and a number of similar sites are blacklisted at meta:Spam blacklist. In general, most such pages are not considered quality references, and higher-quality alternatives should be sought unless the page is written by a recognized expert (which is rare). Zetawoof(ζ) 07:56, 12 December 2009 (UTC)
- OK. I'd say it's not bad enough to blacklist; certainly the simple non-ad comparison of different types of instant water heater is useful, though ads are displayed. I don't claim any expertise on this subject in particular, so will let matters lie and the article develop as it may. I'd suggest a link to the meta:Spam blacklist be added to the "blacklisted page" message (unless it's there and I missed it). Thanks Pol098 (talk) 09:25, 12 December 2009 (UTC)
- Suite101.com is bad enough to blacklist globally, most of the information on the site is unreliable, and has been spammed widely by many editors to many wikis (often by editors with a conflict of interest). However, there are single documents left and right which are of interest, and I would like to ask you to request specific whitelisting on MediaWiki_talk:Spam-whitelist. Hence, Declined and Defer to Whitelist. --Dirk Beetstra T C 09:52, 12 December 2009 (UTC)
- Thanks, have done as you suggest: MediaWiki_talk:Spam-whitelist#Request_to_whitelist_a_single_page_of_kitchen-gadgets.suite101.com. Pol098 (talk) 01:37, 13 December 2009 (UTC)
grangehotels.com
Appears to be a legit hotel group, and owns a five star hotel, Grange City Hotel which would normally have a link to the hotel website, e.g. to www.grangehotels.com/hotels-london/grange-city-hotel/grange-city-hotel.aspx?int=1
I don't know why it's on the blacklist. --Tagishsimon (talk) 23:16, 14 December 2009 (UTC)
- Here's your reason. Stifle (talk) 10:47, 15 December 2009 (UTC)
- Thanks Stifle. I vaguely understand from that that some SEO creep has in the past spammed the link. Where does that leave us now that we have an article about the hotel, which would like a link to the hotel website? (I'm not at all familiar with this area of wikipedia, and, come to that, don't even care much about the hotel article. If someone could give me a clue about a route forward, that would be great.) --Tagishsimon (talk) 13:49, 15 December 2009 (UTC)
merchantcashadvances.org
This website provides merchants with information regarding merchant cash advances. It discusses the entire lending process, and what merchants should be looking for when taking out a merchant cash advance. Many merchants don't know about this relatively new form of funding and this site provides them with answers to many questions they may have. Why is this site on the black list? —Preceding unsigned comment added by Merchantcashadvances (talk • contribs) 02:31, 15 December 2009 (UTC)
- merchantcashadvances.org: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
- Fails WP:EL additionaly Wikipedia is NOT a "vehicle for advertising". Declined--Hu12 (talk) 04:21, 15 December 2009 (UTC)
Troubleshooting and problems
This section is to report problems with the blacklist. Old entries are archived |
Logging / COIBot Instr
Blacklist logging
Full instructions for admins
Quick reference
For Spam reports or requests originating from this page, use template {{/request|0#section_name}}
{{/request|213416274#Section_name}}
- Insert the oldid 213416274 a hash "#" and the Section_name (Underscoring_spaces_where_applicable):
- Use within the entry log here.
For Spam reports or requests originating from Wikipedia_talk:WikiProject_Spam use template {{WPSPAM|0#section_name}}
{{WPSPAM|182725895#Section_name}}
- Insert the oldid 182725895 a hash "#" and the Section_name (Underscoring_spaces_where_applicable):
- Use within the entry log here.
- Note: If you do not log your entries, it may be removed if someone appeals the entry and no valid reasons can be found.
Addition to the COIBot reports
The lower list in the COIBot reports now have after each link four numbers between brackets (e.g. "www.example.com (0, 0, 0, 0)"):
- first number, how many links did this user add (is the same after each link)
- second number, how many times did this link get added to wikipedia (for as far as the linkwatcher database goes back)
- third number, how many times did this user add this link
- fourth number, to how many different wikipedia did this user add this link.
If the third number or the fourth number are high with respect to the first or the second, then that means that the user has at least a preference for using that link. Be careful with other statistics from these numbers (e.g. good user who adds a lot of links). If there are more statistics that would be useful, please notify me, and I will have a look if I can get the info out of the database and report it. This data is available in real-time on IRC.
Poking COIBot
When adding {{LinkSummary}}, {{UserSummary}} and/or {{IPSummary}} templates to WT:WPSPAM, WT:SBL, WT:SWL and User:COIBot/Poke (the latter for privileged editors) COIBot will generate linkreports for the domains, and userreports for users and IPs.
Discussion
This section is for other discussions involving the blacklist. Old entries are archived |
examiner.com redux
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
- examiner.com: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • Spamcheck • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
It was proposed for removal above and then withdrawn, but I'd like to reopen it. I agree that it's not a particularly reliable source. If someone used it to back up a dubious fact or to establish notability, I'd challenge them on it. But sources of questionable reliability are not blanket banned using technical means; there's no community consensus for that (that I'm aware of). Our reliable source guidelines say that articles should primarily rely on reliable sources, but as with all our guidelines, it's subject to discretion and exception. I believe that using the spam blacklist in this way exceeds the scope of what it's supposed to be for, and that this case is gray enough that it shouldn't be listed. As well, I don't believe that examiner.com has any unique conflicts of interest in terms of the author's compensation... I can't imagine many web sites where a goal isn't to drive traffic. Anyway in summary, I agree that it's "blog like"... I agree that it should be used with caution, but I disagree that it should be blanket banned using the blunt instrument of the spamlist. Gigs (talk) 00:15, 20 November 2009 (UTC)
- I poked around to see if there was a standing community consensus on this, I didn't find one, but I did find this arbcom finding that says specifically that "Blacklisting is not to be used to enforce content decisions." Gigs (talk) 02:49, 20 November 2009 (UTC)
- Well, Gigs, that was quite a blanket statement, which I don't think is a reason to de-blacklist (basically, all blacklisted items are content decisions saying 'we don't want this content here'; and you seem to assume that it was blacklisted because we want to keep out the content, maybe it was just plainly spammed?)
- Regarding the examiner.com, there are several discussions stating it is not a reliable source: Wikipedia:Reliable_sources/Noticeboard/Archive_35#examiner.com_.3D_paid_blogging.2C_no_editorial_oversight, Wikipedia:Reliable_sources/Noticeboard/Archive_38#Request_to_reopen_discussion_on_examiner.comWikipedia:Reliable_sources/Noticeboard/Archive_39#Examiner.com, Wikipedia_talk:Reliable_sources/archive_21#Examiner, Wikipedia_talk:Reliable_sources/archive_21#Examiner.com. Basically, no editorial oversight, self published sources
- Regarding spamming, I found at least one editor who was spamming their own work, Special:Contributions/Thetwilightexaminer, unfortunately too many records, I may be able to examine more of this. Maybe the MediaWiki talk:Spam-whitelist can be of assistance here? --Dirk Beetstra T C 15:39, 20 November 2009 (UTC)
- If it were spammed in a widespread manner that something lesser like XLinkBot can't handle then that's fine. But the main reason given for its initial and continued listing seems to be that it's not a particularly reliable source, which is something I don't agree with and I don't believe there's community consensus for. The reliability of a source should have no bearing whatsoever on a blacklist listing. The same goes with the discussions above regarding ehow.com, associated content, etc. Yes, I could probably get the specific link I wanted whitelisted, but I guess I'm concerned about the larger issue here of black and white listing decisions being driven by WP:RS instead of actual spam concerns. Maybe we should transplant this to the discussion section below, and we can hold this request pending the outcome of that larger discussion? Gigs (talk) 20:25, 20 November 2009 (UTC)
- As shown above there infact has been spamming and abuse, additionaly community consensus is rooted in Wikipedia policies of whats acceptable for inclusion, and in this case of Examiner.com links;
- Have no editorial oversight (see WP:RS) and articles are essentially self-published
- Offers its authors financial incentives to increase page views
- ""Examiners" are paid a very competitive rate based on standard Internet variables including page views, unique visitors, session length, and advertising performance. "
- Fails Wikipedia's core content policies:
- As shown by community discussion and consensus, the reliability of a source has a determining factor on what is or is not removed or whitelisted. On that basis this request is Declined. However, If a specific link is needed as a citation, as suggested, it can be requested on the MediaWiki talk:Spam-whitelist on a case-by-case basis, where the url can be demonstrated as a reliable source. The guideline that most directly relates to whether a given source is reliable is Reliable sources. The policies that most directly relate to this are: Verifiability and No original research. For questions and discussions debating the reliability of sources, the appropriate place for discussion is at the Wikipedia:Reliable_sources/Noticeboard. thanks. --Hu12 (talk) 21:59, 20 November 2009 (UTC)
- moved --Hu12 (talk) 23:30, 20 November 2009 (UTC)
- Where is the community discussion and consensus regarding using WP:RS to determine what to list on the spam blacklist? I couldn't find it. Quite the opposite, I found several comments against using it in that way, including that arbcom finding. Gigs (talk) 22:06, 21 November 2009 (UTC)
- moved --Hu12 (talk) 23:30, 20 November 2009 (UTC)
- As shown above there infact has been spamming and abuse, additionaly community consensus is rooted in Wikipedia policies of whats acceptable for inclusion, and in this case of Examiner.com links;
- If it were spammed in a widespread manner that something lesser like XLinkBot can't handle then that's fine. But the main reason given for its initial and continued listing seems to be that it's not a particularly reliable source, which is something I don't agree with and I don't believe there's community consensus for. The reliability of a source should have no bearing whatsoever on a blacklist listing. The same goes with the discussions above regarding ehow.com, associated content, etc. Yes, I could probably get the specific link I wanted whitelisted, but I guess I'm concerned about the larger issue here of black and white listing decisions being driven by WP:RS instead of actual spam concerns. Maybe we should transplant this to the discussion section below, and we can hold this request pending the outcome of that larger discussion? Gigs (talk) 20:25, 20 November 2009 (UTC)
- Gigs, the fact that "Examiners" are paid a very competitive rate based on standard Internet variables including page views, unique visitors, session length, and advertising performance. " is a HUGE spam incentive, and many, even SINGLE additions are basically spam, not edits to improve the Wikipedia. The existence of that incentive also results in some cases in violation of WP:ELNO #2, and moreover it fails WP:RS where most of the documents simply can NOT be used as a reference. Simply, in by far the most cases this site should not be linked to, it has been abused, and hence it is blacklisted with the clear possibility to whitelist individual pages on this site.
- You would have a case if it was solely blacklisted for violation of WP:RS, but that is not the case. --Dirk Beetstra T C 09:12, 30 November 2009 (UTC)
- Every site has employees or authors that, if they were to add links to said site, it would represent a conflict of interest (and probably should be reverted). Most sites make money through traffic. If we block sites on the grounds that they make money from traffic, then we'll need to block most of the Internet. As for WP:ELNO #2, obviously it is not examiner's goal to mislead people through incorrect information. That clause seems directed more at hoax sites. And again, I don't see why the editorial decision over whether a site is a reliable source for a certain fact or not should be dictated through the administrative means of a black list. I don't see why the reliability or lack thereof should even be a factor here at all. I doubt many editors are aware that the black list is being used in this way. It may be useful to open an RFC to see where the consensus is. Gigs (talk) 17:25, 1 December 2009 (UTC)
- Unfortunately, I didn't notice this discussion here before making my request for an unlisting yesterday; however, it seems to me that Gigs in correct in saying that this is at least worth some wider discussion, perhaps at WP:RS/N. GlassCobra 14:19, 3 December 2009 (UTC)
Before we take this to a wider audience, I'd like to at least get some more or less neutral questions agreed upon. To me, the main questions are:
- Should the reliability of a source be a determining factor on what is blacklisted or whitelisted?
- Should we blacklist sites based on their business model of paying authors based on ad revenue?
In taking this to the community, I would want to remind people that we do have XLinkBot as well for doing reversible reverting of possibly ill-advised links that can be undone by established editors, so that people are aware that we do have tools other than the blacklist for this sort of thing. Gigs (talk) 14:53, 3 December 2009 (UTC)
- I am sorry Gigs, but I am afraid that you look at it from the wrong end.
- a) reliability can be a secondary factor, until now I have not seen any which have been solely decided on 'not being a reliable source'.
- b) No, we don't do that, and that is also not what I said, nor what I believe is done here.
- Of course, all sites have people working for them, who have a conflict of interest. They are not disallowed to add their site, as long as the information is to the point, reliable, etc. etc.
- People who work for, say, the American Chemical Society can link to documents on their site, that would indeed give some revenue to the organisation, and if that would be the incentive, then we would revert. We don't blacklist, as it is a reliable source, it is needed.
- People who make their own website on a server like the old geocities don't get any money for people who visit their site. They still have a conflict of interest if they add a link to their site to Wikipedia. Geocities makes (made) money from that, as all those free web hosts do. If the links were added by a person who works for Geocities, then scenario 1 is in place. Sites like these tend to fail WP:RS. Do we blacklist, generally not.
- Now we have sites like examiner.com. You can write your own website on there, just like on Geocities, but it has as an added bonus, that if you then link to your page, and people follow that link, that you actually get paid for that. The data is, generally again, not a WP:RS, one has a conflict of interest when adding a link to an own document. Still not really dissimilar from either 1 or 2 .. do we blacklist immediately, no.
- But, if documents on sites like 3 are more often added in an inappropriate manner (and I already gave an example of one spammer, I don't recall if I blacklisted or someone else, but I did not review the case in detail now), then an evaluation can be made, and these pay per view sites are then earlier eligible than geocities. Note that geocities has been on XLinkBot's revertlist for a long, long time, and that many, many additions of said site were inappropriate as they are (generally) unsuitable external links (and probably also generally unsuitable as references).
- So basically, this site is not blacklisted on grounds that it makes money from traffic (all do), this site is not blacklisted on grounds that it is not a reliable source (basically, then we should shut down linking to all free web hosts, social networking sites, blogs, image and video sharing sites, etc. etc.), but it is, in beginning, blacklisted because it was abused, and being a pay-per-view site makes the incentive for editors who have a page on such a site to link inappropriately bigger. Some of the early and bigger examples of such pay-per-view sites have been massively abused/spammed just for that reason (e.g. associatedcontent.com).
- Does this mean that we should not use this site, no. If you need documents which are not replaceable, and which are a unique/reliable source, then that document could/should be whitelisted, and if you make such a request with a bit of reasoning, it will be handled swiftly. I am afraid that removing this site from the blacklist will result in a new influx of such spammy additions, while in the end there will not be many which are really to improve. I am sure you are here for one or two specific documents, and there may have been a couple more requests, but sites like associatedcontent.com, which are here already for a long time, only get a request for whitelisting every now and then, while the spamming before blacklisting was severe. I hope this explains. --Dirk Beetstra T C 15:15, 3 December 2009 (UTC) (adapted, I meant associatedcontent.com --Dirk Beetstra T C 15:19, 3 December 2009 (UTC))
- I am not sure what to say. What you have said here directly contradicts what Hu12 has said and also what is being practiced on this page and on the whitelist page. Hu12 said that "As shown by community discussion and consensus, the reliability of a source has a determining factor on what is or is not removed or whitelisted." I believe this to be false, I have found no such community consensus for using the reliability of a source as a determining factor. You say it's a "secondary factor", and yet I see many decisions here and on the whitelist page being primarily based on a WP:RS rationale for not removing a blacklist or adding a whitelist entry. I have gone back over the last couple months of archives, and here are all decisions that have been primarily based on the site being unlikely to meet WP:RS:
- MediaWiki_talk:Spam-blacklist/archives/November_2009#ehow.com - Similar to examiner
- MediaWiki_talk:Spam-blacklist/archives/October_2009#Ning.com - Social Networking hosting site, geocities style, blanket blacklist of every social network hosted there was added because just one subdomain was being spammed.
- MediaWiki_talk:Spam-blacklist/archives/October_2009#atbriders.com - Forum site
- MediaWiki_talk:Spam-blacklist/archives/October_2009#Examiner.com - Of course
- I don't think there is community consensus for this kind of administrative and technically enforced decision about the suitability of sites as reliable sources. You suggest that I could get a link whitelisted; I'm sure I can. But the problem here isn't the link I want to use, it's the systematic problem that I discovered when I tried to use the link. I would rather get that corrected than get the band-aid of a whitelist entry. As you point out, there probably is consensus for adding these kinds of sites to XLinkBot, since that's been done for years, but that's not what's happening here. They are being hardblocked with the blacklist instead of XLinkBot. Gigs (talk) 20:47, 3 December 2009 (UTC)
- There is a distinction I think you're missing. Sites aren't placed on the blacklist because they aren't reliable, they're placed on the blacklist because someone was spamming them. Fast forward to when somebody wants to whitelist (or unblacklist) a link to use in an article. At that point it's worth considering if using the site as the requester suggests would meet with policy - if it doesn't there's no good reason to grant that particular request.
- If the reliability of the source were the primary criterion, unreliable sites would be proactively blacklisted before anyone came along to spam them, but that doesn't happen. - MrOllie (talk) 21:21, 3 December 2009 (UTC)
- I am not sure what to say. What you have said here directly contradicts what Hu12 has said and also what is being practiced on this page and on the whitelist page. Hu12 said that "As shown by community discussion and consensus, the reliability of a source has a determining factor on what is or is not removed or whitelisted." I believe this to be false, I have found no such community consensus for using the reliability of a source as a determining factor. You say it's a "secondary factor", and yet I see many decisions here and on the whitelist page being primarily based on a WP:RS rationale for not removing a blacklist or adding a whitelist entry. I have gone back over the last couple months of archives, and here are all decisions that have been primarily based on the site being unlikely to meet WP:RS:
- Gigs, sites are blacklisted because of abuse. I think you've got the cart before the horse. Guidelines such as WP:RS inherantly reflect community consensus, because they are community created and accepted standards.
- The reliability of Examiner.com as a source has been determined by the Wikipedia:Reliable sources/Noticeboard, as not reliable;
- The reliability of Examiner.com as a source has been determined on Wikipedia_talk:Reliable_sources, as not reliable;
- So yes, "the reliability of a source has a determining factor on what is or is not removed or whitelisted". Understand that when considering a removal, One must also consider the probability of reoccuring/future spamming and abuse. The fact that; →"Examiners" are paid a very competitive rate based on standard Internet variables including page views, unique visitors, session length, and advertising performance. ←, works against Examiner.com. The potential for continued spamming is a likely problem, as the incentive to do so is extremely high. Unfortunatly we have learned this in past pay-per-spam type cases.--Hu12 (talk) 00:13, 4 December 2009 (UTC)
- Gigs, sites are blacklisted because of abuse. I think you've got the cart before the horse. Guidelines such as WP:RS inherantly reflect community consensus, because they are community created and accepted standards.
- In addition to this, XLinkBot was not set up (until just a couple of days ago, and it has not been tested yet) to revert references. And for associatedcontent, ehow, and examiner, it is not just an unreliable source, you seem to 'ignore' the fact of the pay-per-view incentive. You say for ning.com that it was blacklisted just one subdomain was spammed, did you investigate all the others, and what the incentive there is (is ning.com also a pay-per-view site?)? It is fine to say, that sites should not be blacklisted because they are deemed not to be a reliable source, and if you put an request for comment on that fact only I am sure that it will not pass (I am with you there, though I can see the benefits of it, it has huge drawbacks, we do link to unreliable sources for other reasons, and sometimes it is a matter of what conclusion you want to draw whether it is unreliable or not). But these are not just sites which are containing a lot of unreliable material, and I don't think that that request for comment (on WP:RS basis only) will give results which are portable onto these sites, one would then need a second for pay-per-view sites which are also unreliable sources.
- Let me give an example, some time ago we had an editor who begged us to leave his referral link for a week, because they needed the money. The lengths this editor went through to get their referrals linked, there are a handful of links on the blacklist These sites give essentially the same problem. I can write a story on these sites about some mainstream subject, and link it from Wikipedia, so I earn some extra money. My story can be completely crap .. it will work. This is not just a site where the information is unreliable, where other editors are adding links to the unreliable information in good faith, this is not just a site where some information is fine, and some is not, no, this is a site where it pays to write absolute crap and link it from as many places as possible in order to get you some extra money. You used the argument that most sites get money from somewhere, yes, true, but I don't think that many websites will go through the effort of just filling pages with information and linking them throughout the web to get people on their sites (well, you see it in the Sildenafil corner of the web ..).
- And as I said, most of them were abused in one form or another, I recall that I, when I examined one of these sites some time ago, there were quite some single or not-so-wide-scale additions, which were not really improving the encyclopedia we are writing here, all where the username on both sides was the same or very similar. This does not necessary go by big numbers .. yes, you are right, they contain good stuff, but I am not sure it is worth the effort. Yes, they can go onto XLinkBot (I think associatedcontent.com was there for some time), but this incentive of being payed for linking defies XLinkBot (especially if you put it into reference; and the incentive just makes people revert XLinkBot). Spamming != vandalism. It generally does not pay to vandalise, while it seldomly does not pay to spam .. please do not ignore that pay-per-view incentive on these generally unreliable sources. --Dirk Beetstra T C 22:58, 3 December 2009 (UTC)
- I have been watching this for a while and would agree with the status quo (whitelisting on request only). There is far too much potential for misuse. I would most like to do it by way of an edit filter (which could permit editors with over a certain level of contributions to add the links on the assumption that they're reliable), but that doesn't support the fine granularity that we need. Stifle (talk) 09:02, 4 December 2009 (UTC)
- Regarding ning.com, the blacklist is now blocking thousands of sites on the grounds that just one of them was spammed. It is like IP blocking all of Russia because we had a single Russian vandal! This sort of prior restraint goes against the foundation of Wikipedia, and every wiki in general. It strikes at WP:BOLD and turns it into WP:ASKFIRST. Gigs (talk) 21:38, 4 December 2009 (UTC)
- I can't find a log entry for ning.com, I see that Hu12 blacklisted a subdomain, but I can't find who added the whole domain. This one seems a bit odd. Is there a valid reason why the whole domain is blacklisted? --Dirk Beetstra T C 23:04, 4 December 2009 (UTC)
- Fist Russia is not blocked. Secondly the domain ning.com is not blocked. One subdomain (addisethio.ning.com) is blocked as was requested. Thirdly, its an Ethiopian social network sub-site in which multiple "sub-group" links were spammed, including multiple instances of link vandalism [17][18][19]. I'm a bit confused by what gigs posted. Even the IP isnt russian.--Hu12 (talk) 06:37, 5 December 2009 (UTC)
- Oh, my mistake (I did not look carefully), but still. There is a rule '\ning\.com\b' (which IIRC is not a correct regex, \n does not exist. We can still link to http://beetstra.ning.com, http://beetstra.ing.com (just testing) I think. That regex is, again if I see it correctly, not properly logged, and if it is really not working, it should go.
- Gigs, if you see only the proof presented of one subdomain, then that is not a reason to think that it are not multiple subdomains. Sometimes it is just one particularly bad example (but a look at e.g. a User:COIBot-report shows that the rest of the site was not used in a particularly helpful way either), sometimes an evaluation is made on the major site. Please ask whether there is enough evidence, don't say 'the blacklisting was not done on enough evidence'. User:Japanhero is giving us a hard time, using multiple sockpuppets to add links where the subdomain on the free web server is changing upon blacklisting of every other one. We are running behind the facts, and there is hardly anything we can do. Sometimes then we have to make the evaluation, 'what if we blacklist the whole domain, do we lose much?'. Yes, it becomes a bit difficult to add the good stuff (one has to go through whitelisting), but, well, the man in the street does not see how much effort it sometimes takes to keep spammers out. Again, spammers earn money from spamming! It is not just school boys and girls adding bad words to pages which you can block. They go through great lengths. But I presume that 'the editors' don't like the 'administrative decision' that Wikipedia is not supposed to end in a site where one can promote themselves or a site which can be used to improve their own revenues. The blacklist is a last resort, surely, but believe us, you don't want us to fully protect ALL drug pages (Sildenafil, etc.; yes, it takes 4 days and 10 innocent edits to become autoconfirmed, socks are easily made, so you can still spam your links to semiprotected pages, so semi is NOT enough), we can't block the whole of Russia (unfortunately some countries have a high influx of certain forms of spam, and some ranges easily change IP, and accounts are easily made), XLinkBot only reverts, and is easily reverted (and XLinkBot does not revert again .. it notifies editors, and those who follow XLinkBot will see when it is reverted; but it does not STOP spammers, it slows them only down and makes them visible), and ning.com/webs.com/&c. subdomains are easily made. Spammers know the holes, and they will use them. IT PAYS, (AND/OR) IT IS THEIR JOB! So, Gigs, are you going to help us checking and removing all the crap that will come from examiner, just because some of the documents are suitable and therefore the whole domain can't be blacklisted? Again, this site is not blacklisted solely because it is not a reliable source, it is blacklisted because it is not a reliable source ánd a pay-per-spam site. Thát is the problem. Blacklisting a non-reliable source solely on the fact that it is not a non-reliable source is never done, there is always more, either it has been abused; used e.g. to systematically 'source' wikipedia documents in a way which is neglecting our core policies, or plainly spammed, or to gain money, or even just to attract people to the site.
- To all, please stop suggesting that we 'blacklist maintainers' (well, all you admins are blacklist maintainers) make it impossible for editors to work, to reference material or to add helpful external links, we may make mistakes, but blacklisting is seldomly done without proof, and once a site starts being spammed, then you know more is going to follow. Sites like Associated content, examiner.com, ehow.com give a great incentive, and don't even think that blacklisting one subdomain will stop the spam. My suggestion below to block such sites on sight, or even pre-emptive is harsh and hard .. believe me, it is not worth the cleaning up. --Dirk Beetstra T C 08:36, 5 December 2009 (UTC)
Pre-emptive blacklisting of Pay-per-view sites
I actually would like to turn this discussion around. We have until now only few cases of link-types which go onto this blacklist without discussion, and sometimes even without abuse, or even without any additions to Wikipedia (redirect sites like tinyurl.com are one, sites which are installing malicious software another, referral links are sometimes also blacklisted very fast without widescale abuse). I'd like to hear some community input on what to do with these 'free web hosts which offer money to the creator of documents on a pay-per-view basis' (like associatedcontent, ehow, examiner). IMHO, such sites should not be linked to, except after careful examination of specific documents and whitelisting of such documents on a need-to-link-to basis, and that such sites can actually be blacklisted to avoid abuse. Thoughts? --Dirk Beetstra T C 10:13, 4 December 2009 (UTC)
- Community practice isn't really consistent on this. On the one hand we have those three blacklisted, on the other another such site is not blacklisted and is still extensively linked on Wikipedia (About.com). - MrOllie (talk) 13:08, 4 December 2009 (UTC)
- Hmm, About.com states "Contributing Writers go through a training program, in which they submit writing samples to an About.com editor. After the editor's suggestions have been incorporated, the articles will be re-evaluated and a hiring decision made. You can read more about the training process for Contributing Writers here.". You can then indeed earn money, but it's setup is different from the other three I mention here, where you can just join and write. --Dirk Beetstra T C 13:26, 4 December 2009 (UTC)
- Looking further, examiner.com does a check ("Once you click the submit button on your application, it goes to a member of the content channel team for which you have applied (Business & Finance, Sports, Pets, etc). They will assess writing style, voice and tone, knowledge within the topic, experience, etc., as well as technical factors such as grammar, spelling and punctuation. Every application is reviewed, though sometimes it can take up to two weeks due to the volume of applicants." and "Authorization to conduct criminal history background check and identity verification. We do not check credit history or contact former employers."), but not a training (like about.com: "Contributing Writers go through a training program, in which they submit writing samples to an About.com editor. After the editor's suggestions have been incorporated, the articles will be re-evaluated and a hiring decision made."). Associated content even states "The sign-up process is easy, and you can start submitting content immediately.", similarly, Ehow.com states "Just sign in to your eHow account, and from your profile page, click on the "Write Now" button. From there eHow's publishing wizard will guide you through the publishing steps.". --Dirk Beetstra T C 13:35, 4 December 2009 (UTC)
- Examiner does seem to go farther than the others mentioned, with the claim to assess; "writing style, voice and tone, knowledge within the topic, experience, etc., as well as technical factors such as grammar, spelling and punctuation." in the examinerfaq. Unfortunatly it (as with the others) falls short of editorial fact checking. This seems verified in their actual Terms of Use, Under section 8. User-Submitted Content... states "Since Examiner.com does not control the User Content posted on the Site, it cannot and does not warrant and/or guarantee the truthfulness, integrity, suitability, or quality of that User Content...". That seems to the nature of social media self-publishing. The policy on sourcing in this case; ”Self-published sources (online and paper)” (see Wikipedia:Verifiability#cite_note-4).--Hu12 (talk) 20:03, 4 December 2009 (UTC)
- The suitability of a link or a reference is not an administrative decision, it's an editorial one that is considered on a case by case basis, generally on talk pages and through our normal editing processes. I object to this entire discussion as invalid on the grounds that it attempts to usurp editorial discretion and put it in the hands of a small group of blacklist maintainers. If you hadn't noticed, this is the thrust to all my objections. Gigs (talk) 21:35, 4 December 2009 (UTC)
- Examiner does seem to go farther than the others mentioned, with the claim to assess; "writing style, voice and tone, knowledge within the topic, experience, etc., as well as technical factors such as grammar, spelling and punctuation." in the examinerfaq. Unfortunatly it (as with the others) falls short of editorial fact checking. This seems verified in their actual Terms of Use, Under section 8. User-Submitted Content... states "Since Examiner.com does not control the User Content posted on the Site, it cannot and does not warrant and/or guarantee the truthfulness, integrity, suitability, or quality of that User Content...". That seems to the nature of social media self-publishing. The policy on sourcing in this case; ”Self-published sources (online and paper)” (see Wikipedia:Verifiability#cite_note-4).--Hu12 (talk) 20:03, 4 December 2009 (UTC)
- heh, indeed! Editors have decided what WP:EL, WP:RS, WP:SPAM look like, and editors have also decided that redirect sites are not to be used on Wikipedia, that commercial spam can result in blacklisting, and editors can also decide that pay-per-view sites are generally not to be used, and can be pre-emptively blacklisted, and that then on a case-by-case basis some documents can be whitelisted. Blacklisting a site is not an administrative decision, it is an administrative action, backed up by our (editor supported) policies and guidelines. Now we have never discussed whether such sites should be blacklisted, but we have already decided that certain content shall not be linked to (heh, that is why we have this blacklist). I am here now asking our editors, whether administrators can perform the action of blacklisting pay-per-view sites just by nature. It may be that the editors disagree with that proposal (believe me, I know the pro's and con's), but there is no administrative decision here. --Dirk Beetstra T C 22:56, 4 December 2009 (UTC)
- If you truely want community consensus on this, then we need to expand the solicitation past just this page. Since this issue has community-wide implications, we should advertise it community wide. I'm not sure how to go about this yet, but it looks like the discussion is narrowing down into a few questions. Gigs (talk) 19:36, 6 December 2009 (UTC)
- I mainly am looking for thoughts for now. If we really want to push it to pre-emptive blacklisting (I am happy enough with the 'as soon as a pay-per-view sites are being abused, the domain goes on the blacklist'), then we should indeed move on to write this into policy somewhere. But its a bit too early for that, I think that there is more consensus for the current case of 'abuse => blacklist'. --Dirk Beetstra T C 21:34, 6 December 2009 (UTC)
- If you truely want community consensus on this, then we need to expand the solicitation past just this page. Since this issue has community-wide implications, we should advertise it community wide. I'm not sure how to go about this yet, but it looks like the discussion is narrowing down into a few questions. Gigs (talk) 19:36, 6 December 2009 (UTC)
- I do not know if pre-emptive blacklisting of pay-per-view sites is warranted, but once such sites have started being spammed here (particularly when even a small number of external links or REFSPAM is added by SPA accounts), I support blacklisting the site. That is, block the site early; do not wait to reach that common-sense conclusion after a lot of effort reverting spam and conducting a pointless debate (would people really get multiple Wikipedia accounts just to add links in the hope of earning money? – yes). It is impractical to debate the pros and cons of every link to a large site where people have an incentive to spam (such debate would often have to cover many hundreds of links). What we know is that it pays people to spam links to examiner.com, it has been spammed, and it is blacklisted – that is as it should be. Johnuniq (talk) 07:18, 5 December 2009 (UTC)
RfC ?
See: Wikipedia:Rfc/Reliablity of sources and spam blacklist for further discussion. Gigs (talk) 15:36, 10 December 2009 (UTC)
Here's my attempt at a neutral summary: User:Gigs/blacklistRfC. It's not live yet so don't start commenting there, but I'd appreciate editing of the "Arguments" section, especially if anyone thinks I have mischaracterized a position. Gigs (talk) 20:28, 6 December 2009 (UTC)
- Take care, it looks like you are mixing up things, and though neutrality is fine, it does not characterise the positions properly. Blacklist reasons are not the same as de-blacklist reasons or whitelist reasons, and the criteria are different.
- Blacklisting is because of abuse, of course, as soon as the blacklisting is in place, there is no abuse anymore.
- De-blacklisting then questions whether the abuse will continue, and whether the site will be of use anyway (as a whole!). If there is a significant risk that the site will be abused again, then de-blacklisting is not a good solution. It can NOT be replaced with XLinkBot, or monitoring. Again, JapanHero is making it not easy, how many subdomains and sock accounts are needed?
- Whitelist requests often get the question back 'is it reliable', you in the RFC now state that that is an administrative decision , no it is a legitimate question. The site does not have to be whitelisted to be discussed on its merits. The onus of the proof is on the person wanting to include it, that proof can be provided before whitelisting is performed. Or do you want to blindly whitelist (or de-blacklist), and see the editor actually abuse it, and 10 reverts and a block later it gets de-whitelisted again? There are here regular requests from the spammer to have their domain de-blacklisted .. do you really believe that those are requests so the editor can discuss, or go into a BRD cycle? As Johnuniq says below, 'would people really get multiple Wikipedia accounts just to add links in the hope of earning money?' ... --Dirk Beetstra T C 23:25, 6 December 2009 (UTC)
- I have also responded there, given comments and expanded it. --Dirk Beetstra T C 00:02, 7 December 2009 (UTC)
A few comments on this whole topic. Blacklisting is evidence-based and isnt used Pre-emptively (With exception to malware/exploits). Removal requests are treated on a case by case basis where outcomes are based on community established policies and guidelines, which carry community-wide consensus. These core principles are agreed by all here, except for Gigs who is alone in opposing these priciples.
- "I object to this entire discussion as invalid on the grounds that it attempts to usurp editorial discretion and put it in the hands of a small group of blacklist maintainers" --Gigs (talk) 21:35, 4 December 2009 (UTC)
Additionaly, the discussion of Pre-emption started by Beetstra appears clearly intended to get thoughts and ideas on a hypothetical, and does not seem to be a proposal, nor does it attempt to trump current practice. So them, Why a Rfc? The RfC wholey miscaracterizes the purpose, intent and actual practice of blacklisting and appears to be an attempt by its creator to usurp discussion, further a viewpoint, and to imply that the MediaWiki:blacklist is somehow being improprly used.--Hu12 (talk) 19:05, 8 December 2009 (UTC)
- "All here" is a pretty biased audience of what, 3 or 4 people that have commented and are mostly also active in blacklist administration? Hence the RfC to widen the audience. Gigs (talk) 22:58, 8 December 2009 (UTC)
- To clarify, the RfC has nothing to do with pre-emption as Beetstra has proposed; it is only about current practices of blanket blacklisting entire pay-per sites when initial spamming is detected, and the second section is about using reliability as a factor in making black/whitelist decisions. Gigs (talk) 23:05, 8 December 2009 (UTC)
Gigs, one of the feelings I tried to get into the RfC yesterday evening was a reflection of what is actually behind blacklisting.
For these sites like examiner.com, there are billions of pages possible, all of them possible spam targets, what, even likely ones. Associatedcontent.com made it a long, long time without being fully blacklisted. And you don't want to know how much work has been behind it to keep up with spammers coming up with new stuff. There are a couple of whitelisting requests (for specific documents) a month, and some get declined as useless anyway. Yes, a couple. Those documents are really not worth the effort that would be behind cleaning up behind the spammers.
Is it bad that the whole site is blacklisted, from a sourcing point of view, YES. It hampers referencing the good stuff, it hampers in editing, it implies bad faith on those editors who contribute to these sites without having as primary target 'making money'. You say, there are here 3 or 4 people that have commented and who are mostly also active in blacklist administration (maybe a bad faith assumption, but there are only a few who understand what the problem actually is). Thát is the problem, and if the RfC does get more active in actually keeping up with the spam, then it is fine. But a likely outcome is the conclusion that many will say 'those sites should not be blanket blacklisted', the spam hence increases, but those who then have it made possible will not be the ones to help cleaning it up. Your remark '"All here" is a pretty biased audience' is not going to alleviate the already existing frustration (actually, it is in part the basis of this rant). Systematically fighting spam comes down to a handful of editors and admins, we all engage in fighting vandalism (even brand-new editors fight vandalism). Let me try again: Spam != vandalism. Vandals don't earn money from what they do. Spammers earn money from what they do, for some it is their job, companies run on spamming, what, even not-for-profit organisations hire SEOs to make sure they get linked in as many as possible places, because more links = more people know you = more people donating money to your good cause. Spam is not just the Sildenafil mails you get in your inbox. Spam is a more persistent problem than vandalism. Only few vandals go through the systematic effort of creating socks, finding ways to circumvent anti-vandalism bots or edit filters. A lot of spammers however do. It's their job. And sites like ehow, associatedcontent and examiner put that same power into the hands of the man in the street.
I am sorry, I don't think that the RfC will in any form be able to convey the significance and the size of the problem, I can however see other outcomes. And I don't think that is the feeling that I, nor you, can get into the RfC. --Dirk Beetstra T C 23:53, 8 December 2009 (UTC)
- What you are basically arguing here is: "Spam fighting is complicated, and spam fighters are hard to come by, so we should just avoid soliciting community consensus for what we are doing to fight spam". If what you were doing were uncontroversial, then maybe I'd say there's no reason to get a wider consensus. But it is clear that there are a number of editors coming here to challenge this every month, with requests that are denied on grounds that I'm not sure reflect wider community values. It's not a large number, but for every one that comes here, I'm sure there are more that get the nasty red box that never come to complain about it. How many good faith editors are getting stopped by the blacklist... I don't know. But I do feel like we have an obligation to follow up on this.
- If I don't do it now, it may come up later in a much nastier and more personal context when a less sympathetic experienced editor gets offended by it. If we do establish a community consensus, or if we at least have the discussion, then there can't be accusations that this was going on in a manner to avoid community consensus. You and Stifle have made constructive contributions to the RfC... I suggest that you try to integrate more changes into it to educate the readers about what you are doing here if you are still concerned that people will vote from a position of ignorance about spam efforts. I'm giving you this opportunity to help frame the issue instead of slapping an RfC out quickly there because I do know that there is a risk here of hampering spam fighting more than necessary. Gigs (talk) 00:25, 9 December 2009 (UTC)
Hmm .. no, that is not what I mean. It's more that I would like more people to actually get involved in the topic. And I have already seen the much nastier and more personal contexts of it (both from spammers and from experienced editors, both on spam topics and on other topics). It is not my first reaction, this is my second or third rant of this type regarding the more liberal use of sites which impose massive problems. I am sorry that I react this way, but you (and others) place the same common remarks which are made over and over (my apologies to you, Gigs, for the words, it is a reaction to the triggering of just the frustrations by (again, I am sorry) someone who is ignorant about spam efforts and spam problems, again the same remarks/arguments as we hear so often), which exactly describe the problem, but which are not a solution.
Of course I see utility in community consensus, and I am trying in the RfC, but I don't think that the RfC can express the problem, without going into extensive detail (and even then). I'll have a bit more of a go. --Dirk Beetstra T C 07:22, 9 December 2009 (UTC)
- "If I don't do it now, it may come up later ..." Pre-emptive RfC? ;)--Hu12 (talk) 08:07, 9 December 2009 (UTC)
- Anyways, Clarified it a bit, see my summaries. Lets remember, the draft RfC is for the funtion and practice of MediaWiki blacklist, this is not the whitelist, MediaWiki:Titleblacklist, or Xlink bot. Draft seperate RfC's on those respective pages if needed. --Hu12 (talk) 22:32, 9 December 2009 (UTC)
Note; Moved the draft out of the MediaWiki namespace to User:Gigs/blacklistRfC. This provides an appropriate development ground with corresponding talkpage, unlike interface pages. Feel free to continue discussions there. --Hu12 (talk) 07:51, 10 December 2009 (UTC)
- You have completely hacked it up, biased the facts section, and moved it to my userspace. Your edits are not constructive. Stop. Gigs (talk) 15:15, 10 December 2009 (UTC)
- I have tried to retain as much as I could of your edits, while restoring the neutral facts that Beetstra and Strife and I collaborated on. I have made the RFC live, so please just add your position into the discussion section, since it's at a point where I don't think we can go any further without actually beginning comment. Gigs (talk) 15:36, 10 December 2009 (UTC)
- You have completely hacked it up, biased the facts section, and moved it to my userspace. Your edits are not constructive. Stop. Gigs (talk) 15:15, 10 December 2009 (UTC)
Redtube.com
I'm posting this here because I'm not sure whether unlisting this subject is appropriate. There's been an article about Redtube (edit | talk | history | protect | delete | links | watch | logs | views) for a few weeks, but I notice the site itself is blacklisted. As the article contains independent references which verify a certain degree of notability, I'm wondering whether it might be useful to be able to include a link to the site itself. Having said that, I have heard of problems involving this stie in the past, one being that clicking on some of the links can result in the user receiving unwanted pop up windows requesting bill payments, which are locked for a certain amount of time. Any thoughts? TheRetroGuy (talk) 15:21, 15 December 2009 (UTC)
- I think it is best to have only a link to e.g. main index.htm or about.htm whitelisted, leaving the complete rest of the site impossible to link. Defer to Whitelist ?? --Dirk Beetstra T C 16:35, 15 December 2009 (UTC)