Edge Rewrite
Jump to content

Template talk:Link summary

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

Comment

[edit]

Would be nice to see this style of template used on meta. Would make for ease of cross posting spamlinks, as apposed to reformating for meta. just a thought.--Hu12 13:52, 28 September 2007 (UTC)Reply

Meta has a spamlink template:
--A. B. (talk) 14:11, 28 September 2007 (UTC)Reply

This template should not actually link to the domain. If the domain is blacklisted then the page can't be edited unless the template is removed. It also clogs up Special:LinkSearch with irrelevant results.  Mike.lifeguard | @en.wb 16:48, 12 May 2008 (UTC)Reply

Reports

[edit]

{{editprotected}} Could someone change [[:m:User:COIBot/cw/{{lc:{{{1|}}}}}{{!}}COIBot-XWiki]] to [[:m:User:COIBot/XWiki/{{lc:{{{1|}}}}}{{!}}COIBot-XWiki]]? The former won't work. Thanks. --Erwin85 (talk) 13:34, 23 August 2008 (UTC)Reply

 Done Happymelon 13:47, 23 August 2008 (UTC)Reply
[edit]

{{editprotected}}

Please change http://toolserver.org/~eagle/linksearch to http://toolserver.org/~eagle/crosswiki.php (it occurs twice) and http://toolserver.org/~eagle/spamsearch to http://toolserver.org/~eagle/spamArchiveSearch.php as the former URLs are broken. Thanks. MER-C 10:09, 4 December 2008 (UTC)Reply

 Done, thanks! --Dirk Beetstra T C 11:23, 4 December 2008 (UTC)Reply
[edit]

Hi!
related talk: Wikipedia talk:WikiProject_Spam#http_use_on_this_page.
I guess it would be helpful to have an additional link to
http://en.wikipedia.org/w/index.php?title=Special%3ASearch&search=%22example.org%22+prefix%3AWikipedia_talk%3AWikiProject+Spam&fulltext=Advanced+search.
Any objections? -- seth (talk) 19:54, 2 January 2009 (UTC)Reply

