Template talk:Sockpuppeteer

Language idea

This is a really nice looking warning box, but I'm concerned that the "puppet master" language might glorify sock-puppeting in the minds of the offenders. I'd like to suggest consideration for changing the language to something dismissive, basically to make it so that someone who has the {{sockpuppeteer}} tag on their page won't want to show it off to the rest of his friends in middleschool. Something along the lines of "This user is suspected or confirmed as using sock-puppets to evade bans/blocks" or some other defanged text. - CHAIRBOY (☎) 14:30, 5 October 2006 (UTC)

That's a good point, Chairboy, I agree. I put up an edit request template for you. I also wonder why the "list" links appear red, even when the categories are not empty, but that's no big deal. — coelacan talk — 04:06, 26 November 2006 (UTC)

Categories are weird: They can be populated, but unless you create them (Same as a page), they appear as red links. 68.39.174.238 11:51, 18 December 2006 (UTC)

Changed the wording in line with Chairboy's comment. Ashibaka tock 06:35, 26 November 2006 (UTC)

Change suggestion

Wouldn't it be easier just to say "to violate policy" rather then try and give a laundry list of things you can do with puppets? 68.39.174.238 23:01, 1 January 2007 (UTC)

</br>!?

The character sequence </br> lacks any syntactical and semantical meaning. It should definitely be removed from ...sock puppets</br>to evade... and changed to <br>, <br /> or two real line breaks at ...puppets]].</small></br>''The use... Anyway, you are free to use the toolbar above the editing box which has a button like this: regards, Torzsmokus 20:55, 25 January 2007 (UTC)

Wording of template

"Abuse, libel or ban evasion" - these are very different wiki crimes to be covered by such a broad brush. Avoiding 3rr or protectionist editing is not the same as abusive or libelous behaviour and I think having this catch all template lump these together could be libelous itself - remember some people do edit under their own names. Sophia 21:21, 3 February 2007 (UTC)

Edit

I think you should add a contribution link somewhere, maybe before or after block log link. Code: [[Special:Contributions/{{PAGENAME}}]] --AAA! ^(AAAA) 03:02, 8 February 2007 (UTC)

Seeing as this is designed for userpages, which have a contribs link in the toolbox, this probably isn't necessary. --ais523 18:06, 8 February 2007 (UTC)

Hm. Good-faith request, I'm glad to see. :) Not sure, either, myself -- to add to what ais523 mentioned, I rarely see this template used alone; it's usually supplemented with {{indefblocked}} or something similar, which itself includes a contribs link IIRC. Luna Santin 08:30, 9 February 2007 (UTC)

Replacment Image

I made an SVG version of the image used on this template. Perhaps it should be used? Improvement suggestions welcome. --Midnightcomm 04:24, 25 February 2007 (UTC)

I agree. --AAA! ^(AAAA) 03:22, 26 February 2007 (UTC)

I have added it. Thank you for creating it. Essjay (Talk) 03:48, 27 February 2007 (UTC)

Suspected or confirmed?

{{sockpuppeteerproven}} Just a suggestion, but shouldn't that top sentence It is suspected that this user has used... be changed to It is suspected or confirmed that this user has used... I really think that adding "confirmed" would make the template sound more efficient and accurate because of two reasons:

1. More likely it has been confirmed that the sockpuppeteer is an abusive sock master if WP:RCU confirmed the user's sock activities
2. This template should really be for confirmed puppetmasters instead of suspected puppetmasters

See what I mean? Power level (Dragon Ball) 04:53, 26 February 2007 (UTC)

Why not add or confirmed after where it says: It is suspected...? That's how it was before. I don't get why it was changed. Power level (Dragon Ball) 06:28, 27 February 2007 (UTC)

