Special:Log/checkuser-temporary-account. Shortcut WP:TAIVDISCLOSEWP:TAIVDISCLOSE It is never a violation of the TAIV disclosure policy to make a statement...
Click to read more »they become unnecessary (instead requiring only their removal). See WP:TAIVDISCLOSE for more information. Following the 2025 Arbitration Committee elections...
Click to read more »claims. Clerk declined CheckUser request, as the WP:CUTADISCLOSE and WP:TAIVDISCLOSE policies prevent checkusers from publicly linking registered accounts...
Click to read more »they become unnecessary (instead requiring only their removal). See WP:TAIVDISCLOSE for more information. Arbitration Following the 2025 Arbitration Committee...
Click to read more »January 2026 (UTC) @TarnishedPath: yes, see the last bullet point of WP:TAIVDISCLOSE. Since TAIV links temp accounts -> IPs, and you're requesting CU to provide...
Click to read more »acknowledging that you won't be able to confirm having done so per WP:TAIVDISCLOSE. MCE89 (talk) 15:26, 24 May 2026 (UTC) Requested actions completed, closing...
Click to read more »tags ~2026-19287-37 per behavioral evidence and WP:TAIV data. Per WP:TAIVDISCLOSE, I am unable to specifically comment on any related IP address blocks...
Click to read more »recurring problem, but it is challenging to identify a good solution. Per WP:TAIVDISCLOSE, I am unable to comment on whether WP:TAIV data associates the temporary...
Click to read more »Esedullahhh-created Draft:Shi'a views on face-veiling on 2 November 2025. Per WP:TAIVDISCLOSE, I am unable to publicly disclose whether WP:TAIV data associates ~2026-61953-0...
Click to read more »Tools: Editor interaction utility · Interaction Timeline · SPI Tools (WP:TAIVDISCLOSE) Appears to be block evasion, a different /8 range, but ISP and general...
Click to read more »fulfill the request of the editor who wishes to be scanned. Also, WP:TAIVDISCLOSE prevents checkusers from publicly linking registered accounts to temporary...
Click to read more »Tools: Editor interaction utility · Interaction Timeline · SPI Tools (WP:TAIVDISCLOSE) WP:DUCK, editing exclusively in the same topic area as a related TA...
Click to read more »From a purely behavioral standpoint (i.e. under bullet point 1 of WP:TAIVDISCLOSE), it appears to me that KorFlyer88 has been editing while logged out...
Click to read more »range that appears to have been obtained from the WP:TAIV permission. WP:TAIVDISCLOSE states that the disclosure is allowed when "reasonably believed to be...
Click to read more »from a trace may not be provided publicly except as permitted under WP:TAIVDISCLOSE. The following is a list of tools and resources available for those who...
Click to read more »[16]), es:Durango ([17][18][19][20] vs. [21], despite [22]). Per WP:TAIVDISCLOSE, I cannot publicly disclose the extent to which WP:TAIV data associates...
Click to read more »area. I'm not going to mention them here to avoid running afoul of WP:TAIVDISCLOSE, but ask that clerks/CUs examine them as well. As I don't believe this...
Click to read more »addendum, which I have deleted before filing this case to satisfy WP:TAIVDISCLOSE. — Newslinger talk 23:46, 19 February 2026 (UTC) Clarifying for the record...
Click to read more »suppose it is okay to tag them provided that doing so does not violate WP:TAIVDISCLOSE or WP:CUIPDISCLOSE (in this case it was fine to tag because the TA-to-account...
Click to read more »data which connects the temporary accounts with one another. Per WP:TAIVDISCLOSE, I am unable to comment on whether these temporary accounts are technically...
Click to read more »acknowledging that you won't be able to confirm having done so per WP:TAIVDISCLOSE. MCE89 (talk) 08:27, 31 May 2026 (UTC) Requested actions completed, closing...
Click to read more »won't be able to disclose publicly whether or not you've done so per WP:TAIVDISCLOSE. MCE89 (talk) 13:55, 5 May 2026 (UTC) Blocked without tags all listed...
Click to read more »tags ~2026-31144-00 per behavioral evidence and WP:TAIV data. Per WP:TAIVDISCLOSE, I am unable to specifically comment on any related IP address blocks...
Click to read more »(acknowledging that you won't be able to confirm having done so per WP:TAIVDISCLOSE). MCE89 (talk) 12:10, 6 May 2026 (UTC) Blocked without tags all listed...
Click to read more »blocks made in relation to this case should not be disclosed per the WP:TAIVDISCLOSE policy. Staraction (talk · contribs) 18:00, 25 May 2026 (UTC) Blocked...
Click to read more »previously involved. Vestigia Leonis (talk) 12:27, 17 November 2025 (UTC) (WP:TAIVDISCLOSE) TA-Cluster1 raised concerns about sock puppets at Talk:Forspoken. While...
Click to read more »[Kepler-1229b's comment moved to appropriate section] @Kepler-1229b: Per WP:TAIVDISCLOSE, I am unable to specifically comment on any IP address blocks, but I...
Click to read more »Category:Suspected Wikipedia sockpuppets of ~2025-34848-32 for the full list. Per WP:TAIVDISCLOSE, I am unable to specifically comment on any related IP address blocks...
Click to read more »(acknowledging that confirmation of such a block will not be given per WP:TAIVDISCLOSE. User:Swordfish121,641, thanks for the report, although feel free to...
Click to read more »(acknowledging that you won't be able to disclose having done so per WP:TAIVDISCLOSE). MCE89 (talk) 10:45, 9 June 2026 (UTC) Blocked without tags. Closing...
Click to read more »investigate · cuwiki · SI) per behavioral evidence and WP:TAIV data. Per WP:TAIVDISCLOSE, I am unable to specifically comment on any related IP address blocks...
Click to read more »to avoid an appearance of impropriety. This is cautioned about at WP:TAIVDISCLOSE: TAIVs should take care not to give the impression that they are inappropriately...
Click to read more »MCE89 (talk) 13:13, 8 June 2026 (UTC) Blocked without tags. Per WP:TAIVDISCLOSE, I am unable to specifically comment on any related IP address blocks...
Click to read more »23:12, 28 July 2026 (UTC) Blocked without tags ~2026-40259-24. Per WP:TAIVDISCLOSE, I am unable to specifically comment on any related IP address blocks...
Click to read more »wants to do that, I'll repeat the suggestion I included in a footnote at TAIVDISCLOSE that they do the disclosure on a transcluded subpage, so that it can...
Click to read more »GiftedIceCream 17:25, 26 March 2026 (UTC) @SuperPianoMan9167: Per WP:TAIVDISCLOSE, you are not allowed to reveal the IP address of a TA. --Prothe1st (leave...
Click to read more »block log · CA · CheckUser(log) · investigate · cuwiki · SI) Per WP:TAIVDISCLOSE, I am unable to specifically comment on any IP address blocks, but I...
Click to read more »they become unnecessary (instead requiring only their removal). See WP:TAIVDISCLOSE for more information. Arbitration Following the 2025 Arbitration Committee...
Click to read more »agreeing to the Access to Temporary Account IP Addresses Policy, and WP:TAIVDISCLOSE summarises what information can be disclosed to others. As you are a...
Click to read more »have to bring out a bloody thesaurus to actually report it because WP:TAIVDISCLOSE is obtusely restrictive in being able to even mention an IP address....
Click to read more »behaviour? Ifly6 (talk) 20:32, 31 March 2026 (UTC) Indeed it is (see WP:TAIVDISCLOSE if you'd like to read more). Please see ~2026-19399-63, ~2026-19533-29...
Click to read more »(talk) 13:45, 24 May 2026 (UTC) If you read the full sub-bullet in WP:TAIVDISCLOSE, country information is explicitly listed as a generally permissible...
Click to read more »tie a IP addressed to a named account. See the last dot point of WP:TAIVDISCLOSE TarnishedPathtalk 00:24, 29 January 2026 (UTC) That answer is irrelevant...
Click to read more »Vorbis (carbon • videos) 23:33, 7 May 2026 (UTC) (Non-administrator comment) (WP:TAIVDISCLOSE) Looking at the related TAs, and specifically this talk page message...
Click to read more »