The reports could be extended by
[http://en.wikipedia.org/w/index.php?title=Special%3ASearch&search=%22{{{1|}}}%22+prefix%3AWikipedia_talk%3AWikiProject+Spam&fulltext=Advanced+search WikiProject Spam on en].
-- seth (talk) 12:13, 4 January 2009 (UTC)Reply
After thinking about this more, I realized that relevant talk sometimes takes place in areas other than the spam archives (WP:ANI, WP:RFPP, WP:AN3, WP:COIN, etc), so I wonder if it would be more useful to search the full namespaces for "Wikipedia" and "Wikipedia_talk" such as:
WPT space on en:
[http://en.wikipedia.org/w/index.php?title=Special%3ASearch&search=%22{{{1|}}}%22+prefix%3AWikipedia_talk%3A&fulltext=Advanced+search WPT space on en]
or, ideally, is there a way to merge that one with this, or would they each need to be separate?
WP space on en:
[http://en.wikipedia.org/w/index.php?title=Special%3ASearch&search=%22{{{1|}}}%22+prefix%3AWikipedia%3A&fulltext=Advanced+search WP space on en]
Just some options to consider. --- Barek (talkcontribs) - 18:58, 4 January 2009 (UTC)Reply
In that case you don't need the "prefix:..."
You can use the (old) normal syntax: . -- seth (talk) 21:32, 4 January 2009 (UTC)Reply
That format pulls things from all namespaces; which frequently has false positives in the search results. I think restricting to only the 'Wikipedia' and 'Wikipedia_talk' namespaces would be better at getting the most relevant results showing prominently. --- Barek (talkcontribs) - 00:43, 5 January 2009 (UTC)Reply
Have a look at my presented link. See the parameters ns4=1 and ns5=1. This means that only wikipedia NS and wikipedia_talk NS will be searched. -- seth (talk) 13:54, 5 January 2009 (UTC)Reply
Sorry about the misunderstanding. Yes, I agree that link would be the best way to go. --- Barek (talkcontribs) - 16:39, 5 January 2009 (UTC)Reply

modified proposal

[edit]

What do you think of this:
example.org:
Linksearch en - meta - de - fr - simple - wikt:en - wikt:fr • Interwiki link search, big: 20 - 57
Reports: Links on en - COIBot - Meta: SRB-XWiki - COIBot-XWiki - Eagle's spam report search
Linkwatcher: search
Wikipedia search: en - fr - deWikipedia and Wikipedia-Talk NS (en)what links to WikiProject Spam/LinkReports
Google: search - Veinor pages - meta • Yahoo: backlinks
Domain: domaintools - AboutUs.org - DomainsDB.net - Alexa - OnSameHost.com - WhosOnMyServer.com

-- seth (talk) 20:10, 6 January 2009 (UTC)Reply

I like the contents; although I think the wording needs to be compacted some, as "Wikipedia and Wikipedia-Talk NS (en)" and "what links to WikiProject Spam/LinkReports" seem a bit long and would clutter-up the already crowded template (the problem is, I'm not sure how best to reword it to compact it). --- Barek (talkcontribs) - 20:16, 6 January 2009 (UTC)Reply
I have added the two searches in a separate 'section' called "Discussions:" with resp. "tracked" as keyword for the Template-search and "advanced" as keyword for the advanced search. (Sorry to hurry this without further discussion, but the tools are too handy to wait for them, we can still discuss the semantics). --Dirk Beetstra T C 14:26, 8 January 2009 (UTC)Reply
Looks good to me; I think that adequately compresses the text so as to not add too much clutter - and the links are handy, so I appreciate having them added. --- Barek (talkcontribs) - 17:33, 8 January 2009 (UTC)Reply

Documentation

[edit]

{{editprotect}} Change doc-ref to {{documentation}}. Nsaa (talk) 00:59, 4 January 2009 (UTC)Reply

 Done - Rjd0060 (talk) 22:57, 4 January 2009 (UTC)Reply

Request

[edit]

{{editprotected}}

Adding {{Do not delete}} Triplestop x3 21:12, 3 September 2009 (UTC)Reply

Why? — RockMFR 01:32, 4 September 2009 (UTC)Reply

The template is often used to track spam on user talk pages. {{#ifeq|{{NAMESPACE}}|User talk|{{Do not delete}}||}} can work too. Triplestop x3 02:00, 5 September 2009 (UTC)Reply

ao

[edit]

Could something be done to specify what a.o. means here? Thanks. Rogerdpack (talk) 17:04, 21 June 2010 (UTC)Reply

Linked tools not working - toolserver user account expired

[edit]

Several links on this template now generate the following error message:

403: User account expired

The page you requested is hosted by the Toolserver user eagle, whose account has expired. Toolserver user accounts are automatically expired if the user is inactive for over six months. To prevent stale pages remaining accessible, we automatically block requests to expired content.

If you think you are receiving this page in error, or you have a question, please contact the owner of this document: eagle [at] toolserver [dot] org. (Please do not contact Toolserver administrators about this problem, as we cannot fix it—only the Toolserver account owner may renew their account.)

Does anyone know how to contact the user? Or, does anyone have access to copy the tools to another account? Or, last option, do we need to remove those tools from the template if they can not be recovered. --- Barek (talkcontribs) - 02:49, 16 December 2010 (UTC)Reply

I've reposted the above at WT:WPSPAM#Linked tools not working - toolserver user account expired to try to get more eyes onto the problem. --- Barek (talkcontribs) - 16:05, 22 December 2010 (UTC)Reply
[edit]

{{editprotected}} Please remove (or comment out) the following three lines:

-->[http://toolserver.org/~eagle/spamArchiveSearch.php/{{{1|}}} Eagle's spam report search] • <!--
-->Interwiki link search, big: [http://toolserver.org/~eagle/crosswiki.php?search={{{1|}}}&totalwikis=20 20] - <!--
-->[http://toolserver.org/~eagle/crosswiki.php?search={{{1|}}}&totalwikis=50 50] • <!--

The reports called by those three lines have not been functioning for over a month now. I would do it myself, but am not logged into my admin account at the moment, and feel it better to have another admin review this request anyways. --- Barek (talk) - 20:45, 25 January 2011 (UTC)Reply

 Done Eagle's account on toolserver is still expired.  Ronhjones  (Talk) 21:18, 25 January 2011 (UTC)Reply

OnSameHost.com

[edit]

OnSameHost.com should be removed from this template, because it's just serving spam. --82.136.210.153 (talk) 22:35, 21 October 2014 (UTC)Reply

Template-protected edit request on 6 January 2015

[edit]

Please remove OnSameHost.com, the site is down and is linking to spam. Remove (or comment out) the line:

 -->[http://onsamehost.com/query.jsp?host=www.{{{1|}}} OnSameHost.com] • <!--

—CraigyDavi (TC@) 18:34, 6 January 2015 (UTC)Reply

Done{{U|Technical 13}} (etc) 19:57, 6 January 2015 (UTC)Reply

Tools

[edit]
  1. Yahoo not responding as at 17:29, 11 February 2016 (UTC) (Will be right back... Thank you for your patience. Our engineers are working quickly to resolve the issue.)
  2. http://www.whosonmyserver.com/ may not work.

All the best: Rich Farmbrough, 17:29, 11 February 2016 (UTC).Reply

Template-protected edit request on 16 September 2017

[edit]

Please change "[http://www.alexa.com/data/details/main?url={{{1|}}} Alexa]" to "[https://www.alexa.com/data/details/main?url={{{1|}}} Alexa]" as Alexa supports HTTPS. Note that it appears this link is broken and should actually be something like "https://www.alexa.com/siteinfo/{{{1|}}}" but I'm not entirely sure if that was the information the original link was supposed to display. Jon Kolbert (talk) 14:53, 16 September 2017 (UTC)Reply

I've made some additional changes in the sandbox, adding https for DomainTools and Google as well as using non-relative links. Jon Kolbert (talk) 15:05, 16 September 2017 (UTC)Reply
@Jon Kolbert: https should not be forced; the way to do this is to give the URL as //site.tld/path/ (but only for sites that do support https). Example: (MediaWiki will add the http or https depending on the capabilities of the browser). Is the Alexa path correction also added in sandbox? Please update the Template:Link summary/testcases page to test any options you've changed. If it's all working, I'll be happy to deal with the editprotected request.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:19, 20 September 2017 (UTC)Reply
I made all links relative. Still not sure about the alexa-link, though, maybe someone else knows (I am not using that one myself in investigations, maybe User:MER-C?). --Dirk Beetstra T C 11:35, 20 September 2017 (UTC)Reply
I don't use it either. MER-C 11:46, 20 September 2017 (UTC)Reply
@MER-C, SMcCandlish, and Jon Kolbert: .. OK, I'll put it there, I guess 'they who is using/needs Alexa' will complain if it doesn't work anymore .. --Dirk Beetstra T C 12:14, 20 September 2017 (UTC)Reply
OK. Well, please test-case it, and if it's all in working order I'll copy the new code over into the live template.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  12:16, 20 September 2017 (UTC)Reply
@MER-C, SMcCandlish, and Beetstra: Using non-protocol relative links in the edit request was not an accident. All Wikimedia projects are served exclusively using HTTPS, so using a protocol relative link will lead to the HTTPS link anyway. The distinction between the two methods is that when using Special:LinkSearch/http://www.alexa.com it will bloat the results because the relative links are included despite never actually directing to HTTP. A few bots, including KolbertBot use LinkSearch to flag pages which may need a change. Templates using relative links can, and have artificially inflated LinkSearch by 300K+ articles. Jon Kolbert (talk) 18:51, 20 September 2017 (UTC)Reply
OK. Seems I got behind the times on a technical aspect.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  19:00, 20 September 2017 (UTC)Reply

Template-protected edit request on 23 February 2018

[edit]

Please change //www.whosonmyserver.com/?s=&submit=Lookup WhosOnMyServer.com to http://www.whosonmyserver.com/?s=&submit=Lookup WhosOnMyServer.com, https doesn't work. Jon Kolbert (talk) 16:59, 23 February 2018 (UTC) Jon Kolbert (talk) 16:59, 23 February 2018 (UTC)Reply

Actually, same goes for domainsDB. //www.domainsdb.net/ to http://www.domainsdb.net/. All links should not be relative links, they just tend to cause issues. [//www.aboutus.org/{{{1|}}} AboutUs.org] to [https://aboutus.com/{{{1|}}} AboutUs.com], //whois.domaintools.com/{{{1|}}} to https://whois.domaintools.com/{{{1|}}} Jon Kolbert (talk) 17:15, 23 February 2018 (UTC)Reply
 DoneJJMC89(T·C) 02:40, 24 February 2018 (UTC)Reply

Template-protected edit request on 17 June 2020

[edit]

Remove dead links from the links on the template:

No point keeping links to any of the above on the template.

Cheers, Naypta| ✉ talk page | 22:00, 17 June 2020 (UTC)Reply

Template-protected edit request on 21 August 2021

[edit]

Change

-->[https://wikipediatools.appspot.com/linksearch.jsp?link={{{1|}}}&https=1 MER-C X-wiki] • <!--

to

-->[https://wikipediatools.appspot.com/linksearch.jsp?link={{{1|}}}&https=1 MER-C X-wiki] - <!--
-->[{{canonicalurl:toollabs:global-search|q={{urlencode:"{{{1|}}}"|PATH}}}} '''gs'''] • <!--

This adds in the "gs" link that's seen on MetaWiki's version of this template. There's probably some other stuff that could be copied from there, but this is really the most useful link that the enwiki template is currently missing. You can see what this change looks like on the sandbox version of the testcases. Perryprog (talk) 17:58, 21 August 2021 (UTC)Reply

 Done although I've removed the bold (to match the other elements in the template). firefly ( t · c ) 10:49, 22 August 2021 (UTC)Reply

Alexa.com

[edit]

Alexa.com will be retired on 1 May 2022.[1] It'll need removing from the template at that point. Cabayi (talk) 12:20, 29 March 2022 (UTC)Reply

Or replacement by for example Similarweb.com?

References

[edit]

Please apply this sandbox diff to the template, changing the gs link to point directly to the global search tool without the iw.toolforge.org redirect; this is a tiny bit faster for users and works better with Special:LinkSearch. I tested this at Template:Link summary/testcases by visiting the non-sandbox links and observing that the sandbox links also turned purple, demonstrating that the old links redirect to exactly the URLs of the new links. Lucas Werkmeister (talk) 19:20, 29 September 2023 (UTC)Reply

 Done SWinxy (talk) 00:30, 30 September 2023 (UTC)Reply
 Actually done this time I swear. SWinxy (talk) 00:34, 30 September 2023 (UTC)Reply
@SWinxy: Thank you very much! And I think I’m now done with these edit requests too (at least on enwiki), this was the last “big” one (externallinks to iw.toolforge.org are now done to 27k from over a million). Lucas Werkmeister (talk) 09:25, 30 September 2023 (UTC)Reply

Edit request

[edit]

I believe the recent edit has caused to lint errors with the small tag somehow, see Special:LintErrors/multiple-unclosed-formatting-tags both lint errors are linked to this template. I'm not a template person, but the new edit seems somewhat inconsistant. Change to {{lc:{{{1|}}}}}|*|*}} I believe. --pro-anti-air >(talk)< 19:50, 21 October 2025 (UTC)Reply

I have reverted. This change appears to have caused Linter errors in a few cases, including at Wikipedia talk:WikiProject Spam/2007 Archive Apr. Testing in the sandbox and on the testcases page appears to be needed. – Jonesey95 (talk) 19:56, 21 October 2025 (UTC)Reply
Doesn't appear to have helped, I still see the errors. --pro-anti-air >(talk)< 19:59, 21 October 2025 (UTC)Reply

Switching to Lua

[edit]

Hi,

I've prepped a Lua version of this template at Module:Link summary and staged it in the sandbox. All the testcases look correct, so I'll make the swap in a few days if there aren't any concerns.

I think this should have a significant performance improvement on pages that use this template a lot. For example, on MediaWiki_talk:Spam-blacklist/archives/February_2008, nearly 70% of the page rendering time is in this template (the template itself plus all the calls to {{Replace}}):

Transclusion expansion time report (%,ms,calls,template)
100.00% 6997.248      1 -total
 35.96% 2516.530   4118 Template:Replace
 33.57% 2348.779    120 Template:LinkSummary
  5.95%  416.597    144 Template:IPSummary
  5.76%  403.361     21 Template:Spamlink
  1.74%  122.056     77 Template:UserSummary
  1.74%  122.016    576 Template:Color
  1.54%  107.939     78 Template:Toolbar
  1.31%   91.642     15 Template:User-multi
  1.07%   74.873    576 Template:Ifsubst

Legoktm (talk) 05:43, 30 December 2025 (UTC)Reply

 Done. Looking at MediaWiki_talk:Spam-blacklist/archives/February_2008 and MediaWiki_talk:Spam-blacklist, they're now roughly 1/3 faster. Legoktm (talk) 03:33, 2 January 2026 (UTC)Reply
MediaWiki talk:Spam-blacklist/archives/June 2021/Natural news is newly in Category:Pages where post-expand include size is exceeded. It might need to have its template transclusions replaced with #invoke direct module usages. There are a few more, and more might appear as the job queue refreshes them. – Jonesey95 (talk) 04:30, 3 January 2026 (UTC)Reply
Ugh, thanks for flagging. I guess we can fix the archives with direct #invoke, but if it's going to happen with new archives too, that'll be an issue. The job queue is roughly 30% updated, so we can guess there'll be another 7-9 pages? I'll give it another day before fixing up the archives. Legoktm (talk) 05:18, 3 January 2026 (UTC)Reply
I did a null edit on all of the unprotected subpages of MediaWiki talk:Spam-blacklist/archives, so they should be all caught up. – Jonesey95 (talk) 16:19, 3 January 2026 (UTC)Reply

Templated domains invisible to Wikipedia site search?

[edit]

I don't know if this has been caused by the above Lua change, or if it's is an older absence, but if a page uses this template and I perform a site search for the domain (which is obviously a common task when removing spam, and is linked within the template itself), the search results don't include that page. Is this an oversight?

For example, User talk:Itpl fiorano has a warning for spamming the domain fiorano.com, where that domain is only included inside the template, and nowhere outside it. A search for https://en.wikipedia.org/wiki/Special:LinkSearch?target=fiorano.com doesn't find that talk page.

(In case it's a caching problem I've also tested it with a new templated fake domain on my user page, and the search can't find that either.) Belbury (talk) 10:22, 7 January 2026 (UTC)Reply

@Belbury It is intentional, some links appear on many pages. In this way a linksearch only gives active links. To look for discussion or mentions of the template use the tracking link). Also (manual) archiving of discussions is impossible when the link is live in the discussions. There is {{LinkSummaryLive}} though for having a templated domain with link. Dirk Beetstra T C 18:05, 7 January 2026 (UTC)Reply
I see! Thanks. Belbury (talk) 18:17, 7 January 2026 (UTC)Reply