My main objection to this is that it is awkward and redundant. There are few or no confirmed sockpuppets, only varying degrees of probability. One can rarely be objectively sure that a user is a sockpuppet, even with a CheckUser search. Given that, 'suspected' covers CheckUser-confirmed cases anyway; they're just much more strongly suspected. —{admin} Pathoschild 08:01:23, 27 February 2007 (UTC)

Please change. "It is suspected that this user has used one or more accounts abusively" to "It is suspected or confirmed that this user has used one or more accounts abusively." Retiono Virginian 16:20, 1 March 2007 (UTC)

plural, singular

The {{sockpuppeteer|banned}} template now gives this line: This user has been blocked indefinitely because it is suspected that they have used one or more accounts abusively. - if you want in singular, you have to add "this user has" like {{sockpuppeteer|this user has|banned}}. Can it be done, that the singular form comes first? (without the need of adding "this user has") What is the reason for having a plural wording, anyway? --Vince ^{hey, yo! :-)} 00:52, 27 February 2007 (UTC)

Seems to be an application of the Singular they. Essjay (Talk) 01:16, 27 February 2007 (UTC)

Yep, although it is technically epicene they. Using a gender-neutral pronoun is less awkward than, say, "this user has been blocked because this user has..." or "this user has been blocked because he/she/it has...". :) —{admin} Pathoschild 01:32:01, 27 February 2007 (UTC)

About first sentence

Maybe change "It is suspected that..." to "It is supected or confirmed that..." --AAA! ^(AAAA) 08:21, 15 March 2007 (UTC)

I've restored the older version of {{Sockpuppeteerproven}} which has confirmed, since this one does not. I think it better to have the two separate templates. -- Avi 18:07, 15 March 2007 (UTC)

confirmed/blocked

Setting confirmed or blocked says indef block.

Should we allow for a version that doesn't say indef blocked.Mayalld (talk) 12:27, 6 August 2008 (UTC)

Suggested changes

This user has been blocked indefinitely because it is suspected that this user has used one or more accounts abusively. ==> This user has been blocked indefinitely due to the suspicion that one or more accounts were used abusively.

Disagree. It doesn't say that this user was the abuser, but it does imply it. — Rlevse • Talk • 22:04, 25 September 2008 (UTC)

---

This user has been blocked indefinitely because this user has used one or more accounts abusively. ==> This user has been blocked indefinitely due to the use of one or more accounts abusively.

Disagree. It doesn't say that this user was the abuser, but it does imply it. — Rlevse • Talk • 22:04, 25 September 2008 (UTC)

-- IRP ☎ 22:02, 25 September 2008 (UTC)

For the second one, how about: This user has been blocked indefinitely because this user has used one or more accounts abusively. ==> This user has been blocked indefinitely due to their use of one or more accounts abusively.

— Rlevse • Talk • 22:05, 25 September 2008 (UTC)

Disagree, "their" means more than one person. So how about his or her? -- IRP ☎ 22:09, 25 September 2008 (UTC)

OK. I'll get good template admin to do it as these are rather intertwined. — Rlevse • Talk • 01:53, 26 September 2008 (UTC)

If somethings not broken, why fix it? - Oppose any change without reason   «l| Ψrometheăn ™|l»  (talk) 14:14, 27 September 2008 (UTC)

• There's a consensus for this change, so I've went ahead and implemented it; however, I see no need for a change, and think the new version of this template to be of a poorer quality than the original. I propose undoing this change, if necessary in favour of some small improvements, but otherwise retaining the bulk of the content we've been using until now. I really see no problem here. Anthøny ✉ 21:26, 27 September 2008 (UTC)
  • We need more input this is a very small group that's participated here. — Rlevse • Talk • 22:55, 28 September 2008 (UTC)
    • The reason I wanted the change done was because it doesn't look right when this user is used twice. -- IRP ☎ 22:57, 28 September 2008 (UTC)
      • WAIT! An important change: This user has been blocked indefinitely it is suspected that he or she has used one or more accounts abusively. → This user has been blocked indefinitely due to the suspicion that he or she has used one or more accounts abusively. -- IRP ☎ 23:08, 28 September 2008 (UTC)
