Template talk:IPvandal

Usage

This template is designed to be used for IP users only, WHOIS will give random results if used on a username as opposed to an IP, also the pagemove function has been removed, as anon users are incapable of pagemoves. Also note that this template only references ARIN, as opposed to the general WHOIS database, and will not return any direct results for users outside of a certian geographic range.

Wicked!

Someone should've made this a long time ago. Nice! Snoutwood (talk) 00:09, 9 May 2006 (UTC)

• I'm not so sure about the new link, I agree that a north america only service is not very useful, but I'm not crazy about the output from samespade.org, too jumbled, seems like it would be more likely to scare away users who are less than tech savy, where as ARIN is pretty bare bones..
• since most people report vandalism via bot, the only way IPvandal is going to catch on is if it becomes popular with casual vandalism reporters, it seems like user friendliness might be more important at this point, than thouroughness--{anon iso − 8859 − 1janitor} 03:16, 11 May 2006 (UTC)

Do you have a better link? ARIN isn't useful because it's North America only, and more than half of our users come from Europe, Oceania, South America, Asia, and even a few from Africa. If we're worried about the non-tech-savvy, how will they possibly know to go to RIPE or wherever else? If you have a better WHOIS site than Sam Spade, though, I'm certainly open. Snoutwood (talk) 05:29, 11 May 2006 (UTC)

Seems to be working perfectly well, the only issue I *might* have is that they seem to have a lot of server downtime--{anon iso − 8859 − 1janitor} 12:34, 16 June 2006 (UTC)

I've restored the external link "light blue" coloration for the sam spade sam spade link, and added an example at the bottom. — May. 26, '06 [09:55] <freak|talk>

necessarily vandal?

I feel like calling this "IPvandal" insteald of "IPinfo" or something is disingenuous. Not all IPs are vandals (indeed, most are not), but sometimes it is useful to have such information for them too. - Che Nuevara 18:04, 13 December 2006 (UTC)

If it were a non-vandal template, it shouldn't have the Special:Blockip link. I'd be happy to have a non-vandal version, but due to that (and to some extent the block log link, a bad-faith sort of link) I would think that it would be best in a different, modified, template. Snoutwood 19:55, 13 December 2006 (UTC)

Point taken; I've used this template at an RfAr because I thought it would be useful to have the WHOIS etc., but I would support a new version without the block links. - Che Nuevara 06:13, 14 December 2006 (UTC)

See also {{IPUser}}--172.152.30.67 20:56, 26 January 2007 (UTC)

protection?

why is a template that's never been vandalized sprotected? hmm?--172.152.30.67 20:55, 26 January 2007 (UTC)

I don't know. In fact, I don't think it's right to have high risk templates semi-protected. TobytheTramEngine 15:54, 3 December 2007 (UTC)

so how do I use this?

I found an IP that has been a vandal and I would like to use this to report them, but I don't know how. Can I have some instructions? Thanks. Psu256 (talk) 14:28, 11 January 2008 (UTC)

You fill out the template, then place it on WP:AIV so that the vandalism can be brought to the attention of administrators.--VectorPotential^Talk 15:13, 9 February 2008 (UTC)

Not working correctly?

Hello - I saw the IP Vandal Template when I edited at page:

   Pages transcluded onto the current version of this page:
   Template:IPvandal (view source) (semi-protected)

But when I used it above - a lot of the links are red (ip address and talk), show up empty (contributions) or don't work (http, RDNS). Someone should fix the template. 99.150.255.75 (talk) 02:27, 18 February 2010 (UTC)

Could someone update the WHOIS link?

I don't want to muck this up but could someone switch the link here from dnstuff to the toolserver? The ip talk and related pages already use that method. Kwsn (Ni!) 14:52, 23 September 2011 (UTC)

 Done. -- Luk ^talk 16:31, 11 January 2012 (UTC)

Separator character

Maybe a bit pedantic, but could the separator dot please be changed to '''·'''? The display at WP:AIV looks a mess, because this template uses a huge bullet, and {{vandal}} uses a tiny dot. The suggested code is a compromise. — This, that, and the other (talk) 10:08, 22 October 2011 (UTC)

 Done I used {{int:dot-separator}} (which is currently equivalent to '''·''') to match templates such as {{user}}. Anomie⚔ 00:12, 23 October 2011 (UTC)

It looks like you removed the filter log in the process ... was that intentional, or an accidental omission? --- Barek (talk • contribs) - 18:47, 11 January 2012 (UTC)

I didn't remove anything: this is all I did. Anomie⚔ 19:15, 11 January 2012 (UTC)

I see now, sorry about that. It looks like it was removed by Luk in this edit (look like it was related to the thread above this one). I'll bring it up on their user talk page. --- Barek (talk • contribs) - 19:32, 11 January 2012 (UTC)

