Welcome to my talk page. |
Archives |
Archive 1 ǀArchive 2 ǀArchive 3 ǀArchive 4 ǀArchive 5 ǀArchive 6 ǀArchive 7 ǀArchive 8 ǀArchive 9 ǀArchive 10 ǀArchive 11 ǀArchive 12 ǀArchive 13 ǀArchive 14 |
News and updates for administrators from the past month (April 2025).

Interface administrator changes
Thanks for blocking that IP block evader, looks like they're back again withDrew72828 (talk ·contribs ·deleted contribs ·nuke contribs ·logs ·filter log ·block user ·block log). Do you mind blocking them and protecting the page? I have filed AIV and RPP reports but that might take a bit and this vandal isn't stopping anytime soon. Cheers,GoldRomean (talk)19:19, 31 May 2025 (UTC)[reply]
News and updates for administrators from the past month (May 2025).
I warned IP editor User:50.104.26.15 to stop vandalizing various Wikipedia articles. After 3 times without change, and since you also warned this editor, I believe a longer block is appropriate in this case.CANthony0125 (talk)14:00, 19 June 2025 (UTC)[reply]
Hi, Paul! I believe the yearlong block on 97.112.192.0/18 by Daniel Case may have been miscalculated... blocking 16,384 usable IP addresses for an entire year takes out a majority of Brightspeed customers in south Alabama! Thanks for your help! God bless!2600:387:2:805:0:0:0:56 (talk)00:10, 28 June 2025 (UTC)[reply]
News and updates for administrators from the past month (June 2025).

Interface administrator changes
I don't usually say this to people, but you can be more harsh in your blocks when dealing with LTA vandals on proxies. If you're sure you've found a data center, web hosting service, or open proxy, you can hard block it. We don't want logged-in vandals using them, which is what often happens. Just be careful of doing hard blocks on anything else. They can cause a lot of collateral damage.NinjaRobotPirate (talk)14:13, 16 July 2025 (UTC)[reply]
HiPaul Erik! It's good to run into you as usual! I was patrolling recent logs and edits and saw the exact same thing that you saw with this LTA, and we both managed to block this user at the same time. I know that there were changes made recently around the blocking structure and how they now work, such as the ability to add more than one block to the same user and with different expirations, different types and options, and on different areas (partial vs site), etc. Apparently I was a "photo finish" faster than you, because it logged my block first followed by yours.
Take a look at the block loghere and maybe you'll be surprised to see what I'm seeing (or who knows, maybe not). Up until recently, this would be logged as me adding the block to the account, then your block would've overwritten mine and "updated it". I was surprised, however, to see that your indefinite site-wide block no longer overwrites the older one that I set. Instead, it addedanother site-wide indefinite block, and is now logged as"added a block for" instead of"updated block for". I saw this and then asked myself what would happen if I were to just remove one of them... and I did just that - removed your block as an ad-hoc "test" if anything (and also for procedural purposes, since seeing two blocks like that could cause confusion). The removal of one of the two blocks was logged as me "unblocking" the user account instead of "removed a block for"...
What gives? I totally see how being able to add more than one block to the same user would be necessary in relation to partial blocks and blocks that expire, but not two of the exact same block where it's set indefinitely and as a site-wide block. Have you seen this before? Something tells me that this shouldn't be expected nor how this should function. I would expect a second indefinite site-wide block to overwrite the previous one. Weird...
I will say that I used a script to query the API in order to apply the block to that account. Maybe we're now relying on the newSpecial:Block interface to tell us that this isn't going to work? I haven't tested that... Anyways, what do you think about all this? I guessWP:WHEEL would no longer be possible in this exact situation since you technically added another block and didn't change mine? In that case, HA! We can just add a mess load of the same block over and over and make a huge ridiculous list! :-P~Oshwah~(talk)(contribs)21:48, 30 July 2025 (UTC)[reply]
News and updates for administrators from the past month (July 2025).
All pages related to the region ofSouth Asia (India, Pakistan, Afghanistan, Sri Lanka, Bangladesh and Nepal), broadly construed, including but not limited to history, politics, ethnicity, and social groups.
News and updates for administrators from the past month (August 2025).
Thanks for dealing with that vandal, keep up the good work!Throwaway200976 (talk)03:29, 16 September 2025 (UTC)[reply]
News and updates for administrators from the past month (September 2025).

[[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.Sorry for the rollback, which I’ve self-reverted: I agree with your assessment and the series of reverts had me confused which way you were going, I thought you were doing the opposite!Kingsif (talk)12:26, 22 October 2025 (UTC)[reply]