Contents
Stephen Breyer
Hi 49TL! I hope you're having a great weekend. I noticed that you blocked the 2600:1015:B125:E4E2:B4F2::/64 range (perfect!), but after blocking each individual IP from that range for evasion. I just wanted to let you know that I removed the individual IP blocks you placed so that the /64 range block you placed would take care of them all. It makes it easy in case we were to need to remove that /64 range block, or extend it to a wider range (we would just unblock the /64 range and apply a wider block, etc). If you have any questions, let me know. Cheers ;-) ~Oshwah~(talk) (contribs) 23:29, 10 February 2019 (UTC)
- Hey @Oshwah:, thanks for that. Are there any pages that discuss best practice for range blocks (such as unblocking the individual IPs afterwards)? I've searched but can't find much. 49 TL 09:41, 11 February 2019 (UTC)
- You're quite welcome! :-) Other than the pages that have the in-depth technical information about what IP ranges are and how CIDR notation works, there really isn't much. I've had to apply some best practices from what I've learned from making them myself after making many range blocks and from helping other admins with ranges. One recent example is on my user talk page here, where I helped a group of admins by walking them through how to check for collateral damage. Even they agreed that instructions and pages with best practices regarding range blocking is very lacking here. I do what I can to help though; I've put creating or adding this information to the appropriate place on my to-do list. When it gets done is up in the air; I have a lot of different projects and daily tasks on my plate where getting things on my to-do list completed has been going pretty slow... ~Oshwah~(talk) (contribs) 09:49, 11 February 2019 (UTC)
- @Oshwah: Good read, thanks! I'm encouraged to see my pre-block checks are pretty much in line with yours. Will definitely bear in mind removing the original blocks in future. 49 TL 19:07, 11 February 2019 (UTC)
- You bet; always happy to help. :-) And again, removing individual blocks placed after extending a block to a range isn't absolutely urgent or crucial... but I can tell you that it makes life a lot easier. It changes the block for each individual IP to inherit the block placed on the range, which means that all of the blocks are set to the same expiration, and if you have to extend the block to a wider range - you just unblock the first range and then apply a block to the wider one. Or, if you find that you need to remove the entire block for any reason - you just need to remove the one block as opposed to having to rush and search through range contribs, block logs, etc and hope that you unblock them all. Just little things like that... the small conveniences and advantages definitely add up as you apply and manage more range blocks for various and unrelated things - lol. I'm glad that my input was of some inspiration and use to you. If you need me for anything else, you know where to find me. ;-) Cheers - ~Oshwah~(talk) (contribs) 19:18, 11 February 2019 (UTC)
- @Oshwah: Good read, thanks! I'm encouraged to see my pre-block checks are pretty much in line with yours. Will definitely bear in mind removing the original blocks in future. 49 TL 19:07, 11 February 2019 (UTC)
- You're quite welcome! :-) Other than the pages that have the in-depth technical information about what IP ranges are and how CIDR notation works, there really isn't much. I've had to apply some best practices from what I've learned from making them myself after making many range blocks and from helping other admins with ranges. One recent example is on my user talk page here, where I helped a group of admins by walking them through how to check for collateral damage. Even they agreed that instructions and pages with best practices regarding range blocking is very lacking here. I do what I can to help though; I've put creating or adding this information to the appropriate place on my to-do list. When it gets done is up in the air; I have a lot of different projects and daily tasks on my plate where getting things on my to-do list completed has been going pretty slow... ~Oshwah~(talk) (contribs) 09:49, 11 February 2019 (UTC)
Wanda Nara
Hello, 49TL! Thanks for defending the article Wanda Nara. Someone listed it at RfPP. I semi-protected it for a week, and I revision-deleted the grossly inappropriate stuff. I think I got it all, but please check to see if I missed anything. -- MelanieN (talk) 21:58, 17 February 2019 (UTC)
- Hey, thanks. Looks like you got them all. I've done a bit of reading on revision deletion and will remember to clean up next time :) 49 TL 22:27, 17 February 2019 (UTC)
- Yeah, with BLPs it's important to not just revert that kind of stuff but to get it out of the history as well. Sometimes you have to rev-del a dozen perfectly innocent edits between the vandalism and the revert, because the intervening edits display the vandalism too. It would sure be nice if some of these jerks would get a new hobby. :-( -- MelanieN (talk) 22:36, 17 February 2019 (UTC)
- And welcome back, admin. We appreciate the help. I saw you revdeleted that offensive username: thanks. Drmies (talk) 18:45, 21 February 2019 (UTC)
- Thanks, I appreciate the note. There's a decent amount of new stuff around since I was last properly active, but I think I'm getting the hang of it again! 49 TL 18:54, 21 February 2019 (UTC)
Indian Air Force
Hey, I saw you changed visibility of some revisions on Indian Air Force and Future of the Indian Air Force due to RD3. Can you please take a look at List of active Indian military aircraft for similar issue? Thanks —Sarvatra (talk, contribs) 06:39, 26 February 2019 (UTC)
- Hey there, I've just had a look through the edits from the past couple of days and can't see anything that would usually meet the revision deletion criteria. From what I can tell, it seems like "standard" vandalism, but let me know if I've missed anything or need to look back further. 49 TL 07:40, 26 February 2019 (UTC)
Administrators' newsletter – March 2019
News and updates for administrators from the past month (February 2019).
Interface administrator changes
|
|
- The RfC on administrator activity requirements failed to reach consensus for any proposal.
- Following discussions at the Bureaucrats' noticeboard and Wikipedia talk:Administrators, an earlier change to the restoration of adminship policy was reverted. If requested, bureaucrats will not restore administrator permissions removed due to inactivity if there have been five years without a logged administrator action; this "five year rule" does not apply to permissions removed voluntarily.
- A new tool is available to help determine if a given IP is an open proxy/VPN/webhost/compromised host.
- The Arbitration Committee announced two new OTRS queues. Both are meant solely for cases involving private information; other cases will continue to be handled at the appropriate venues (e.g., WP:COIN or WP:SPI).
- paid-en-wpwikipedia.org has been set up to receive private evidence related to abusive paid editing.
- checkuser-en-wpwikipedia.org has been set up to receive private requests for CheckUser. For instance, requests for IP block exemption for anonymous proxy editing should now be sent to this address instead of the functionaries-en list.
- The Arbitration Committee announced two new OTRS queues. Both are meant solely for cases involving private information; other cases will continue to be handled at the appropriate venues (e.g., WP:COIN or WP:SPI).
- Following the 2019 Steward Elections, the following editors have been appointed as stewards: Base, Einsbor, Jon Kolbert, Schniggendiller, and Wim b.
The Signpost: 31 March 2019
- From the editors: Getting serious about humor
- News and notes: Blackouts fail to stop EU Copyright Directive
- In the media: Women's history month
- Discussion report: Portal debates continue, Prespa agreement aftermath, WMF seeks a rebranding
- Featured content: Out of this world
- Arbitration report: The Tides of March at ARBCOM
- Traffic report: Exultations and tribulations
- Technology report: New section suggestions and sitewide styles
- News from the WMF: The WMF's take on the new EU Copyright Directive
- Recent research: Barnstar-like awards increase new editor retention
- From the archives: Esperanza organization disbanded after deletion discussion
- Humour: The Epistolary of Arthur 37
- In focus: The Wikipedia SourceWatch
- Special report: Wiki Loves (50 Years of) Pride
- Community view: Wikipedia's response to the New Zealand mosque shootings