Yup, I screwed up there! -- Luk ^talk 22:15, 11 January 2012 (UTC)

IPV6 update

• 127.0.0.1 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
• 2001:4BA0:FFF9:17E:0:0:0:2 (talk · contribs · (/64) · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log)

Update preformed as some tools dont work for IPV6. -- A Certain White Cat ^chi? 01:47, 10 June 2012 (UTC)

Small fix needed

This tag flips out if you leave a space around the IP number:

normal tag:
127.0.0.1 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)

with leading space:
127.0.0.1 (talk · contribs · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log)

trailing space:
127.0.0.1 (talk · contribs · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log)

Since IP numbers are typically cut and pasted this happens frequently, at least to me. It can't be that hard to fix this (the regular wiki double bracket article links ignore leading and trailing spaces). Thanks. Hairhorn (talk) 13:01, 21 September 2012 (UTC)

Edit request on 1 April 2014

Replace both occurrences of

[http://{{{1}}}/ http]

with

[http://{{Trim|{{{1|}}}}}/ http]

Should work like:

• http

All the best, Rich Farmbrough, 23:40, 1 April 2014 (UTC).

@Rich Farmbrough: Question: How about

[http://{{#if:1|{{{1|}}}}}/ http]

which gives http. A parser function always strips whitespace, and since {{trim}} is built with a parser function, it'll be quicker too. --Redrose64 (talk) 10:46, 7 May 2014 (UTC)

Hm, that is what {{Trim}} does. IMHO {{Trim}} makes for clearer code and is less likely to be optimised away by a future editor. Trim will be cached so there's no disk read overhead, and it wil lonly be called when the page is rendered. We could do a speed test. All the best: Rich Farmbrough, 11:10, 7 May 2014 (UTC).

The following is with 3200 invocations.

Stat	Trim	#if
CPU time	4.440	2.388
Real time	4.506	2.445
PP v nodes	22,401	6,401
PP g nodes	57,639	57,604
Post-exp inc.	89,600	44,800
Temp arg size	44,800	0
Highest exp depth	3	2
Exp. Parser funcs	0	0

So the extra cost from calling {{Trim}} is about .0006 seconds - I think that is probably bearable. All the best: Rich Farmbrough, 11:27, 7 May 2014 (UTC).

Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. The problem isn't the speed factor, it is the fact that it adds 44,800 to the post-include size, which could be enough to cause template expansion size exceeded errors and should be avoided. — {{U|Technical 13}} ^{(t • e • c)} 15:57, 12 May 2014 (UTC)

Technical 13 Please ping me if you have a query with one of my requests. Note the table above is for 3,200 invocations, as clearly stated. The overhead therefore is 14 bytes. All the best: Rich Farmbrough, 01:42, 22 August 2014 (UTC).

Any disagreement with the above improvement? All the best: Rich Farmbrough, 01:42, 22 August 2014 (UTC).

Note this functionality has been moved out into an infinitely nested series of templates and modules.

Edit request on 7 May 2014

For IPV4 section, change

|6=[http://toolserver.org/~chm/whois.php?ip={{{1}}} WHOIS]

to

|6=[http://toolserver.org/~overlordq/cgi-bin/whois.cgi?lookup={{{1}}} WHOIS]

as it has expired. --Glaisher [talk] 09:02, 7 May 2014 (UTC)

@Glaisher: Question: Why the old toolserver? The equivalent link in Template:Anontools/ipv4 is to http://wolfsbane.toolserver.org/~overlordq/cgi-bin/whois.cgi?lookup= notice that the domain is wolfsbane.toolserver.org not toolserver.org --Redrose64 (talk) 10:51, 7 May 2014 (UTC)

@Redrose64: What do you mean by old toolserver? AFAIK, ortelius and wolfsbane are both web servers of toolserver. When toolserver is shut down, both those servers also get shutdown. I don't know of a WHOIS tool on Labs. We'll have to change it when toolserver gets closed next month. (Perhaps to an external whois tool if there is no replacement on Labs.) --Glaisher [talk]

I just think that the WHOIS link should be the same, wherever the script actually resides. --Redrose64 (talk) 17:05, 7 May 2014 (UTC)

@Redrose64: What difference would be there? :) It was changed to wolfsbane.toolserver.org temporarily due to issues (it was never changed though even when it was fixed). See this thread. A link to a wolfsbane or main toolserver would be fine as long as it is working. I would appreciate it very much if this could be done quickly as this template is used at a high traffic page (AIV). --Glaisher [talk] 04:33, 8 May 2014 (UTC)

OK, Done --Redrose64 (talk) 09:16, 8 May 2014 (UTC)

Question: Rose, why is the old toolserver being used instead of |6=[https://accounts.wmflabs.org/redir.php?tool=oq-whois&data={{{1|<!--IP address-->}}} WHOIS] which is a redirect to a who is from labs? Any objections to using the labs whois redirect Glaisher? — {{U|Technical 13}} ^{(t • e • c)} 16:01, 12 May 2014 (UTC)

I don't know why you're asking me why is the old toolserver being used. It was Glaisher who asked for that; I was querying wolfsbane.toolserver.org vs toolserver.org --Redrose64 (talk) 20:50, 14 May 2014 (UTC)

Template-protected edit request on 8 July 2014

WHOIS no longer works and I don't see it was migrated, so I suggest using robtex, like we do for RBLs. Please change:

(in the IPV6 section)

|5=[http://toolserver.org/~overlordq/cgi-bin/whois.cgi?lookup={{{1}}} WHOIS]

to

|5=[https://www.robtex.com/ip/{{{1}}}.html#whois WHOIS]

and

(in the IPV4 section)

|6=[http://toolserver.org/~overlordq/cgi-bin/whois.cgi?lookup={{{1}}} WHOIS]

to

|6=[https://www.robtex.com/ip/{{{1}}}.html#whois WHOIS]

—[AlanM1(talk)]— 14:15, 8 July 2014 (UTC)

Note that the following templates also call the same defunct overlordq whois script: {{Whois}}, {{Proxyip6}}, {{Proxyip4}}, {{IPuser}}, {{Proxyip2}} and are likely candidates for the same change. —[AlanM1(talk)]— 14:27, 8 July 2014 (UTC)

Question: Wouldn't it be better to use toollabs:whois? — {{U|Technical 13}} ^{(e • t • c)} 14:37, 8 July 2014 (UTC)

The json output is not particularly user-friendly and I don't see a way to change that. —[AlanM1(talk)]— 12:06, 9 July 2014 (UTC)

(clarifying) I mean it's not obvious how to change it. I haven't looked at the code. I've used robtex myself for a while, and we use it for the RBL link, so it seems a reasonable solution. —[AlanM1(talk)]— 13:54, 9 July 2014 (UTC)

Probably better if we can get this code added to Template:User-multi and then convert this template. Then we won't have to update multiple templates when the code changes. I've posted a request on the template talk page. — Martin (MSGJ · talk) 11:08, 11 July 2014 (UTC)

Looks like it's been added over there. —[AlanM1(talk)]— 17:52, 11 July 2014 (UTC)

• As this affects my ACC work in some cases, I oppose using an external whois lookup when we have our own on tools.wmflabs.org — {{U|Technical 13}} ^{(e • t • c)} 18:32, 11 July 2014 (UTC)

Where? —[AlanM1(talk)]— 18:40, 11 July 2014 (UTC)

Doh! I forgot about the above (and then wacked this edit – time for a break :( ). What about the less-than-ideal json output format? —[AlanM1(talk)]— 18:43, 11 July 2014 (UTC)

I've implemented this template using {{User-multi}} in the sandbox. Note, however, there are functions currently present here that seemingly are not available in {{User-multi}}, specifically "http", "info", "RDNS", and "trace". It probably makes sense to re-evaluate which links/tools are available for IPv4 and IPv6 anyway. —[AlanM1(talk)]— 18:40, 11 July 2014 (UTC)

So, meanwhile, we still have broken whois functionality on a bunch of pages. Until a decision can be made on which of the other missing functions to implement and where, can we just get whois working again with the edits requested above? —[AlanM1(talk)]— 13:33, 13 July 2014 (UTC)

I have removed the broken links, so we now do not have broken links. Once this discussion ends up with a decision, a working link can be re-added. — xaosflux ^Talk 03:52, 17 July 2014 (UTC)

Sorry I haven't had much time to follow up on this. I've added a request for those missing links to user-multi. The links to http://www.dnsstuff.com/ don't seem to be working at the moment. (See my examples over there.) — Martin (MSGJ · talk) 09:30, 17 July 2014 (UTC)

Two more have now been added here. — Martin (MSGJ · talk) 10:50, 17 July 2014 (UTC)

Cool. Thanks. I've updated the sandbox —[AlanM1(talk)]— 15:03, 20 July 2014 (UTC)

I've also updated or verified the other templates that called toolserver's whois: {{Whois}} (pending copy from sandbox), {{Proxyip6}}, {{Proxyip4}}, {{IPuser}}, {{Proxyip2}}. —[AlanM1(talk)]— 17:21, 20 July 2014 (UTC)

Template-protected edit request on 27 September 2017

Please surround the user fields with {{noping}}. Thanks. jd22292 (Jalen D. Folf) (talk) 00:06, 27 September 2017 (UTC)

Not done: IPs cannot be pinged. — JJMC89 (T·C) 00:13, 27 September 2017 (UTC)

Prevent ping notifications

It's quite annoying to get the "failed ping" notification every time I AIV an IP user. I'm not sure what the best fix here is: {{noping}} would work, but losing the redlink is annoying; we could also do what pretty much everything else does with IPs and just link to contribs. Gaelan 💬✏️ 06:27, 7 February 2019 (UTC)

I came here to post the same thing as Gaelan, though I don't see losing the red link as a significant problem. Would it be possible to change this template to behave as {{no ping}} does, avoiding the notification system, by making external links with code like <span class="plainlinks">username</span> instead of wikilinks like [[User:Username|Username]]? BlackcurrantTea (talk) 21:21, 3 June 2020 (UTC)

 Not done for now: please establish a consensus for this alteration before using the {{edit template-protected}} template. Please reactivate this template when you have figured out what you want. Thanks. Feel free to make changes to the template's sandbox. – Jonesey95 (talk) 23:34, 3 June 2020 (UTC)

Template-protected edit request on 7 September 2020

The "deleted contribs" and "block user" links should be hidden under sysop-show, as they are on {{vandal}}, because only admins can access them. Username⁶⁸⁹² 18:27, 7 September 2020 (UTC)

 Not done for now: this uses the meta-template {{user-multi}} so you may need to make your request there instead — Martin (MSGJ · talk) 19:54, 8 September 2020 (UTC)

IPv6 needs to be uppercase

A report at at WP:VPT points out that IPv6 contributions links no longer work if lowercase is used (and lowercase is what you get when copying from, say, a history page). The bug is tracked at phab:T272225.

Meanwhile, reports at WP:AIV do not contain working IPv6 contribs links. A workaround would be to use Module:String2 as shown in this demo:

• [[Special:Contributions/2600:1004:b0c7:da25:905c:f34b:a2aa:b252]] → Special:Contributions/2600:1004:b0c7:da25:905c:f34b:a2aa:b252 (link currently does not show contributions)
• [[Special:Contributions/{{#invoke:String2|upper|2600:1004:b0c7:da25:905c:f34b:a2aa:b252}}]] → Special:Contributions/2600:1004:B0C7:DA25:905C:F34B:A2AA:B252 (link works)

I'm not sure where that should occur and don't know if other pages would also need a patch. Any thoughts? Johnuniq (talk) 00:09, 26 January 2021 (UTC)

Resolved Phab:T272225 has been fixed. User:GKFX^talk

Edit request to complete TfD nomination

Template:IPvandal has been listed at Templates for discussion (nomination), but it was protected, so it could not be tagged. Please add:

{{subst:tfm|help=off|type=tiny|1=Vandal}}

to the top of the page to complete the nomination. Thank you. Aasim - Herrscher of Wikis ❄️ 13:31, 17 October 2022 (UTC)

 Completed. P.I. Ellsworth , ed. ^put'r there 11:51, 18 October 2022 (UTC)

Edit request 26 October 2022

Description of suggested change: This template needs to be merged into {{Vandal}} per the outcome of the TfM. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 20:21, 26 October 2022 (UTC)

• More immediately, the nomination template needs to be removed. — Ceso femmuin mbolgaig mbung, mellohi! (投稿) 14:40, 27 October 2022 (UTC)

  Yes that too. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 16:44, 27 October 2022 (UTC)

  @Blaze Wolf "Merge this template" is not a suitable edit request. Please read the text of the edit request template. If you want to merge the templates yourself then you need to have written the template code, tested it in the template's sandbox, and verified that the testcases still work correctly. If you don't know how to do that that just leave it for another editor, this is already listed at WP:Templates for discussion/Holding cell and a template savvy editor will get around to doing it. 192.76.8.80 (talk) 18:04, 27 October 2022 (UTC)

  I can't merge it myself because I'm not a template editor. I didn't know this was already listed at the holding cell because the nomination template still says it's at TfM when that was closed. If I were a template editor then I would do what you described and do it myself. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 18:09, 27 October 2022 (UTC)

  @Blaze Wolf You don't need to be a template editor. You would need to write the code for the merged template, test it at Template:IPvandal/sandbox then check that everything at Template:IPvandal/testcases still works. None of that requires template editor rights, all those pages are unprotected. 192.76.8.80 (talk) 18:12, 27 October 2022 (UTC)

  Right, but in order to actually do the merge I need to be a template editor because both templates are Template protected. Regardless, the template at the top needs to be changed. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 18:15, 27 October 2022 (UTC)

I've changed the template at the top. Actually implementing the merge is Not done for now pending someone doing the relevant coding in the sandbox. * Pppery * _{it has begun...} 18:23, 27 October 2022 (UTC)