• The status quo didn't need to change, I tentatively suggest. Perhaps we can restore the template to the state it was previously in? Anthøny ✉ 23:12, 29 September 2008 (UTC)
  • I like the new header, but the "he or she" part is needlessly complicated IMHO. -- lucasbfr ^talk 18:24, 30 September 2008 (UTC)

Language correction

{{editprotected}} The wording "due to his or her use of one or more accounts abusively" which is used in the lower two alternatives ("proven" and "blocked with evidence") of this template sounds weird and is bad English. This should be changed to "due to his or her abusive use of one or more accounts". Is he back? (talk) 14:59, 16 January 2009 (UTC)

• Bit tricky, because of the switching - I have tried two possible ideas - see User:Black Kite/TemplateSock and User:Black Kite/TemplateSock2. No change made yet. Black Kite 21:18, 17 January 2009 (UTC)

• I think your second alternative sounds best. Is he back? (talk) 00:19, 19 January 2009 (UTC)

• Done I've changed the language similarly for all of the alternatives, as I would've had to restructure the template entirely otherwise.--Aervanath (talk) 15:16, 21 January 2009 (UTC)

Editprotected

{{editprotected}} Could someone please update the template from Template:Sockpuppeteer/sandbox? The sandbox changes the SPI casepage link to 'Sockpuppet investigations case page' and if a casepage already exists for the sockpuppeteer, it makes it appear automagically in the links. Foxy Loxy ^Pounce! 11:22, 2 March 2009 (UTC)

Not done: The code doesn't look right to me. You could end up with two links to the same page if the page exists. Please check your code. I'm not sure what the advantage of this is - if the page doesn't exist yet then it might well be convenient to have the redlink to help create it. Or maybe I'm missing something. Martin^msgj 14:15, 2 March 2009 (UTC)

The parameter and the automatic one are nested, so that one overrides the other, so that is not a problem (it has already been tested) and because of the specific format required at a SPI page, we don't want users just creating case pages, because they wont have the required content and format. Foxy Loxy ^Pounce! 22:47, 4 March 2009 (UTC)

The template also now has a timeblocked param for sockpuppeteers who were blocked, but not indef. Foxy Loxy ^Pounce! 07:13, 5 March 2009 (UTC)

Done. Cheers. --MZMcBride (talk) 07:17, 5 March 2009 (UTC)

Mbox

{{editprotected}}

Could the template please be updated with the contents of {{Sockpuppeteer/sandbox}}? This makes it use {{Mbox}}, instead of the deprecated messagebox class. TIA. —Ms2ger (talk) 12:20, 29 March 2009 (UTC)

Done. - Trevor MacInnis (Contribs) 16:27, 29 March 2009 (UTC)

Changes?

I'm wondering if we can add a category that seperates suspected sockpuppeteers from confirmed sockpuppeteers. I just took a look at the category and I didn't know who was a sockpuppeteer and who was not. Maybe we can clarify this a bit? Taylor Karras (talk) 07:17, 11 September 2009 (UTC)

Edit protected

{{editprotected}}

Change abusively used "one or more accounts" to "multiple accounts". Abusing one account is not sockpuppetry. Triplestop x3 20:23, 14 September 2009 (UTC)

I would do it, but all of the templates use the same wording. Are you going to propose those be changed also? - Rjd0060 (talk) 22:28, 14 September 2009 (UTC)

Not sure your wording solves the problem. In the case of good hand/bad hand accounts, the operator is a sockpuppeteer, though only one account is abused.  Skomorokh  22:30, 14 September 2009 (UTC)

Having one good account and abusing another account should count as abusing multiple accounts. And yes, I am proposing everything be changed. "abusively used one or more accounts" implies that using one account is sockpuppetry, when in cases like straightforward vandalism that is not the case. Triplestop x3 22:56, 14 September 2009 (UTC)

