I went and reviewed all of my edits in that most recent batch and those were the only two errors that I found. Thanks again for keeping an eye out! Phuzion (talk) 16:27, 17 September 2025 (UTC)[reply]
Hello, Phuzion. Per your request, your account has been grantedtemporary-account-viewer rights. You are now able to reveal the IP addresses of individuals using temporary accounts that are not visible to the general public. This is very sensitive information that is only to be used to aid in anti-abuse workflows. Please take a moment to review Wikipedia:Temporary account IP viewer for more information on this user right. It is important to remember:
Access must not be used for political control, to apply pressure on editors, or as a threat against another editor in a content dispute. There must be a valid reason to investigate a temporary user. Note that using multiple temporary accounts is not forbidden, so long as they are not used in violation of policies (for example, block or ban evasion).
It is also important to note that the following actions are logged for others to see:
When a user accepts the preference that enables or disables IP reveal for their account.
Revealing an IP address of a temporary account.
Listing the temporary accounts that are associated with one or more IP addresses (using the CIDR notation format).
Remember, even if a user is violating policy, avoid revealing personal information if possible. Use temporary account usernames rather than disclosing IP addresses directly, or give information such as same network/not same network or similar. If you do not want the user right anymore then please ask me or another administrator and it will be removed for you. You may also voluntarily give up access at any time by visiting Special:Preferences. Happy editing! — rsjaffe🗣️04:21, 22 September 2025 (UTC)[reply]
In the future, if you come across a clearly incomplete draft that has been submitted by a brand new editor, please revert the submission rather than rejecting the draft. It is not uncommon for new accounts created for commercial editing and other improper purposes to disguise their intent by submitting drafts and like activities. The subject in this case is clearly notable on its face, having been a Supreme Court justice, but the article is clearly unsuitable for main space, and the submission was not in good faith. BD2412T02:32, 27 September 2025 (UTC)[reply]
Hello, I'm Zackmann08. Thank you for your recent contributions to N747PA. When you were adding content to the page, you added duplicate arguments to a template which can cause issues with how the template is rendered. In the future, please use the preview button before you save your edit; this helps you find these errors as they will display in yellow at the top of the page. Thanks. Zackmann (Talk to me/What I been doing) 08:57, 28 September 2025 (UTC)[reply]
The documentation for that template is broken, it does mention |map_name=, but the actual template code does |pushpin_map=. Maybe address that first before removing potentially useful caller code? --Joy (talk) 16:09, 12 October 2025 (UTC)[reply]
Hi, thanks for the feedback! I've been regularly verifying that my edits have no effect on how the infobox is rendered, if I've missed some, please let me know which ones and I can fix them. And as far as I can tell, the info in |map_name= and |map_type= is not useful for |pushpin_map=? Virtually every single monument that I've made the edits on has had a coordinates parameter, which |pushpin_map= uses to generate the map's location. Phuzion (talk) 16:23, 12 October 2025 (UTC)[reply]
It's apparent that the intent was to show a map that was more zoomed out than the mapframe. I guess I don't mind the outcome in the end, but it still seems like it's based on a bug...
It looks like map_name was active between this edit in 2018 and these edits in 2022[1][2], when the parameter name was replaced without explanation.
I suppose it's a question of whether we think it's better for the average English reader to see a zoomed in location, and then have to zoom out themselves to see country context; or if it's better for them to see a country location map, but then it precludes showing the zoomed in mapframe.
I do agree, there’s more discussion to be had about what the best zoom level of a map would be. However, as far as I can tell, the info that was held in the old parameters (such as |map_name= and |map_type=) is incompatible with the pushpin maps, with the possible exception of |map_caption= to |pushpin-caption=. The vast majority of these captions, however, have been extremely basic, and included no additional information other than “$subject’s Location”. Phuzion (talk) 19:37, 12 October 2025 (UTC)[reply]
Thanks :) at the same time, I'd reiterate that maybe there isn't any real need to do anything. The original error wasn't yours, it was in the template documentation, and it stood for years. We don't really strictly need those pushpin maps now that we have mapframes anyway. --Joy (talk) 21:01, 12 October 2025 (UTC)[reply]
Glad to see we're on the same page. I'll continue cleaning up infoboxes, but I'll make sure that I'm not removing potentially useful information moving forward. Thanks for the feedback! Phuzion (talk) 22:27, 12 October 2025 (UTC)[reply]
So just a suggestion, you should absolutely request template editor rights! Appreciate the ping on {{Infobox Israel village}} and I was happy to do it, but you should be able to do that yourself. That was certainly a non-controversial edit. In any case, if you do request it, ping me and I'll endorse ya. You've been doing great work and I think would be an asset to the TE community. Zackmann (Talk to me/What I been doing) 17:21, 23 October 2025 (UTC)[reply]
Thanks! I'll definitely consider requesting the permission. I don't think I have all of the requirements right now (sandbox edits, as an example), but I could probably argue that my edits in the Template talk namespace (largely edit requests with very specific instructions), might count towards that?
Also, would you be willing to walk me through the use of your unknown parameters script at some point? I installed it and I think there might be something missing or conflicting with it working. Phuzion (talk) 17:38, 23 October 2025 (UTC)[reply]
So my unknown params script is ABSOLUTELY a WIP... For the record, I didn't write most of it. The bulk of it was written by the marvelous User:Frietjes, who has written a number of awesome scripts. I just forked their script and made some improvements that work for me... But what errors or issues are you having? --Zackmann (Talk to me/What I been doing) 17:44, 23 October 2025 (UTC)[reply]
{{Infobox archbishop styles}}, it gives me the two popups, but the text never changes, and clicking "Show Changes" shows no difference. But if I click the link again, it acts as if there is already a check for unknown module in the text. This has happened on a couple dozen different templates that I've tried. Phuzion (talk) 17:57, 23 October 2025 (UTC)[reply]
Yep, I caught that when I was trying to figure out what was going on with the script a few days back. Nice feature! Thanks for the help! Phuzion (talk) 18:41, 23 October 2025 (UTC)[reply]
You are correct. I know about this issue. That's why I have the alert that says Already added, attempting to replace. CHECK DIFF CAREFULLY. It works some of the time, some of the time it doesn't... The original script from Frietjes would simply abort if the check for unknown was found. Mine attempts to replace it, but that doesn't always work and I don't know why. That being said you have inspired me to try to solve this issue... lol. Just know that when you get that "Already added" warning, the behavior may not be perfect. This is also important because if the Infobox is calling a Module that inherits params, those are not possible to detect. Hence the CHECK DIFF CAREFULLY. Zackmann (Talk to me/What I been doing) 20:35, 23 October 2025 (UTC)[reply]
Just always be careful with checking your diffs. I ran into an issue with {{Infobox state highway system}}. The modules it calls (Module:Infobox road/map for example) auto-detect args that are not present in the infobox code. so |map= is a valid parameter for that infobox while {{{map}}} is never specified in the code. So if you run the Chk4unkwn on that infobox, it will remove map from the accepted params... To my knowledge there is no way to account for this except on a case by case basis.
It's why I made this change. If Module:Person date is detected, it will automatically insert birth_date & death_date into the unknown params tracker. I did something similar for Module:Infobox mapframe. If you find other common modules like these, let me know and I will add it to the code, but for highly unique ones like the road modules, it doesn't make sense.
Will do! I've already done a few, if you wanted to glance at what I've done. Mostly just some additions here and there, but this one was slightly more than that. Phuzion (talk) 21:15, 23 October 2025 (UTC)[reply]
yo. check your AWB script. you dumped a bunch of pages into CAT:DUPARGS... [3], [4], [5] and about about a dozen more...
Something you might find useful: {{User:Zackmann08/cc|Articles using duplicate arguments in template calls|Duplicate args}}. You can see it and others on my user page. When you are running your cleanup scripts, I strongly recommend checking that category for recent additions that line up with what you are working on. Zackmann (Talk to me/What I been doing) 04:46, 25 October 2025 (UTC)[reply]
Yeah, looking at that particular AWB run, it seems like I forgot to put in a skip parameter if |start= or |end= already existed. I'll be much more careful moving forward. Thanks for letting me know, thanks for the suggestion with the userspace template. I know we work alongside one another on a lot of the invalid parameter stuff, and it's nice to have someone letting me know when something I do goes awry. Genuinely appreciate all the feedback you've been giving lately! Phuzion (talk) 04:58, 25 October 2025 (UTC)[reply]
Just out of curiosity, what is the preferred infobox for Tony Vitello? When I first edited it to reflect his move to the Giants, I added his MLB infobox but kept his college infobox. My reference behind this was Pat Murphy, who of course, before his career in the minors and subsequent managerial positions, was the long-time coach of Arizona State. I'd love to come to a consensus among the veteran editors about which direction they all want this page's infobox to appear. Elirbosley (talk) 11:07, 27 October 2025
Hey, thanks for the message! I'd say {{Infobox baseball biography}} (the one currently there) is probably the most appropriate right now, given that he is managing in the majors. I do wonder if there's a way that we can embed {{Infobox college coach}} into {{Infobox baseball biography}}, but it doesn't immediately appear that way. There's a lot of useful information that would be well-suited to remain in an infobox. Phuzion (talk) 16:15, 27 October 2025 (UTC)[reply]
Hello, Phuzion. This message is being sent to remind you of significant upcoming changes regarding logged-out editing.
Starting 4 November, logged-out editors will no longer have their IP address publicly displayed. Instead, they will have a temporary account (TA) associated with their edits. Users with some extended rights like administrators and CheckUsers, as well as users with the temporary account IP viewer (TAIV) user right will still be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range.
How do temporary accounts work?
Editing from a temporary account
When a logged-out user completes an edit or a logged action for the first time, a cookie will be set in this user's browser and a temporary account tied with this cookie will be automatically created for them. This account's name will follow the pattern: ~2025-12345-67 (a tilde, year of creation, a number split into units of 5).
All subsequent actions by the temporary account user will be attributed to this username. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser.
A record of the IP address used at the time of each edit will be stored for 90 days after the edit. Users with the temporary account IP viewer (TAIV) user right will be able to see the underlying IP addresses.
As a measure against vandalism, there are two limitations on the creation of temporary accounts:
There has to be a minimum of 10 minutes between subsequent temporary account creations from the same IP (or /64 range in case of IPv6).
There can be a maximum of 6 temporary accounts created from an IP (or /64 range) within a period of 24 hours.
Temporary account IP viewer user right
How to enable IP Reveal
Administrators may grant the temporary account IP viewer (TAIV) user right to non-administrators who meet the criteria for granting. Importantly, an editor must make an explicit request for the permission (e.g. at WP:PERM/TAIV)—administrators are not permitted to assign the right without a request.
Administrators will automatically be able to see temporary account IP information once they have accepted the Access to Temporary Account IP Addresses Policy via Special:Preferences or via the onboarding dialog which comes up after temporary accounts are deployed.
Impact for administrators
It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects the autoblock option.
It will still be possible to block an IP address or IP range.
Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this (see a video about IPContributions in a gallery below).
Rules about IP information disclosure
Publicizing an IP address gained through TAIV access is generally not allowed (e.g. ~2025-12345-67 previously edited as 192.0.2.1 or ~2025-12345-67's IP address is 192.0.2.1).
Publicly linking a TA to another TA is allowed if "reasonably believed to be necessary". (e.g. ~2025-12345-67 and ~2025-12345-68 are likely the same person, so I am counting their reverts together toward 3RR, but not Hey ~2025-12345-68, you did some good editing as ~2025-12345-67)
You can use this user right to perform maintenance, answer edit requests, and make any other simple and generally uncontroversial edits to templates, modules, and edinotices. You can also use it to enact more complex or controversial edits, after those edits are first made to a test sandbox, and their technical reliability as well as their consensus among other informed editors has been established. If you are willing to process edit requests on templates and modules, keep in mind that you are taking responsibility to ensure the edits have consensus and are technically sound.
This user right gives you access to some of Wikipedia's most important templates and modules; it is critical that you edit them wisely and that you only make edits that are backed up by consensus. It is also very important that no one else be allowed to access your account, so you should consider taking a few moments to secure your password.
If you do not want this user right, you may ask any administrator to remove it for you at any time.
If you were granted the permission on a temporary basis you will need to re-apply for the permission a few days before it expires including in your request a permalink to the discussion where it was granted and a {{Reply to}} for the administrator who granted the permission. You can find the permalink in your rights log.
I'm not the only one waiting for a bot flag right now, so I'm not too impatient about it. As soon as I get the flag and start the run, I'll let you know! Phuzion (talk) 18:27, 3 November 2025 (UTC)[reply]
Thanks a bunch! I just kicked off the run, it should be done in a few hours. I'll take a look at this and see if I can get AWB ready to go for that task as well. Phuzion (talk) 21:42, 8 November 2025 (UTC)[reply]
Hello! Voting in the 2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
.svg){kind=icon}
