User talk:slakr
 | slakr's life is usually frolicking with chaos, so his activity and response times to queries can be highly variable. Leave a message and he will respond whenever he gets a chance— that is, assuming he gets a chance. Cheers =)
zOMG!!! I need urgent assistance!!!1!! — banana? — kiwi? |
 | Welcome to my talk page. Please sign your entries by inserting ~~~~ at the end. Click here to start a new talk topic |
Ideally, please use this link to post new messages at the bottom. If you can't find something you recently posted, I might have moved it down there or it could have been archived if you posted it over 7 days ago. Cheers :)
| Frequently Asked Questions (FAQ) | |
|
Regarding slakr: Why did my page get deleted?
Please see Wikipedia:Why was my page deleted? first. I have no idea what you're talking about. What's vandalism?
If you received a warning from me and you're not logged in, you might have gotten an old warning I sent to someone who shares your IP address. On the other hand, if you've made recent edits and received a recent warning message from me and you genuinely believe that it's not vandalism, don't fret-- simply drop me a message below, because I could have simply made a silly mistake. :) Regarding SineBot: Why does SineBot keep signing stuff I've already signed?
All comments should have a signature that includes both a link to your user page (slakr) and a datestamp (05:12, 20 August 2007 (UTC)) (per signatures - internal links). This is most easily generated by placing four tildes (~~~~) at the end of your contributions, which makes something like "slakr 05:12, 20 August 2007 (UTC)".
If you have an interwiki-linked user page, consider either creating a user page on enwiki that redirects to your preferred home wiki or simply opting out of automatic signing. If you're still having problems after trying that, post a message below. Be sure to include diffs to make sure I can reference the problem. I don't want my comments signed by SineBot. How do I get it to ignore me or my talk page?
Please use one of the opt-out methods listed on its user page. SineBot forgot to sign something it should have signed.
Usually this happens because the bot isn't sure if it really should sign something, so it defaults to not signing it (e.g., in cases of complex edits). It does this to avoid being annoying. Other times, a comment might be made when the bot is down for maintenance, so the bot simply never sees it. SineBot signed something that it genuinely should not have signed.
Please let me know-- especially if you think it's not a one-time thing. Be sure to include diffs to make sure I can reference the problem. Is SineBot's source code available?
Not currently. I'm signing with four tildes (~~~~) but it's still saying I didn't!
You likely enabled raw signatures. Open your preferences, click the "User profile" tab, make sure that "Treat the above as wiki markup" is NOT checked, and click Save; it should be fixed. If you have an interwiki-linked user page, consider either creating a user page on enwiki that redirects to your preferred home wiki or simply opting out of automatic signing. |
Galatta Plus
[edit]Could you please respond here where you have been pinged? You blacklisted a notable website which is run by a very notable individual. Kailash29792 (talk) 04:35, 18 August 2025 (UTC)
- I've been away for the past few days (and likely will be hit or miss for the next few weeks), but feel free to check the corresponding page's history to see who actually performed the action. Making use of tools like wikiblame can also help save time (and energy) in the future. --slakr\ talk / 01:38, 23 August 2025 (UTC)
Administrators' newsletter – September 2025
[edit]News and updates for administrators from the past month (August 2025).
Administrator changes
Interface administrator changes
Guideline and policy news
- 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.
Technical news
- Administrators can now access the Special:BlockedExternalDomains page from the Special:CommunityConfiguration list page. This makes it easier to find. T393240
Arbitration
- The arbitration case Article titles and capitalisation 2 has been closed.
- 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.
Administrators' newsletter – October 2025
[edit]News and updates for administrators from the past month (September 2025).
Administrator changes
CheckUser changes
Arbitration
- 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.
Discussion at AN about SineBot
[edit]Wikipedia:Administrators' noticeboard#SineBot, benign helper or closet vandal?. ScottishFinnishRadish (talk) 15:47, 10 October 2025 (UTC)
IP user #25208994 sockpuppet accusation
[edit]Hello dear Slakr, i recently saw that my account was blocked for being a suspected Sockpuppet of another IP user (IP adress: 89.205.128.0/17). This is not true, as i simply lost the password of my normal account (i can state the account if you want). Can you give me explanation and a picture of why you blocked me? Thank you for the reply beforehand. 46.244.62.112 (talk) 21:38, 28 October 2025 (UTC)
Guide to temporary accounts
[edit]Hello, Slakr. 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:47, 31 October 2025 (UTC)