User:Valereee/sandbox

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)

{{subst:template name|topic=cid}}

Please do not attack other editors. Comment on content, not on contributors. Personal attacks damage the community and deter users. Please stay cool and keep this in mind while editing. Thank you.

Liège waffles^[1]

Hoping someone will be willing to take a look at Horror film and the talk page there, where Andrzejbanas is exhibiting disruptive behavior issues include ownership, sealioning, refusing to accept consensus is against them, and refusing to revert their edits made against that consensus once it was pointed out to them. When an issue is addressed, they move to a new one, creating walls of text that keep accusing other editors of not being willing to continue discussing and explaining.

More information Extended content ...

Extended content

It started with this reversion, where they wrote in the edit summary there are certainly horror films set during Christmas, but without some page citation from that book, all the other articles just connect the dots that "here are a list of alternative Christmas films" or "here are some horror films set around Christmas time" without really isolating it as a genre. Here, after I'd found those page#s, they reverted again, this time saying I'd added the info back without addressing concerns, which wasn't true. Here argued that none of the sources that none of them describe it as a genre, which wasn't true, and in fact in the content they'd removed included a note I'd added quoting the book source calling it a genre three different times. Here that the genre wasn't well-defined. I pointed out that it doesn't have to be well-defined in order to exist, and that an entire book of essays about the genre had been published by an established publisher. Here that they didn't find the book's arguments convincing. Here argued "seems irregularly represented against other horror cycles here such as the slasher, teen horror film, or the slasher." I pointed out that Teen horror doesn't even exist except as a redirect. Here told me that if I didn't even know what a genre cycle was, I shouldn't be trying to write about film. Here said calling it a genre was FRINGE. Here that nothing in the sources provided any value to the reader. I pointed out that my proposed addition told the reader The essential understanding readers take away is that horror includes a subgenre of Christmas horror. It seems to have a history, to have emerged as a genre fifty years ago and have been referred to as a subgenre as recently as two years ago. Those are things readers may want to know about the overall genre. Here that they never heard the term in common use. Here that an entire book of essays about the genre published by an established publisher wasn't sufficient to show the genre existed, saying, I repeat, this is not a substantial sub-genre, despite there being a book by a non-academic on the topic. Here that other than the book, there were only listicles. I pointed out that NPR and Hollywood Reporter both were calling it a genre or subgenre and giving it lengthy treatment. Here that they'd found errors in books by that publisher and implied NPR and HR were well-disguised listicle content. Which is not true, both describe the genre and its appeal at length. The fact they mention multiple highly-regarded examples does not make those articles listicles. Here circled back to that there was nothing in the three sources that provided valuable information. Twice. At this point, two other editors came in and agreed it was a legitimate genre. To which they responded, I'm not saying that there isn't such a genre, but due to it's sort of wobbly discussion, there is no real way to make it stand on it's own as it hasn't received critical attention. This is why I'm iffy on including it here, and not calling for a removal on the article or anything on it's own. The discussion isn't so much if it's real or not anymore, it's how we can include it here with saying something that gives the genre prominence. As I can't even write that on my own (and I've tried), I'm not sure what the best method is to include it. Which seems pretty WP:OWNy -- if they can't write it, it doesn't go in?

Close

GI60 then proposed entirely new language, which I supported, and Andrjez started the whole rigamarole over with that proposal. GI60 at that point agreed that he and I had done our due diligence and his third opinion provided consensus, and we added the language, and Andrjez reverted again saying there was no consensus. Then he said he hadn't seen the discussion between me and GI60, but still didn't revert himself after being asked multiple times on my talk, his talk, and the article talk. And he's still arguing that neither of us has explained what the issue is and that I'm dodging his questions. The whole thing could be another dozen diffs.