User talk:Luk

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:13, 4 January 2022 (UTC)

22:53, 15 April 2022 (UTC)

Do I see a duck?   –Skywatcher68 (talk) 16:09, 14 August 2022 (UTC)

Very possible! In any case they don't seem to be here constructively so I blocked. Thx for the notice! -- Luk ^contrib 17:33, 14 August 2022 (UTC)

Hi, 2022–23 Liga Nacional de Guatemala has been moved to draft twice, once by me, once by another editor. This one was pasted verbatim from Draft:2022–23 Liga Nacional de Guatemala (2), complete with draft templates. Does that not come under CSD A10? Storchy (talk) 09:26, 15 August 2022 (UTC)

I'd say that since it's the same person who did the draft and the article, it's more akin to a copy paste where they used the draft to start up and "graduated" the article themselves. My reading of A10 is for articles that duplicate another article (and are not a split). I can delete the draft to save the people of AfC some time though. -- Luk ^contrib 09:54, 15 August 2022 (UTC)

Given that this user who you blocked is also abusing their talk page access (including making a now-reverted unblock request using racist language), I'd personally recommend revoking it. JeffSpaceman (talk) 12:30, 3 September 2023 (UTC)

 Done Thanks! -- Luk ^contrib 14:19, 3 September 2023 (UTC)

Hi, in agreement with Lahcen Ahansal, I have translated the page about him to English. French page: https://fr.wikipedia.org/wiki/Lahcen_Ahansal

My English translation: https://en.wikipedia.org/wiki/User:Emilie1111/Lahcen_Ahansal

However, as a new user I do not have the authorization to publish it as the official english translation for his page. The English currently redirects to the Marathon des Sables page (which he won 10 times) but I would like to request to replace that redirect with this translation. Thanks for your help! Emilie1111 (talk) 17:43, 5 January 2025 (UTC)

@Emilie1111: sorry I missed your message, I see that someone did it for you. Thanks for your help in improving Wikipedia! -- Luk ^contrib 12:25, 9 January 2025 (UTC)

Hello, Luk. 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?

• 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

• 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)
• See Wikipedia:Temporary account IP viewer § What can and can't be said for more detailed guidelines.

Useful tools for patrollers

• It is possible to view if a user has opted-in to view temporary account IPs via the User Info card, available in Preferences → Appearance → Advanced options → Enable the user info card
  • This feature also makes it possible for anyone to see the approximate count of temporary accounts active on the same IP address range.
• Special:IPContributions allows viewing all edits and temporary accounts connected to a specific IP address or IP range.
• Similarly, Special:GlobalContributions supports global search for a given temporary account's activity.
• The auto-reveal feature (see video below) allows users with the right permissions to automatically reveal all IP addresses for a limited time window.

Videos

• How to use Special:IPContributions
• How automatic IP reveal works
• How to use IP Info
• How to use User Info

Further information and discussion

• For more information and discussion regarding this change, please see the announcement from the Wikimedia Foundation at Wikipedia:Village pump (WMF) § Temporary accounts rollout.

Most of this message was written by Mz7 (source). Thanks, 🎃 SGrabarczuk (WMF) (talk) 02:48, 31 October 2025 (UTC)

Hello! I noticed you're a bot operator, so I thought you might be interested in a hackathon we're organizing: the Wikimedia Hackathon Northwestern Europe 2026, on 13–14 March in Arnhem, Netherlands.

It's a two-day, technically oriented hackathon bringing together Wikimedians from the region. Whether you want to work on bot frameworks, tools, or other technical projects, this could be a great opportunity to collaborate with fellow developers. Registration closes mid-January or when full. Let me know if there are any questions. Hope to see you there! Daanvr (talk) 08:58, 12 January 2026 (UTC)

@Daanvr: Hi! I'm not interested but best of luck! -- Luk ^contrib 19:12, 19 January 2026 (UTC)

The redirect Лeв Давидович Трóцкий has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 January 20 § Лeв Давидович Трóцкий until a consensus is reached. Mathguy2718 (talk) 04:31, 20 January 2026 (UTC)

News and updates for administrators from the past month (January 2026).

Administrator changes

Vacant0

• Crisco 1492

• Deepfriedokra
• Hbdragon88
• Karl Dickman
• Worm That Turned

CheckUser changes

Daniel Quinlan

Vanamonde93

Mkdw

Oversight changes

Daniel Quinlan

Arbitration

• Due to the result of a recent motion, a rough consensus of administrators at the arbitration enforcement noticeboard may impose an expanded topic ban on Israel, Israelis, Jews, Judaism, Palestine, Palestinians, Islam, and/or Arabs, if an editor's Arab-Israeli conflict topic ban is determined to be insufficient to prevent disruption. At least one diff per area expanded into should be cited.

Miscellaneous

• Voting in the 2026 Steward elections started on 06 February 2026 at 14:00 (UTC) and will end on 27 February 2026 at 14:00 (UTC). The confirmation process for current stewards is being held in parallel. You can automatically check your eligibility to vote.

News and updates for administrators from the past month (February 2026).

Administrator changes

• Brendanconway
• Calmer Waters
• Hut 8.5
• Joe Roe
• VersedFenrir

CheckUser changes

Ks0stm

Oversight changes

Ks0stm

Guideline and policy news

• Following an RfC, the web archival service archive.today has been deprecated; links to the site should be removed.
• A request for comment is open to discuss retiring CSD criterion R3 in favour of handling such redirects through RfD.

Arbitration

• Following a motion, remedy 9.1 of the Conduct in deletion-related editing case has been amended to limit TenPoundHammer to one XfD nomination or PROD per 24-hour period.
• Following a motion, the Iskandar323 further POV pushing motion has been rescinded.
• The Arbitration Committee has passed a housekeeping motion rescinding a number of outdated remedies and enforcement provisions across multiple legacy cases. In most instances, existing sanctions remain in force and continue to be appealable through the usual processes, while some case-specific remedies were amended or clarified.

Miscellaneous

• Following the 2026 Steward Elections, the following editors have been appointed as stewards: A09, AmandaNP, Barras, Count Count, M7, SHB2000, Teles and VIGNERON.
• An Unreferenced articles backlog drive is taking place in March 2026 to reduce the backlog of articles tagged with {{Unreferenced}}. You can help reduce the backlog by adding citations to these articles. Sign up to participate!