The wording is correct. This template is not to be used in cases when just a single account has been used. It is to be used when multiple accounts have been used, and at least one of the accounts has been used abusively. — RockMFR 03:10, 15 September 2009 (UTC)

Problem with the cats and links to evidence

The Category appears to be incorrect due to the renaming of cats from "Wikipedia confirmed sockpuppets . . ." to "Confirmed Wikipedia sockpuppets . . ." I'll try to work this myself when I get a moment. Also, the template seems to only work for newer sockpuppets as the evidence won't link to the older form of "Wikipedia:Requests_for_checkuser/Case/username".

use the following tag |evidence=[[Wikipedia:Requests for checkuser/Case/XXXXXX]] for those cases. -- Avi (talk) 05:37, 23 October 2009 (UTC)

actually, I think I built in functionality to just add |casename=XXXX where XXXX is the name used for the RFCU. -- Avi (talk) 16:14, 23 October 2009 (UTC)

Converting {{checkedpuppeteer}} to this template

When I made the emendations to this template a while back, the idea was to have it be the single puppeteer template. In that vein, I've expanded the examples in the documentation to show the specific CU and non-CU versions, and I'm slowly going through the {{CheckedPuppeteer}}'s converting them. Any help would be appreciated :) -- Avi (talk) 05:48, 23 October 2009 (UTC)

User to account

This should say ""account has been blocked indefinately" rather than user. Pages using this often have a "user has been banned" message too, I would say the account is blocked becasue the user is banned. Making the change, please let me know if you think it's wrong. Rich Farmbrough, 14:51, 22 June 2010 (UTC).

Present perfect for checkuser

I have a suggestion: how about changing the wording of the templates that involve CheckUser to "CheckUser has confirmed that....". The reason being that AFAIK CheckUser is a one-time process that checks the offending/suspected accounts' IPs against another account/confirmed offender. When it's finished, the report appears on the appropriate page and that's it. It isn't like admins with CU rights can/do perform such checks any time at will, is it? :P CoolKoon (talk) 21:02, 10 February 2011 (UTC)

Typo in "timeblocked" option

{{Sockpuppeteer|timeblocked}} gives the following text: "This account has been blocked for a period of time due the operator's abusive use of one or more accounts." I believe "due" needs to be changed to "due to" in order for this sentence to convey the intended meaning using proper English. Any comments? If no one objects, I'll make this change. — Richwales 15:45, 21 September 2012 (UTC)

Include the category

I think it would be helpful if the account this template is used on has the option to include the account in "Category:Wikipedia sockpuppets of foo" or "Category:Suspected Wikipedia sockpuppets of" to automatically list the master account. The master acocunt could be given the name * to distinguish it (ie [[Category:Wikipedia sockpuppets of Foo|*]]). -- A Certain White Cat ^chi? 12:23, 16 October 2012 (UTC)

Edit request on 22 December 2012

I want to add the word 'the' in the {{sockpuppeteer|timeblocked}} section of the template the sentence currently doesn't make any sense.

Hto9950 (talk | contribs) 07:13, 22 December 2012 (UTC)

I think that you mean the word 'to'; Done. --Redrose64 (talk) 20:37, 22 December 2012 (UTC)

Icon

Per the discussion at Template talk:Sockpuppet#Tiny RfC, I think we should restore the sockmaster icon over here as well. It's neither evil nor threatening, and the blue dot is outright non-informative. De728631 (talk) 15:01, 20 April 2013 (UTC)

Template-protected edit request on 10 June 2014

"Abusively using one or more accounts" is confusing. This could potentially be construed to mean that the user is abusively using his/her own account. I think that this should be changed to "abusively using two or more accounts" so that it is clear that it means that the user has been accused of socking specifically. Gparyani (talk) 16:22, 10 June 2014 (UTC)

