User talk:ST47/Archive25
This is a Wikipedia user talk page.
If you find this page on any site other than Wikipedia, you are viewing a mirror site. Be aware that the page may be outdated, and that the user this page belongs to may have no personal affiliation with any site other than Wikipedia itself. The original page is located at http://en.wikipedia.org/wiki/User_talk:ST47. |
The Signpost: 29 August 2021
[edit]- News and notes: Enough time left to vote! IP ban
- In the media: Vive la différence!
- Wikimedians of the year: Seven Wikimedians of the year
- Gallery: Our community in 20 graphs
- News from Wiki Education: Changing the face of Wikipedia
- Recent research: IP editors, inclusiveness and empathy, cyclones, and world heritage
- WikiProject report: WikiProject Days of the Year Interview
- Traffic report: Olympics, movies, and Afghanistan
- Community view: Making Olympic history on Wikipedia
LTA again?
[edit]After the recent incident with LTA "Best known for", I have now the idea that there is a new incarnation. See here. Am I correct with that? The Banner talk 11:52, 30 August 2021 (UTC)
- @The Banner: Possibly. It's some kind of proxy, I've blocked it accordingly. ST47 (talk) 01:19, 31 August 2021 (UTC)
- Thank you very much. The Banner talk 07:11, 31 August 2021 (UTC)
Administrators' newsletter – September 2021
[edit]News and updates for administrators from the past month (August 2021).
- Feedback is requested on the Universal Code of Conduct enforcement draft by the Universal Code of Conduct Phase 2 drafting committee.
- A RfC is open on whether to allow administrators to use extended confirmed protection on high-risk templates.
- A discussion is open to decide when, if ever, should discord logs be eligible for removal when posted onwiki (including whether to oversight them)
- A RfC on the next steps after the trial of pending changes on TFAs has resulted in a 30 day trial of automatic semi protection for TFAs.
- The Score extension has been re-enabled on public wikis. It has been updated, but has been placed in safe mode to address unresolved security issues. Further information on the security issues can be found on the mediawiki page.
- A request for comment is in progress to provide an opportunity to amend the structure, rules, and procedures of the Arbitration Committee election and resolve any issues not covered by existing rules. Comments and new proposals are welcome.
- The 2021 RfA review is now open for comments.
Wholesale AS Blocking
[edit]I encountered an unblock request today regarding an IP in the 192.190.255.0/24 range.
This range is owned by Aerosurf, a residential ISP, and resides on AS6939 - which is owned by Hurricane Electric.
I've found other residential ISP's in that AS, such as 208.75.96.0/21, which belongs to Wicked Broadband, and is also blocked.
Just skimming, I also see "Central Utah Telecom", "Exwire" (which I believe is now Oasis Broadband), "S. Bryer Cable TV Corporation", "JTM Broadband, LLC", "SOS Communications LLC", "TENNESSEE WIRELESS LLC", and I'm sure there are other ranges that I've missed. You've blocked all of these.
Would you mind taking a look at this AS, and lifting your blocks on ranges that appear to be residential ISP's, please? SQLQuery Me! 23:12, 6 September 2021 (UTC)
IPBE request
[edit]Hello, ST47. I still live in mainland China, but my IPBE will expire. Can you grant me another one? (It will be better if you grant me a permanent IPBE) Thanks!--波斯波莉斯 (talk) 00:09, 9 September 2021 (UTC)
- (talk page stalker)@波斯波莉斯:, I have gone ahead and renewed your ipbe for another year. We generally do not (and should not) issue that user right permanently. SQLQuery Me! 11:12, 9 September 2021 (UTC)
Neha Yadav
[edit]As you are already involved, so I am updating you to avoid a mistake. A user redirected Neha Yadav to a TV show, but I undo. I don't see the logic to create a page from a different name and wasting the name in the redirect. Sonofstar (talk) 12:47, 9 September 2021 (UTC)
- @Sonofstar: What you are doing is known as redirect hijacking. You can't just remove the redirect from an article and turned it about a different subject (likely non-notable as per WP:NPOL) so please stop this practice (see WP:GAMING as well as WP:ADMINSHOP). GSS 💬 18:17, 10 September 2021 (UTC)
Proxy?
[edit]Special:contributions/81.177.3.8.--Bbb23 (talk) 16:54, 18 September 2021 (UTC)
- (talk page watcher) @Bbb23: Appears to be this web hosting service, and seems to be running Squid. In short: Yes. See this too, in case you haven't seen yet. --Blablubbs (talk) 17:12, 18 September 2021 (UTC)
- @Blablubbs: Thanks. Some of what you say is beyond me, but it's not clear to me why, after 81. acknowledged that Special:contributions/31.41.45.190 was him, he was allowed to continue because of his "good contributions". I also remain suspicious that he hasn't always edited just with IPs, proxies or otherwise.--Bbb23 (talk) 17:25, 18 September 2021 (UTC)
- I mean I know working SPI just sucks all the AGF out of ya, but sheesh. Look I've been pretty open about how I operate for a long time. I tether through mobile, when the idiots get those ranges blocked I turn on one app or another to continue editing, preferably one that slows things down the least. I'm not that technically proficient some of those ranges are blockable under policy, others probably aren't (I don't believe content filtering ones are). Most don't assign static IPs, but when I find ones that do I'll tend to hang around on them to make things easier for others, but there's always additional options. So look if you need to block a range just block it, it doesn't stop me from editing it just means my history isn't in one place, no big deal, abuse does happen on these ranges, I understand in full. If I'm in the middle of a collaboration (I'm not right now) then an advance talk page notice is polite. But at this point WP:DGAF is my middle name. If you know my writing style, and it is quite distinctive, I'm sure you can go back a very long way if my history is of interest to you.Balls in your court, I was going to try to keep things under this IP over the weekend, but I'll probably be shifting back over to random article patrol, so I doubt it matters much, sorry for the trouble. Regards, 81.177.3.8 (talk) 18:01, 18 September 2021 (UTC)
- @Bbb23: My read of policy is that while proxies may be blocked on sight, editing via a proxy isn't prohibited, and hence the block on 31.41.40.0/21 is essentially a block just on an IP range, not on any specific user. The technical tl;dr is that in my opinion, 81.177.3.0/24 is fine to hardblock. The only reason I haven't done so is because I haven't read the ANI discussion and I'm not sure whether I would disrupt an ongoing conversation by rangeblocking right now. --Blablubbs (talk) 18:03, 18 September 2021 (UTC)
- @Blablubbs: The ANI discussion is about the IP. I'm not sure what use it is or why it should prevent a proxy block. If anything, it should trigger one. Although the block of 31. may not be imposed "on any specific user", the edits by IP 81. are clear block evasion. The proxy part only compounds the problem. My suspicious is that even if we were to block the proxy, the person would just jump to yet another proxy, but just as with all blocks, that shouldn't stop us.--Bbb23 (talk) 18:14, 18 September 2021 (UTC)
- @Bbb23: my understanding was that it's not evasion if the block is not directed at you as a person. However, if the conclusion of the ANI is that I the person (not the IP address) need a time-out then I will abide by it. Hell, If I screwed up something big and someone I trust told me to stay away for 6 months I'd do so, no need to block. All I ask is that you clearly denote in the log how long a block is directed at me, and how long at the address itself. Regards, 81.177.3.8 (talk) 18:19, 18 September 2021 (UTC)
- @Blablubbs: The ANI discussion is about the IP. I'm not sure what use it is or why it should prevent a proxy block. If anything, it should trigger one. Although the block of 31. may not be imposed "on any specific user", the edits by IP 81. are clear block evasion. The proxy part only compounds the problem. My suspicious is that even if we were to block the proxy, the person would just jump to yet another proxy, but just as with all blocks, that shouldn't stop us.--Bbb23 (talk) 18:14, 18 September 2021 (UTC)
- @Blablubbs: Thanks. Some of what you say is beyond me, but it's not clear to me why, after 81. acknowledged that Special:contributions/31.41.45.190 was him, he was allowed to continue because of his "good contributions". I also remain suspicious that he hasn't always edited just with IPs, proxies or otherwise.--Bbb23 (talk) 17:25, 18 September 2021 (UTC)
The Signpost: 26 September 2021
[edit]- News and notes: New CEO, new board members, China bans
- In the media: The future of Wikipedia
- Op-Ed: I've been desysopped
- Disinformation report: Paid promotional paragraphs in German parliamentary pages
- Discussion report: Editors discuss Wikipedia's vetting process for administrators
- Recent research: Wikipedia images for machine learning; Experiment justifies Wikipedia's high search rankings
- Community view: Is writing Wikipedia like making a quilt?
- Traffic report: Kanye, Emma Raducanu and 9/11
- News from Diff: Welcome to the first grantees of the Knowledge Equity Fund
- WikiProject report: The Random and the Beautiful
SPI query
[edit]Hello, ST47,
Several pages created by User:A.A Prinon have been tagged CSD G5 but hours have passed with no admin taking action on them. I know that I haven't because it's unclear to me whether this editor was evading a block when he created them. Reading over the SPI case, it looks like he was initially cleared of being a sockpuppet before he was blocked for harassment and is only now confirmed to be socking. In that case, CSD G5 wouldn't apply to the articles he created but I thought since you closed this case I'd check with you before removing the CSD tags. Is this your understanding of the sequence of events? Many thanks! Liz Read! Talk! 02:30, 29 September 2021 (UTC)
- @Liz: It looks like in the May 2021 case, Cambria Math was confirmed to be A.A Prinon, but A.A Prinon was unblocked subject to a 1 account restriction. Any pages created by a sock after A.A Prinon's indef block for harassment on 11 July 2021 would be eligible for G5, but pages created before then would not. At the moment, it looks to me like anything eligible for G5 has already been deleted. Do you know of any pages that still need a decision? ST47 (talk) 02:43, 30 September 2021 (UTC)
New message from Vanjagenije
[edit]Message added 22:18, 30 September 2021 (UTC). You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
Vanjagenije (talk) 22:18, 30 September 2021 (UTC)
Administrators' newsletter – October 2021
[edit]News and updates for administrators from the past month (September 2021).
- Following an RfC, extended confirmed protection may be used preemptively on certain high-risk templates.
- Following a discussion at the Village Pump, there is consensus to treat discord logs the same as IRC logs. This means that discord logs will be oversighted if posted onwiki.
- DiscussionTools has superseded Enterprisey's reply-link script. Editors may switch using the "Discussion tools" checkbox under Preferences → Beta features.
- A motion has standardised the 500/30 (extended confirmed) restrictions placed by the Arbitration Committee. The standardised restriction is now listed in the Arbitration Committee's procedures.
- Following the closure of the Iranian politics case, standard discretionary sanctions are authorized for all edits about, and all pages related to, post-1978 Iranian politics, broadly construed.
- The Arbitration Committee encourages uninvolved administrators to use the discretionary sanctions procedure in topic areas where it is authorised to facilitate consensus in RfCs. This includes, but is not limited to, enforcing sectioned comments, word/diff limits and moratoriums on a particular topic from being brought in an RfC for up to a year.
- Editors have approved expanding the trial of Growth Features from 2% of new accounts to 25%, and the share of newcomers getting mentorship from 2% to 5%. Experienced editors are invited to add themselves to the mentor list.
- The community consultation phase of the 2021 CheckUser and Oversight appointments process is open for editors to provide comments and ask questions to candidates.
Unblock request
[edit]Hello, I am a Wikimedia projects editor, a recruiter and trainer for new editors and a program lead for Wikimedia Ghana User Group’s Community Development Program, which looks to improve the retention rate of new and experienced editors. We have an upcoming online workshop for new editors which is due this Friday, September 24, 2021. Due to the open proxy block, new participants in Ghana who want to join the workshop can create accounts and this has made it difficult to onboard them. I kindly request a temporal IP lift to enable new editors to join the workshop. The IP is (disabled) by ST47ProxyBot where most of them(participants) say their network provider is in control over the proxy. Hope to hear from you soon. Find the event dashboard here https://outreachdashboard.wmflabs.org/courses/Wikimedia_Ghana_User_Group/Online_Wikipedia_Workshop,_September_24,2021?enroll= Thank you Robertjamal12 (talk) 13:25, 22 September 2021 (UTC)
Hi @User:ST47,
We are hosting a workshop today for newbies who would be learning how to edit Wikipedia articles find dashboard here [1] and the IP: 154.160.14.59 has been disabled by you. I sent an emergency email to the Stewards and I was asked to reach out to you since you where the one who put the block on there. This was the message I got "The quickest solution would be to ask User:ST47 to lift the block for the day and to add a local exception to the global block" after I sent the email.
I would be happy if you can look into this for me and help me because we risk not getting maximum participation from our participants should the block still be in force.
Thank You.
Owula kpakpo (talk) 07:48, 2 October 2021 (UTC)
Another chance?
[edit]Hi there. I do think that Mint69 perhaps deserves another chance. He has admitted guilt and taken responsibility and not tried to shift blame elsewhere. The thing is, he did create some good articles while he was active on the website, unlike a lot of other new users, the articles he created were actually well written and passed GNG. Plus, I think now he has learnt his lesson. Perhaps he deserves another chance and can be watched closely? Just wanted to share my thoughts on the matter. Thanks. Inexpiable (talk) 18:26, 2 October 2021 (UTC)
Temporal unblock request
[edit]Hi, I am a Wikimedia projects editor, a recruiter and trainer for new editors and a program lead for Wikimedia Ghana User Group’s Community Development Program, which looks to improve the retention rate of new and experienced editors. We have an upcoming workshop for new and experienced editors which is due this Saturday, October 9, 2021, in one of the major cities in Ghana. Editing from any IP in the city is blocked by you. Please we will be grateful if you lift the block for the day and add a local exception to the global block to enable participants to join and contribute to Wikipedia. The IP is 154.160.70.27. Find the event dashboard here https://outreachdashboard.wmflabs.org/courses/Wikimedia_Ghana_User_Group/Koforidua_Edits_Wikipedia_2?enroll= Robertjamal12 (talk) 11:04, 3 October 2021 (UTC)
- @Robertjamal12: regarding getting signups, you should be able to select "Enable account requests" on your dashaboard settings to help get signups and account creations completed - will leave it to ST47 if the block can be changed (even temporarily) to a softblock so that logged in users can make edits. — xaosflux Talk 13:43, 4 October 2021 (UTC)
@Xaosflux: Thank you. Yes, we are able to get sign-ups through the dashboard but they can't edit any article after the sign-up. Thanks once again and we will be glad if ST47 grant us the temporal unblock. Robertjamal12 (talk) 14:04, 4 October 2021 (UTC)
Your thoughts?
[edit]This message was dropped on my TP, care to take a look? Celestina007 (talk) 23:44, 5 October 2021 (UTC)
67.205.128.0/18
[edit]I noticed that you blocked Special:Contribs/67.205.128.0/18 indefinitely. While I doubt this range will be assigned to someone other than DO anytime soon, I wanted to check that you meant to do that. AntiCompositeNumber (talk) 20:23, 2 October 2021 (UTC)
- It looks like I changed the settings on someone else's indef block. There are more of these left than I thought there were - I thought someone ran a bot last year-ish to give many of them expirations. ST47 (talk) 01:01, 9 October 2021 (UTC)
AN notice
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello ST47. AN thread of interest: WP:AN#Blocking_admin_is_unresponsive. -- zzuuzz (talk) 10:38, 6 October 2021 (UTC)
- I hate to pester, but while we're on the topic of being responsive to questions regarding administrative actions, would you mind please looking at the message I left you here that fell off into the archive. SQLQuery Me! 12:01, 6 October 2021 (UTC)
- Hurricane Electric operates a tunnel service that easily qualifies as an open proxy. If you have identified a range that you are confident is used by residential customers, please feel free to unblock it. ST47 (talk) 00:53, 9 October 2021 (UTC)
- You did unblock it, over a month before leaving this message. ST47 (talk) 00:53, 9 October 2021 (UTC)
154.160.70.27
[edit]Thanks for promptly unblocking 154.160.70.27 (talk · contribs · block log). I had read the bot's instructions, and even the BRfA, and figured no bot ever overrides an admin's block, not ProcseeBot or anyone (we spent some time making sure ProcseeBot wouldn't do this). The BRfA says "If an IP is blocked, either directly or via a range block, this bot does not modify the block settings at all". Perhaps you could take a look at implementing this behaviour. Thanks. courtesy ping -- zzuuzz (talk) 09:24, 8 October 2021 (UTC)
- @Zzuuzz: The reason is that many of these IPs are being blocked anon-only due to vandalism, by admins who do not recognize that they are proxies. So while the bot is certainly not going to reinstate a block that an admin has removed, it is set up to correct block settings and extend blocks that will soon expire, if needed. I will test having it skip IPs that are directly blocked by someone other than itself, ProcseeBot, or me, and check the log in a day or two to see if it's missing anything major by doing so. ST47 (talk) 00:51, 9 October 2021 (UTC)
.
[edit]Hello why did you decide to block me??? What I have done?? Please inform me. Hisksjueeu (talk) 11:10, 14 October 2021 (UTC)
Dissapointing
[edit]Regarding This close, The query I left here was very obviously not about the range that I had unblocked, but the ranges within that AS that you had blocked wholesale regardless of use - and was asking you to look into those blocks that I feel you had made in error per WP:ADMINACCT. This will be the last attempt that I make to resolve this issue via this venue. SQLQuery Me! 13:46, 27 October 2021 (UTC)
- @SQL: I'm very busy, and while I'm sad to hear that you are disappointed, I don't know what you expect me to do about it. I block a lot of ranges operated by hosting providers and proxy services, including so-called "tunnel brokers" and VPNs. If there is an open unblock request that I need to look at or a range that you object to being blocked then please point it out more clearly. If the ownership of any range has changed and is now not operated by a residential or mobile ISP, or commingles residential and server connections on the same net block, then you also are free to correct those blocks. ST47 (talk) 17:18, 27 October 2021 (UTC)
The Signpost: 31 October 2021
[edit]- From the editor: Different stories, same place
- News and notes: The sockpuppet who ran for adminship and almost succeeded
- Discussion report: Editors brainstorm and propose changes to the Requests for adminship process
- Recent research: Welcome messages fail to improve newbie retention
- Community view: Reflections on the Chinese Wikipedia
- Traffic report: James Bond and the Giant Squid Game
- Technology report: Wikimedia Toolhub, winners of the Coolest Tool Award, and more
- Serendipity: How Wikipedia helped create a Serbian stamp
- Book review: Wikipedia and the Representation of Reality
- WikiProject report: Redirection
- Humour: A very Wiki crossword
77.38.103.96
[edit]I noticed the bot keeps blocking this IP as a proxy again, again and again. Any reason we can't just block indef? It's only been used for trolling and harassment. Ritchie333 (talk) (cont) 14:57, 1 November 2021 (UTC)
- @Ritchie333: We aren't really supposed to do indefinite IP blocks. As long as the IP remains detectable as a proxy, the bot should always extend the block shortly before it is due to expire, so I don't think there's any need for further intervention. ST47 (talk) 19:07, 1 November 2021 (UTC)
Administrators' newsletter – November 2021
[edit]News and updates for administrators from the past month (October 2021).
- Phase 2 of the 2021 RfA review has commenced which will discuss potential solutions to address the 8 issues found in Phase 1. Proposed solutions that achieve consensus will be implemented and you may propose solutions till 07 November 2021.
- Toolhub is a catalogue of tools which can be used on Wikimedia wikis. It is at https://toolhub.wikimedia.org/.
- GeneralNotability, Mz7 and Cyberpower678 have been appointed to the Electoral Commission for the 2021 Arbitration Committee Elections. Ivanvector and John M Wolfson are reserve commissioners.
- Eligible editors are invited to self-nominate themselves to stand in the 2021 Arbitration Committee elections from 07 November 2021 until 16 November 2021.
- The 2021 CheckUser and Oversight appointments process has concluded with the appointment of five new CheckUsers and two new Oversighters.
IP block exemption
[edit]Hi ST47, I've been editing Wikipedia through a VPN server, that I host on one of my VPS servers, due to privacy concerns. Recently I switched my VPS provider to another one and found that their ASN's IP prefix range has been blocked by you, which I noticed when it prevented me from editing the Wiki through (this) registered account. I frequently rotate my IP when I switch my VPS providers, so since you're one of the checkusers, I'm seeking an IP block exemption for this account so that I could edit English Wikipedia (and its sister projects sometimes) without difficulty. I could fill you in with the specifics such as IP ranges and such if required through email. Thanks, WikiLinuz (talk) 02:21, 3 November 2021 (UTC)
An Additional Blocked IP address issue
[edit]My name is Stuart and I have just received a message when attempting to correct a typo on a Wiki listing. The reason you give is that you believe my IP address to be a commercial Web hosting or Collocation provider. I can assure you as a private consumer and donator to Wikipedia for many years now, that I am indeed just a humble gentleman, living a normal life in my cottage in a leafy part of East Sussex, along with my husband & 2 cats! I am not and never have been associated with any kind of Web hosting or collocation providing. My network WiFi is provided by Sky and I believe that they currently are utilising BT Outreach services in order to provide their Broadband and telephone services to us.
We don't currently have any kind of superfast cabling installed on our Lane, so Sky are the only reliable "satellite" TV services provider, until such time that either the UK government, BT, Sky, Virgin or possibly some other Yorkshire based provider installs that much needed superfast fibre networking cables to all of us who live in our lane, here in leafy Sussex! I would definitely appreciate it if you could kindly reverse the choice that you made & so then lift your block on my IP address in order that I may continue to provide help, edit spelling or/ and add or delete information as I have been doing for several years now. I love to glean information and then share any of my knowledge or experience with others. Wikipedia, I discover, is one of THE perfect ways to do that. That is why I donate to help keep Wikipedia free to all users and will continue to do so, as long as I am able to. I'm not sure why you thought that my IP address belonged commercial entity in the first place and being an "information sponge" myself, would greatly appreciate it if you could explain your methodologies in arriving at your decision to place a block on my IP address. It's just that I would love to learn how you come to a decision firstly and what enables you to arrive at or base your choices on to block certain IP addresses for whatever reason. I would greatly appreciate that explanation and look forward to you lifting the block you have placed on my IP With the kindest of regards, Stuart & Paul
☆ Further information can be provided to you for future communication, but not in this public forum. We can arrive at a more secure solution to that if you require any further information. KR 😉 Stupotty1965 (talk) 06:10, 17 November 2021 (UTC)
ArbCom 2021 Elections voter message
[edit]The Signpost: 29 November 2021
[edit]- In the media: Denial: climate change, mass killings and pornography
- WikiCup report: The WikiCup 2021
- Deletion report: What we lost, what we gained
- From a Wikipedia reader: What's Matt Amodio?
- Arbitration report: ArbCom in 2021
- Discussion report: On the brink of change – RFA reforms appear imminent
- Technology report: What does it take to upload a file?
- WikiProject report: Interview with contributors to WikiProject Actors and Filmmakers
- Recent research: Vandalizing Wikipedia as rational behavior
- Humour: A very new very Wiki crossword
A possible connection to a checkuser block you did
[edit]You blocked User:Wiki person that edits (intentionally not linked) with a checkuser block without specifying more details. I have seen a new account, User:EnWikiFactChecker, editing in similar areas. I do not hear quacking, but something feels...off with the account. Not sure where to report, but since it was your CU block on the first account, you might know where to go with the second. —C.Fred (talk) 02:39, 1 December 2021 (UTC)
- Seemed obvious to me. I blocked without tags because that's apparently what others wish. C.Fred, the master is LEKReports, and I assume someone will request a glock.--Bbb23 (talk) 03:25, 1 December 2021 (UTC)
- Actually, I misread the tagging issue, so have now tagged.--Bbb23 (talk) 03:30, 1 December 2021 (UTC)
- @Bbb23: That's what was missing in my brain, the master. Thanks for jogging the memory. —C.Fred (talk) 03:36, 1 December 2021 (UTC)
- @C.Fred:, Confirmed to TheLEKReports, Two three one two and Pagecreators are confirmed as well. All are blocked and tagged. ST47 (talk) 07:15, 3 December 2021 (UTC)
- @Bbb23: That's what was missing in my brain, the master. Thanks for jogging the memory. —C.Fred (talk) 03:36, 1 December 2021 (UTC)
- Actually, I misread the tagging issue, so have now tagged.--Bbb23 (talk) 03:30, 1 December 2021 (UTC)
Temporarily blocked, but not any more
[edit]Hi ST47. I was blocked from editing earlier today and saw the message "Editing from 2C0F:F4C0:1000:0:0:0:0:0/36 has been blocked (disabled)", relating to a block apparently applied by you. I am no longer blocked. Just to make sure, should I apply to be IP-block exempted or not necessary? Regards, and have a great weekend. Rui ''Gabriel'' Correia (talk) 06:37, 3 December 2021 (UTC)
- @Rui Gabriel Correia:, it sounds like that block isn't affecting you anymore, but in any case, I have lifted it. ST47 (talk) 07:19, 3 December 2021 (UTC)
- Thanks, ST47. Thanks for looking into it and for the action taken. Rui ''Gabriel'' Correia (talk) 07:21, 3 December 2021 (UTC)
Administrators' newsletter – December 2021
[edit]News and updates for administrators from the past month (November 2021).
- Unregistered editors using the mobile website are now able to receive notices to indicate they have talk page messages. The notice looks similar to what is already present on desktop, and will be displayed on when viewing any page except mainspace and when editing any page. (T284642)
- The limit on the number of emails a user can send per day has been made global instead of per-wiki to help prevent abuse. (T293866)
- Voting in the 2021 Arbitration Committee Elections is open until 23:59, 06 December 2021 (UTC).
- The already authorized standard discretionary sanctions for all pages relating to the Horn of Africa (defined as including Ethiopia, Somalia, Eritrea, Djibouti, and adjoining areas if involved in related disputes), broadly construed, have been made permanent.
NYPL ip blocked as P2P proxy
[edit]The bot erroneously blocked 65.88.88.93 as a P2P proxy/VPN. The network 65.88.88.0/24 is one of the address pools used by NYPL, and is perfectly legitimate. More interesting is the comment that suggests that this was an API-based action. Which API would that be? Don't have the time to look into the bot particulars. 69.193.135.254 (talk) 22:12, 3 December 2021 (UTC)
- It is possible that the IP range is shared or that some computer on that IP has been infected with malware that is causing it to proxy malicious traffic. The block is correct, and due to its short duration, it will be lifted in short order if the IP is no longer showing signs of being a proxy. ST47 (talk) 22:47, 3 December 2021 (UTC)
- ??? Of course it is a shared ip range, didn't you check the address? A simple whois/donain tools search would have given all the info. The entire /24 range is not blocked, afaik only this address is. What is the API that determined that this is a proxy and why did it single out that address? Btw, it is extremely unlikely that the Library IT dept. would overlook this. This is a fully staffed network with thousands of nodes and way above average security track record. It would be next to impossible to run proxy software on a public/user node, especially one that could be so easily detected by whatever tools the bot uses. 172.254.222.178 (talk) 00:50, 4 December 2021 (UTC)
- Hmmm, have to amend the above. It seems that user devices (as distinct from Library assets) are allocated ips from the same ranges that Library nodes use. Not the place to expand on this, but between masking, subnetting, and translation, it is entirely possible that a user's own laptop could get an ip also used by the Library's own computers. Obviously, the Library cannot guarantee the security profile of visitor devices. I agree that little can be done about this. Obviously a "bad" visitor computer triggered this, thereby limiting other visitors' experience. 172.254.222.178 (talk) 01:06, 4 December 2021 (UTC)
- ??? Of course it is a shared ip range, didn't you check the address? A simple whois/donain tools search would have given all the info. The entire /24 range is not blocked, afaik only this address is. What is the API that determined that this is a proxy and why did it single out that address? Btw, it is extremely unlikely that the Library IT dept. would overlook this. This is a fully staffed network with thousands of nodes and way above average security track record. It would be next to impossible to run proxy software on a public/user node, especially one that could be so easily detected by whatever tools the bot uses. 172.254.222.178 (talk) 00:50, 4 December 2021 (UTC)
Administrators will no longer be autopatrolled
[edit]A recently closed Request for Comment (RFC) reached consensus to remove Autopatrolled from the administrator user group. You may, similarly as with Edit Filter Manager, choose to self-assign this permission to yourself. This will be implemented the week of December 13th, but if you wish to self-assign you may do so now. To find out when the change has gone live or if you have any questions please visit the Administrator's Noticeboard. 20:06, 7 December 2021 (UTC)
Precious anniversary
[edit]Two years! |
---|
--Gerda Arendt (talk) 08:38, 8 December 2021 (UTC)
Permission to unblock my access to edit Unduk Ngadau
[edit]I am sorry if there is any misunderstood behind editing in Wikipedia. I just started editing with a proper policy since a week ago. Please unblock my IP address and I will not edit false news anymore. Please. Yoon Ezz (talk) 14:02, 12 December 2021 (UTC)
- @Yoon Ezz You’re not even blocked at all. 👨🏻💻 Rng0286 (☎️ talk) ✍️ conts ;) The Iconfactory “is everywhere” (☑️ rights) Kinopid'oh! 03:06, 20 December 2021 (UTC)
Checkuser data
[edit]Hello, I really hate to bother you, but I have question to ask. Is there any data publicly available about how many SPI investigations are opened annually, and how many result in confirmation? I searched the web but could only find secondary sources that give uncited figures for certain years.
For example, a quote from Case Study of Sockpuppet Detection on Wikipedia":
"Sockpuppets are a prevalent problem in Wikipedia, there were close to 2,700 unique suspected cases reported in 2012. "
This is helpful but I can't find any facts on the number of sockpuppets investigated/confirmed for 2014, 2018, or 2020, etc.
Are these facts even formally collected and disseminated? If so I would greatly appreciate knowing where to find them. Thanks for your time. Hunan201p (talk) 08:41, 24 December 2021 (UTC)
- By the way, I am aware of this SPI archive but it dates back to the 2000s and seems inactive, and not very quantitative. To clarify, I'm looking for more recent figures, rather than a list of cases. Hunan201p (talk) 08:52, 24 December 2021 (UTC)
The Signpost: 28 December 2021
[edit]- From the editor: Here is the news
- News and notes: Jimbo's NFT, new arbs, fixing RfA, and financial statements
- Serendipity: Born three months before her brother?
- In the media: The past is not even past
- Arbitration report: A new crew for '22
- By the numbers: Four billion words and a few numbers
- Deletion report: We laughed, we cried, we closed as "no consensus"
- Gallery: Wikicommons presents: 2021
- Traffic report: Spider-Man, football and the departed
- Crossword: Another Wiki crossword for one and all
- Humour: Buying Wikipedia
Merchandise giveaway nomination
[edit]A token of thanks
Hi ST47! I've nominated you (along with all other active admins) to receive a solstice season gift from the WMF. Talk page stalkers are invited to comment at the nomination. Enjoy! Cheers, {{u|Sdkb}} talk ~~~~~
|
MediaWiki message delivery (talk) 23:50, 31 December 2021 (UTC)
Happy New Year!
[edit]Thanks for your contributions to Wikipedia, and a Happy New Year to you and yours! 7&6=thirteen (☎) 13:41, 1 January 2022 (UTC)
- – Send New Year cheer by adding {{subst:Happy New Year}} to user talk pages.
Administrators' newsletter – January 2022
[edit]News and updates for administrators from the past month (December 2021).
Interface administrator changes
|
|
- Following consensus at the 2021 RfA review, the autopatrolled user right has been removed from the administrators user group; admins can grant themselves the autopatrolled permission if they wish to remain autopatrolled.
- Additionally, consensus for proposal 6C of the 2021 RfA review has led to the creation of an administrative action review process. The purpose of this process will be to review individual administrator actions and individual actions taken by users holding advanced permissions.
- Following the 2021 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Beeblebrox, Cabayi, Donald Albury, Enterprisey, Izno, Opabinia regalis, Worm That Turned, Wugapodes.
- The functionaries email list (functionaries-enlists.wikimedia.org) will no longer accept incoming emails apart from those sent by list members and WMF staff. Private concerns, apart from those requiring oversight, should be directly sent to the Arbitration Committee.
Category:Reuploaded deleted images has been nominated for discussion
[edit]Category:Reuploaded deleted images has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. * Pppery * it has begun... 00:39, 4 January 2022 (UTC)
How we will see unregistered users
[edit]Hi!
You get this message because you are an admin on a Wikimedia wiki.
When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.
Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.
If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.
We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.
Thank you. /Johan (WMF)
18:13, 4 January 2022 (UTC)
How we will see unregistered users
[edit]Hi!
You get this message because you are an admin on a Wikimedia wiki.
When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.
Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.
If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.
We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.
Thank you. /Johan (WMF)
18:14, 4 January 2022 (UTC)
Your Bot is Out of Control
[edit]Your bot (ST47ProxyBot) is running amok banning IPs left and right, today mine got blocked for no apparent reason. Fix your spaghetti code.--Catlemur (talk) 16:24, 7 January 2022 (UTC)
- Maybe you can try to ask it a bit more polite?? I can not blame ST47ProxyBot and ST47 for plain ignoring your rude attack. The Banner talk 17:42, 7 January 2022 (UTC)
Help for a blocked account
[edit]Hello ST47, I hope you are doing great? :)
The user account; Ataavi has been an active wikipedian for about 4 years with over 2,700 edits on English wikipedia. His account was recently blocked for using a P2P proxy. He submitted an unblock request but the request has been declined.
I believe the block was made with the best intentions for wikipedia, but I do not believe there was any intent of malice from the blocked party.
I was wondering if you could kindly look into the matter, help resolve the issue, and if possible, exempt the account from IP blocks.
Counting on your usual support.
Best regards,
Kinvidia (talk) 00:21, 10 January 2022 (UTC).
- @Kinvidia: I've granted block exemption. -- zzuuzz (talk) 00:29, 10 January 2022 (UTC)
Thank you for the swift intervention zzuuzz. I am very grateful. Kinvidia (talk) 10:08, 10 January 2022 (UTC)
Tier1 ISP he.net blocked
[edit]The IPv6 service provided by he.net has been blanket banned, as the whole ISP seems to be marked as a colocation web host. Please coordinate with he.net to resolve, blocking IPv6 addresses making moving from IPv4 to IPv6 difficult. Minfrin (talk) 15:55, 17 January 2022 (UTC)
Colo block adjustment
[edit]Per this unblock request on UTRS where a rep from the network is saying that this block covers quite a few customers that are not part of colo services. They're saying that only 82.221.96.0/19 and 82.221.128.0/19 are used for colo. Those two /19 ranges are already blocked globally through August 2023 as open proxies. OhNoitsJamie Talk 00:41, 20 January 2022 (UTC)
Block Exemptions
[edit]Hello ST47, I hope you are doing great? :)
Considering the advent of rampant blocks on English wiki lately, I was wondering if block exemptions could be requested for new accounts. My team and I will be embarking on projects that are aimed at recruiting new editors for Wikipedia, and I assume that these IP blocks may significantly affect these projects if block exemptions are not offered for new editors. If this is not possible, could you kindly recommend a better resolve to me if you have any?
Best regards.
Kinvidia (talk) 02:49, 20 January 2022 (UTC)
The Signpost: 30 January 2022
[edit]- Special report: WikiEd course leads to Twitter harassment
- News and notes: Feedback for Board of Trustees election
- Interview: CEO Maryana Iskander "four weeks in"
- Black History Month: What are you doing for Black History Month?
- WikiProject report: The Forgotten Featured
- Arbitration report: New arbitrators look at new case and antediluvian sanctions
- Traffic report: The most viewed articles of 2021
- Obituary: Twofingered Typist
- Essay: The prime directive
- In the media: Fuzzy-headed government editing
- Recent research: Articles with higher quality ratings have fewer "knowledge gaps"
- Crossword: Cross swords with a crossword
Administrators' newsletter – February 2022
[edit]News and updates for administrators from the past month (January 2022).
- The Universal Code of Conduct enforcement guidelines have been published for consideration. Voting to ratify this guideline is planned to take place 7 March to 21 March. Comments can be made on the talk page.
- The user group
oversight
will be renamedsuppress
in around 3 weeks. This will not affect the name shown to users and is simply a change in the technical name of the user group. The change is being made for technical reasons. You can comment in Phabricator if you have objections. - The Reply Tool feature, which is a part of Discussion Tools, will be opt-out for everyone logged in or logged out starting 7 February 2022. Editors wishing to comment on this can do so in the relevant Village Pump discussion.
- The user group
- Community input is requested on several motions aimed at addressing discretionary sanctions that are no longer needed or overly broad.
- The Arbitration Committee has published a generalised comment regarding successful appeals of sanctions that it can review (such as checkuser blocks).
- A motion related to the Antisemitism in Poland case was passed following a declined case request.
- Voting in the 2022 Steward elections will begin on 07 February 2022, 14:00 (UTC) and end on 26 February 2022, 13:59 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
- Voting in the 2022 Community Wishlist Survey is open until 11 February 2022.