This user is busy in real life and may not respond swiftly to queries.
If you are here to request something to be suppressed, do not post it here. Instead, please visit Wikipedia:Requests for oversight to see how you can get in touch with the Oversight team regarding your request.
Hey LuK3 - I'm jumping the gun a bit, but at 100% support with a couple of hours to run I don't think I'm taking too much of a risk of getting egg on my face - congratulations, welcome to the team, drop me a note if you ever want a second pair of eyes on something. Happy mopping when the time comes! GirthSummit (blether)12:52, 23 September 2020 (UTC)[reply]
A not quite as early bird from me - I'm incommunicado for a few hours, but I wanted to drop my thanks here first. Congrats on a good run. Best of luck with your mop wielding! Nosebagbear (talk) 13:47, 23 September 2020 (UTC)[reply]
Hi LuK3 and congratulations on passing RFA. I have closed your RFA as successful. It looks like you may not be newest admin for very long, possibly not long enough to make the tea as there is another on the way later today. When you get bored of scrabbling down the back of the sofa to find the right block message have a look at my Monobook - some kind soul put a really nifty script there that gives a useful dropdown menu. Once again, welcome. ϢereSpielChequers14:25, 23 September 2020 (UTC)[reply]
Thank you everybody for the kind words and support, I truly appreciate it. Now to learn some new buttons carefully, thank you again! -- LuK3(Talk)15:09, 23 September 2020 (UTC)[reply]
Congratulations! My only words of advice is that it is never a bad idea to ask for a second opinion if you are unsure about a decision or have a conflict. Even admins who've been doing the job for years and years do it in particular situations. It's how you learn...which never really ends. Good luck! LizRead!Talk!17:19, 23 September 2020 (UTC)[reply]
On behalf of the Always Righteous Bastion of the Committee Of Mops (not to be confused with that other ARBCOM), I hereby grant you your first mop. Treat it well, and it shall treat you well. CaptainEekEdits Ho Cap'n!⚓18:42, 23 September 2020 (UTC)[reply]
Congrats! Very well deserved, and pleasantly surprised to see your RfA pass quite as uncontroversially as it did - doesn't happen often! ~ mazcatalk21:52, 23 September 2020 (UTC)[reply]
(belated) Congratulations! Please don't be afraid to ask any questions should you ever have any! I would also recommend stealing -- ahem...borrowing...long term... -- scripts from other admin's JS and CSS. --TheSandDoctorTalk04:36, 26 October 2020 (UTC)[reply]
2021 CheckUser and Oversight appointments: candidates appointed
Hello everyone, and welcome to the 27th issue of the Wikipedia Scripts++ Newsletter, covering all our favorite new and updated user scripts since 2025! Boy, does it feel good to kick off the year with an issue. Yep, it's been a year since we cleared out the 2022-2024 backlog with issues 23 and 24! Good times. Though in this case "a year" just means... 6 months? 😯 The salience of whatever joke I was planning to make here has vanished speedily. Aaron Liu (talk) 21:00, 31 July 2025 (UTC)[reply]
Got anything good? Tell us about your new, improved, old, or messed-up script here!
WikiTextExpander by Polygnotus, is this edition's featured script. At the click of a configurable hotkey, this script will find and replace or link a configurable list of phrases within the selected text in all source editors (even in the comment/reply field!). Besides allowing the quick insertion of templated messages, this script greatly mitigates the WP:WTF? problem by providing both the legibility of familiar words and the convenience of shortcuts. And to those asking, the capitalization of "Wikitext" as "WikiText" was a necessary sacrifice for far-more-memorable acronymy.
CanonNi: AlertAssistant has been fixed and rewritten using OOUI instead of Twinkle's Morebits. Such modern, very tool. (Do note that the maintainer has since become inactive.)
NguoiDungKhongDinhDanh/AjaxLoader has been updated to use modern JS APIs that replace the browser's URL bar with the link you clicked on to load in place. The "back" (and "forward") buttons also work now. Cool, innit?
andrybak: Unsigned helper no longer shows an error when the message to sign was added in the earliest 50 revisions of a page's history. This is especially relevant to pages with short histories.
BilledMammal/Move+ needs updating to order list of pages handle lists of pages to move correctly regardless of the discussion's page, so that we may avoid repeating fiasco history.
In breaking m:Tech/News, Gadgets can now include .vue files. This makes it easier to develop modern user interfaces using Vue.js, in particular using Codex, the official design system of Wikimedia. Codex icons are now also available. The documentation has examples.
Appo/Globstory integrates OpenHistoryMap, updating the map whenever hovering/clicking on a location or year, the latter of which changes the map to be (hopefully) accurate to the year selected. It's pretty interesting.
linkinfo Somewhat similar to WP:NavPops, Awesome Aasim/linkinfo(pictured) provides a collection of links to replace the right-click context menu, presented beautifully.
PreviousDiscussions provides a link to search for your username on subpages of another user's userpage and talkpage conveniently.
Twineeea/noRedLinks brings you to the "read" instead of the "create" tab when you visit a red link. Contemplate life's mysteries as you stare into the blank! Deeply.
No, this is not going to be the enduring tradition of S++ for the future. This was meant to be a joke for the special occasion on the first day of the fourth month but was delayed by four months because I'm lazy.
Following a request for comment, there is a new policy outlining the granting of permissions to view the IP addresses of temporary accounts. Temporary account deployment on the English Wikipedia is currently scheduled for September 2025, and editors can request access to the permission ahead of time. Admins are encouraged to keep an eye on the request page; there will likely be a flood of editors requesting the permission when they realize they can no longer see IP addresses.
South Asia (WP:CT/SA) is designated a contentious topic. The topic area is specifically defined as All pages related to the region of South Asia (India, Pakistan, Afghanistan, Sri Lanka, Bangladesh and Nepal), broadly construed, including but not limited to history, politics, ethnicity, and social groups.
Wikimania 2025 is happening in Nairobi, Kenya, and online from August 6 to August 9. This year marks 20 years of Wikimania. Interested users can join the online event. Registration for the virtual event is free and will remain open throughout Wikimania. You can register here now.
Yankees–Red Sox rivalry has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the reassessment page. If concerns are not addressed during the review period, the good article status may be removed from the article. Z1720 (talk) 14:01, 27 August 2025 (UTC)[reply]
go and read the original comment you deleted carefully where did I say the person should go kill themselves where did I call them stupid everything I said there was true and for their own benefits so they would stop doing something that leads to their own destruction but apparently you don't actually care about that and probably think I'm attacking you because I'm saying you're wrong sorry you're feelings were hurt that someone actually thinks that someone else is wrong for once but maybe they are 149.154.10.161 (talk) 22:01, 30 August 2025 (UTC)[reply]
Nominations for the upcoming Wikipedia:WikiProject Military history coordinator election have opened. A team of up to ten coordinators will be elected for the next coordination year. The project coordinators are the designated points of contact for issues concerning the project, and are responsible for maintaining our internal structure and processes. They do not, however, have any authority over article content or editor conduct, or any other special powers. More information on being a coordinator is available here. If you are interested in running, please sign up here by 23:59 UTC on 14 September! Voting will commence on 15 September. If you have any questions, you can contact any member of the current coord team. MediaWiki message delivery (talk) 00:03, 1 September 2025 (UTC)[reply]
An RfC is open on whether use of emojis with no encyclopedic value in mainspace and draftspace (e.g., at the start of paragraphs or in place of bullet points) should be added as a criterion under G15.
An RfC is in progress to amend the structure, rules, and procedures of the Arbitration Committee election and resolve any issues not covered by existing rules.
Hey there LuK3, I'd like to wish you a happy adminship anniversary! Congratulations on your special day, and thank you for all the contributions you've made.
After a motion, arbitration enforcement page protections no longer need to be logged in the AELOG. A bot now automatically posts protections at WP:AELOG/P. To facilitate this bot, protection summaries must include a link to the relevant CT page (e.g. [[WP:CT/BLP]]), and you will receive talk page reminders if you forget to specify the contentious topic but otherwise indicate it is an AE action.
Hello, LuK3. 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)
Cabayi (talk) 14:34, 23 September 2020 (UTC).jpg?lang=en)
Got anything good? Tell us about your new, improved, old, or messed-up script here!
Featured script
Updated scripts
Newly maintained scripts
Improve a script
Requested scripts
Miscellaneous
New scripts
Administrator changes
Guideline and policy news
Technical news
Arbitration
Miscellaneous
Interface administrator changes
CheckUser changes
Enable the user info card