Question: Gparyani, how about "Abusively using multiple accounts"? I'll change it to that, and if you don't think that works, then I'll revert and we can discuss some more. :) — {{U|Technical 13}} ^{(e • t • c)} 16:50, 10 June 2014 (UTC)

User:Technical 13: Yes, I think that that works. Thanks! Gparyani (talk) 17:03, 10 June 2014 (UTC)

Done Great! Then this is done. :) — {{U|Technical 13}} ^{(e • t • c)} 17:09, 10 June 2014 (UTC)

where is the template for okay sockpuppets?

Where is the template for allowed sockpuppets? Why isn't this included on this page in the see also section, or in the category? Thank you. Thewhitebox (talk) 09:57, 18 September 2014 (UTC)

Template-protected edit request on 23 September 2014

Something is wrong in the following text: {{#if:|for {{{time}}}|}}}; it has one closing curly bracket too many. Eyesnore (pc) 00:17, 23 September 2014 (UTC)

 Done — xaosflux ^Talk 00:56, 23 September 2014 (UTC)

{{sockpuppeteer|proven}}

Shouldnt this variety be reworded to say the account has actually been blocked not that it may need to be? 146.200.40.99 (talk) 11:00, 28 February 2015 (UTC)

I think it's fine as it is. Some sockpuppeteers openly admit to their wrongdoing or their editing pattern is so obvious that we don't need an SPI. But at that stage they may not yet be blocked, so the |proven variety may serve to alert administrators that blocking is still required. De728631 (talk) 12:08, 28 February 2015 (UTC)

Template-protected edit request on 12 June 2015

On the {{sockpuppet}} template, when "checkuser" is used on the first parameter, a CheckUser image is added on the right. However, {{sockpuppeteer}} does not do this. Please add the following markup inside the {{Mbox}} thing:

|imageright={{#ifeq:{{{checked}}}|yes|[[File:Wikipedia Checkuser.svg|50px|alt=A CheckUser has confirmed that the operator of this account abusively used multiple accounts]]|}}

TL22 (talk) 22:15, 12 June 2015 (UTC)

Okay,  Done — Martin (MSGJ · talk) 21:24, 14 June 2015 (UTC)

Proven and blocked

The sockpuppeteer template has one major issue: It don't have any options to tell that the puppeteer is both proven and blocked. How can we implement it? NasssaNser (^talk/_edits) 12:21, 3 October 2016 (UTC)

Link to SPI

Putting this here as a request because I don't really know what I'm doing with templates and don't want to screw things up. It'd be nice if the template would include a link to the sockmaster's SPI, in more cases than it currently does. Since this template is meant only to appear on the sockmaster's user page, and in theory if there is an SPI it'll be under the sockmaster's name (or redirected to the sockmaster's name) I think that it should be easy enough to implement. I just don't know how to do it. Cheers. Ivanvector (^Talk/_Edits) 13:58, 14 April 2017 (UTC)

There is already the |spipage= parameter but, it isn't automatically included because there are cases where the name of the established sockpuppeteer and the SPI page are different. I think though it should be possible to implement a default check in this template to search for an SPI page of the same name. If it exists, it should be linked, if the name is different, the parameter value could be added manually. De728631 (talk) 14:38, 14 April 2017 (UTC)

Blocked sockmaster page where the reason for the account originally being blocked has nothing to do with CU?

The wording This account has been blocked indefinitely because... kinda bothers me. See User:JoshuSasori -- that account was blocked for issuing off-wiki threats, then multiple non-CU-able SPIs found that he was evading his block via IPs, then a single sock account was found, CU was requested and initially endorsed, but not performed because the account admitted to being the same person. Then CheckUser was performed two days later and found a couple of sleepers. Later that week the user was site-banned for reasons unrelated to his sockpuppetry. I kinda feel like the majority of users who are blocked for some reason, then evade their blocks, are CUed, and tagged, are in this same situation, only perhaps a little less serious because their main post-block misbehaviour was the act of evading their block in-and-of itself rather than (in the JS case) continuing their off-wiki harassment.

Wouldn't a parameter being added to say CheckUser evidence confirms that the owner of this account has abusively used multiple accounts, and the account has been blocked be a good idea?

Or, honestly, changing the "Usage" from "Not blocked" to "Not blocked, or blocked for reasons unrelated to sockpuppetry"?

Hijiri 88 (聖やや) 23:48, 23 September 2017 (UTC)

I came here to say exactly the same thing. The example I came across was User:Fmadd, who was apparently indefinitely blocked for having an attitude problem, but created another account to evade the block afterwards which people spotted. Now it wrongly looks as if the block evasion was the reason why they were blocked in the first place (which would be a very sad state of affairs if it were true). Woscafrench (talk) 10:49, 12 November 2017 (UTC)

@Woscafrench: That kind of thing does happen from time to time, but more often in my experience is editors who are "angry" at their fixed-term block, strike out on their talk page, and their block is converted to indefinite. It's not really "sad", though, because the editors were told up-front what would happen and any reasonable human being would know that if they are temporarily blocked and they respond by creating a new account to evade their block the response would not be friendly. Anyway, the problem is not so much that it claims they are blocked for block evasion, since it just says "abusively used multiple accounts": most people who see that would assume it referred to creating multiple accounts to cast multiple !votes or some such, which is actually worse since the type of sockpuppetry they engaged in was block-evasion -- that just wasn't why they were blocked.

How to address this in the template, though...

Hijiri 88 (聖やや) 09:41, 19 April 2018 (UTC)

This is getting off topic, but I should clarify that Fmadd was never temporarily blocked. Their first and only block was indefinite. Woscafrench (talk) 10:14, 21 April 2018 (UTC)

3STRIKES

Can we have an option here related to WP:3STRIKES, alerting admins that this editor should not be lightly unblocked? --Dirk Beetstra ^{T C} 18:48, 9 August 2018 (UTC)

Template-protected edit request on 13 October 2018

I would like to transfer the contents of {{Sockpuppeteer/sandbox}} to {{Sockpuppeteer}}; there is a new parameter in the sandbox for linking to long-term abuse reports. Philroc (c) 12:58, 13 October 2018 (UTC)

Before making the sandbox live I have 3 questions/points...

1. Why is the LTA a separate box rather than included in the box already being added?
2. It assumes the SPI & LTA cases have the same name. Is this always the case? Would it be useful to optionally add an LTA case name/page?
3. It makes no #ifexist check for the existence of the LTA case page. ... Now that I think on it some more, a check whether the LTA page exists would make | lta=y unnecessary. Cabayi (talk) 13:16, 13 October 2018 (UTC)

@Cabayi: All fixed. Philroc (c) 13:31, 13 October 2018 (UTC)

 Done Philroc, Please update the documentation. I also added a default PAGENAMEE to ltapage - so the LTA shows up automatically if the names match, see User:Orangemoody for an example in action. Cabayi (talk) 14:08, 13 October 2018 (UTC)

I made it less obtrusive - an extra link at the parenthetical below, as many of the user pages already have a box to link to the lta case and having another large "see also" is duplication Galobtter (pingó mió) 14:29, 13 October 2018 (UTC)

Great for those pages which already have an extra box, not so good for those pages yet to be created. I guess the choice will be revisited when more new SPI/LTA cases emerge. It would be too much to hope that they don't. Cabayi (talk) 14:59, 13 October 2018 (UTC)

Template protected edit request on 28 October 2018

I'd like to modify the centralauth link to point to meta.wikimedia (since that's where most CentralAuth operations/logging happens). Please see this diff for the proposed changes (adding meta: in front of the Special:CentralAuth link). Regards Sau226 (talk) 08:44, 28 October 2018 (UTC)

Both Special:CentralAuth/Sockpuppeteer and meta:Special:CentralAuth/Sockpuppeteer show the same information. The only difference is the surrounding tools & presentation in the menus at the top & left-hand side. Being on enwiki is more likely to be useful for further action. Sorry, I don't see a positive to this change. So...

 Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. Cabayi (talk) 12:53, 28 October 2018 (UTC)

Template-protected edit request on 9 May 2019

Implement a few extra parameters from its sister template, {{Sockpuppet}}. See sandbox for proposed changes and WT:SPI for discussion relating to this. qedk (t 桜 c) 18:12, 9 May 2019 (UTC)

 Done — JJMC89 (T·C) 03:31, 10 May 2019 (UTC)

Template-protected edit request on 27 May 2019

I noticed the |imageright= parameter fails if both |1= and |checked= are given, resulting in a sort of "blockedconfirmed" parameter which fails every switch case. Just a minor change to switch it only if |checked= is missing. See here for suggested changes. Pinging JJMC89 who made the last change. qedk (t 桜 c) 05:50, 27 May 2019 (UTC)

@QEDK: this seems fairly straight forward, but can you demonstrate the current issue on the /testcases? Thanks, --DannyS712 (talk) 05:57, 27 May 2019 (UTC)

@DannyS712: Done. The current template fails the last case. --qedk (t 桜 c) 06:02, 27 May 2019 (UTC)

 Done DannyS712 (talk) 06:07, 27 May 2019 (UTC)

Template-protected edit request on 26 February 2020

Change "because the account owner" to "because its owner" and change "because CheckUser evidence confirms that the operator" to"because CheckUser evidence confirms that its owner" for brevity and harmonization. ミラP 01:32, 26 February 2020 (UTC) ミラP 01:32, 26 February 2020 (UTC)

@Miraclepine: I agree with the first edit, but the second one should probably be the account's owner because "it" could be referring to the evidence. --Ahecht (TALK
PAGE) 18:13, 26 February 2020 (UTC)

 Done Izno (talk) 23:01, 1 March 2020 (UTC)

Edit request on July 25, 2020

I have a version with a "globally locked" parameter as a replacement for {{locked global account}}. To enable the "globally locked" message, set parameter locked to anything that's not blank. –User456541 18:09, 25 July 2020 (UTC)

Is this really necessary? * Pppery * _{it has begun...} 03:59, 26 July 2020 (UTC)

@Pppery: This doesn't quite answer your question, but Template:Sockpuppet has it. --Mdaniels5757 (talk) 21:14, 26 July 2020 (UTC)

 Done Primefac (talk) 14:48, 2 August 2020 (UTC)

Edit request 26 March 2024

Description of suggested change: Would it be possibleto have a date appear once the template is applied, I realise it's not a big difference, but it saves having to go to page history everytime I want to see when action was taken with regard to the account. Regards, Goldsztajn (talk) 04:10, 26 March 2024 (UTC)

 Not done for now: please establish a consensus for this alteration before using the {{Edit template-protected}} template. There is no way for a template to know when it was added to a page, so this would require a new parameter to be used by editors. I find it unlikely that it would be used. — JJMC89 (T·C) 22:02, 30 March 2024 (UTC)

@JJMC89 - there's two different issues, consensus and technical. On the second, I'm requesting the inclusion of a timestamp; why would editors need to do anything? Could this not be done through the addition of ~~~~ or {{date}}? On consensus - happy to hear views why this would not be a good idea (although this is moot if there's a technical limitation I don't understand). Regards, Goldsztajn (talk) 05:55, 9 April 2024 (UTC)

Adding a parameter for a user-specified date is technically trivial; however, I doubt that CUs, admins, and SPI clerks would use it. (I would only use it if the SPI script did it for me and not for any manual tagging I do.) — JJMC89 (T·C) 17:50, 11 April 2024 (UTC)