This is an archive of past discussions with User:SQL. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
ToBeFree, I've updated the example query so it works now. That isn't why the bot isn't posting, however. I need to make some backend updates to the framework I use with regards to login tokens. SQLQuery me!22:22, 30 November 2019 (UTC)
Allows the user to generate a changes feed for many users, as well as shows overlap of those users.
At the moment, it only works on the recentchanges table (~30 days), and the colors are somewhat terrible (I'd love suggestions + hex codes for 20 colors that look good!). Allows a much larger number of editors to be compared than any of the current editor comparison tools do for performance reasons. I came across the need for a tool like this a few times recently when looking at large sock farms.
I'm working on a mechanism to do longer contribs searches in the revision table via chunking, which should be coming soon. SQLQuery me!17:20, 5 December 2019 (UTC)
Now allows you to search contribs overall. Cumulative query time is limited at the moment, so on people with large amounts of edits, it won't get all of them. SQLQuery me!20:53, 5 December 2019 (UTC)
Hello SQL, may you be surrounded by peace, success and happiness on this seasonal occasion. Spread the WikiLove by wishing another user a Merry Christmas and a Happy New Year, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Sending you heartfelt and warm greetings for Christmas and New Year 2020. Happy editing, JACKINTHEBOX • TALK08:19, 23 December 2019 (UTC)
Hello SQL, may you be surrounded by peace, success and happiness on this seasonal occasion. Spread the WikiLove by wishing another user a Merry Christmas and a Happy New Year, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Sending you heartfelt and warm greetings for Christmas and New Year 2020. Happy editing, Donner60 (talk) 08:27, 25 December 2019 (UTC)
Lofty abyss, I think that was an edit conflict. HBC bot and mine picked the page up at the same time from the looks of it. SQLQuery me! 04:15, 4 January 2020 (UT
Achim55, The paid lookups that ipcheck uses differ from the free lookups. From the website (may require login):
How Do Free Lookups Compare to Paid Plan Lookups?
You're likely missing fraud and high risk IP addresses! All of IPQS paid plans have access to better blacklists that significantly expand behavior patterns and detection rates for high risk IPs. Many of the worst IP addresses that facilitate abusive users online are via residential proxies. Our paid plans have access to premium blacklists with millions of active residential IP addresses & compromised devices collected by proprietary honeypots and botnet infiltration. Free account plans are limited to checking only a small portion of that data, leaving large gaps in coverage.SQLQuery me!15:09, 9 January 2020 (UTC)
I need help can you link me the address for the ENwikipedia helper channel? I've tried multiple times to try to connect to it. I just came back from a 2 year WP: RETIRE so I don't know if they discontinued that channel or something. Thanks in advance. BobherryTalkEdits10:56, 4 February 2020 (UTC)
DVdm, I think I know what's causing that, you saved the edit after the bot had already loaded the page. But, the bot didn't actually have any entries to remove! It shouldn't have attempted to save the page. Should be an easy fix, I'll get to it after work tonight. SQLQuery me!12:22, 14 February 2020 (UTC)
DVdm, Praxidicae (happened to prax the other day too) - This should be fixed now. It'll still be possible to edit conflict with the bot, but it no longer will attempt to save the page on every run (every 30 mins) unless it has a report to remove, which should address 99.9% of the issue. I'm not sure I can eliminate conflicting with the bot altogether. I can have it check before it saves the page, if the page has changed, before saving, but there's still a possibility that someone else changed the page after that. SQLQuery me!22:03, 14 February 2020 (UTC)
I do not really want to edit the page, but the person who vandalized the page has been indefinitely blocked for it. Can you bring it back to its original protection? OcelotCreeper (talk) 01:55, 17 March 2020 (UTC)
OcelotCreeper, unfortunately the abuse occurring there has come from multiple accounts and IP's - some of them gaming Auto Confirmed in order to edit past semiprotection. I believe that temporary full protection is needed at this time. I'd be open to protecting it for less than the current two weeks, but it wouldn't be by much. It appears that this person has been vandalizing the article for a few months now. SQLQuery me!01:59, 17 March 2020 (UTC)
OcelotCreeper, I cannot publicly connect accounts with IP's, sorry. I figured someone that appears to be so knowledgeable about our internal policies and processes would know that. SQLQuery me!02:23, 17 March 2020 (UTC)
One more question before I leave? Of all of the suspected accounts or IPs they abused (I am saying suspected this time), is there a specific article other than Toy Story that the accounts normally edit? Because if there is one, then you could put that article on your watchlist, see if a similar edit was made, then check what contributions they are making. Remember, I read multiple Wikipedia policies before I started my account, but I still do not know or fully understand everything. OcelotCreeper (talk) 02:32, 17 March 2020 (UTC)
Ok sure, especially since the user was not an extended confirmed user. But if this type of vandalism happens again, particularly from an extended confirmed user, use full protection. OcelotCreeper (talk) 02:52, 17 March 2020 (UTC)
Thank you for the copy edit. I've been requesting help on this article for days but there are too many articles to work on. Any way, article is kind of mature so i am indeed slowing down. Yug(talk)08:10, 28 March 2020 (UTC)
You have recently declined my application for the unblocking, stating that the IP address is "clearly a webhost" and suggested that I am probably using a proxy or VPN. I was neither using a proxy nor VPN, and my PC is also not a webhost. BUT I have some idea about where the problem might lie: my internet provider assigns even static IP addresses dynamically (via DHCP server), based on the connected device's MAC address. Can this be the reason?
I am able to write this because now I am using a VPN of my University. So no problem for me, but maybe this type of block can affect others. This is why I am posting this note. Sorry if this is not the right place for it, because I do not know how to "leave a note" otherwise.--Esmu Igors (talk) 14:23, 3 April 2020 (UTC)
This probably isn't an issue with DHCP, as a residential provider wouldn't be able to assign you an address in a range that they don't own.
The only things I can think of are:
Running an anonymizing app or VPN that you aren't aware of, or have forgotten
On a very rare occasion this can be a symptom of malware or other infection, especially if you're seeing odd behavior such as ads on pages that shouldn't have ads
A poorly configured/managed ISP that for some reason routes traffic over a webhost
This is pretty uncommon, but it does happen - generally with free/public wifi
I hope this at least helps to explain how I came to the conclusion that the IP mentioned is clearly a webhost. SQLQuery me!15:40, 3 April 2020 (UTC)
Respected SQL, this does explain Your motivation well. And the physical address mentioned hereis indeed the address in my contract with my internet service provider. But the company NANO special is not my ISP.
The problem is that the information on that page was last updated in 2016. My ISP, in turn, only recently (in the end of 2019) has been reorganized, and also changed its physical location to a completely different address (the one visible over the link above). And simultaneously they changed the IP address range. Also, they went through a rush of changing the company name (2 years ago they were called I-NET, then Netvision (as their homepage is still titled) and now the official company name is Dnet ITrisinājumi). I understand this does not describe my ISP as a rock-reliable company, but things are just as they are. But I also understand this probably means they haven't updated some universally available information somewhere or so. Maybe I should query them as well about this situation... --Esmu Igors (talk) 18:55, 3 April 2020 (UTC)
Blocked user
You blocked this IP address User:45.56.153.110 and it's in a range block but we have an OTRS ticket Ticket:2020033110005992 saying they are unable to edit while logged into their account. Can you assist with this or do I need to involve stewards? I can provide the username privately. ww2censor (talk) 12:58, 6 April 2020 (UTC)
The editor will either have to turn off their VPN in order to edit, or request IPBE both locally and globally (Local procedure can be found at WP:IPECPROXY, global procedure at: meta:Steward_requests/Global_permissions#Requests_for_global_IP_block_exemption). Our local procedure involves emailing the checkuser queue, and being able to articulate a need to edit via open proxies.
Thanks for the info, much of which I am not well versed in, hence the question. I'll reply with some of the details you've given so they can decide as they are in China. Indeed I did not see you on the OTRS agent list. ww2censor (talk) 16:45, 6 April 2020 (UTC)
OcelotCreeper, I'm a volunteer, and with the current crisis, my time available to volunteer is very limited. I'm most comfortable with unblocks, granting IPBE, and technical checkuser requests on the admin side, so that's where I tend to spend most of my time.
My interpretation of RD3 may be stricter than others, but I do not believe that the material in those diffs fits: This includes allegations, harassment, grossly inappropriate threats or attacks, browser-crashing or malicious HTML or CSS, shock pages, phishing pages, known virus proliferating pages, and links to web pages that disparage or threaten some person or entity and serve no other valid purpose, links to any of these, but not mere spam links.. SQLQuery me!21:00, 10 April 2020 (UTC)
Oh, duh... I saw you declined the request and for some reason I thought it was your name in the log also since you're both CUs. Thanks for pinging ST47 here. --Kinut/c21:59, 12 April 2020 (UTC)
Ipcheck API
Hello, is API for IPCheck disallowed now? I am forwarded to the main page when I try to get API result, if that is the problem on my side, please advise. Thank you. -- Hamish Welcome19:12, 18 April 2020 (UTC)
Appreciated. I think both URLs are reliable now so I would not change it until further problems ( hope it will not happen). -- Hamish Welcome09:49, 21 April 2020 (UTC)
Auto-approving " (WMF)" accounts at IPCheck
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.
DBarratt (WMF), I hope this isn't a bother, as I noted in my reply @ phab, I'm open to discussing access to IPCheck. I really have no way that I'm aware of to verify that an account with that suffix is a WMF staff member. I see that there is a staff global group, but it seems a little thin. I'm 100% open to suggestions if you have any. I'm hoping to make a sprint in the coming weeks with relation to machine-learning, which I've started laying a foundation for this week. SQLQuery me!04:27, 21 April 2020 (UTC)
AntiCompositeNumber, One thought / possibility was to allow staff permissions to help train the machine, which I was going to limit to CU's and others that I explicitly trust. Also in the plan was a system similar to WP:OPP. I'm looking for something more substantial than 'was able to create an account', a flag, an indicator, or something else that only WMF can set / create. SQLQuery me!05:36, 21 April 2020 (UTC)
This has been raised at github, complete with a pull request that would 100% accomplish allowing accounts ending in " (WMF)" to bypass the ec check (super helpful actually, this'll make it very easy to go forward with once the concerns are resolved - thanks!!). I've raised the same concerns there that I did here. SQ1LQuery me!00:50, 29 April 2020 (UTC)
I've closed this issue, and all other outstanding IPCheck issues out - as well as archived the project @ github at this time. It's been made very clear to me that I should not be investing any further time or effort in IPCheck. SQLQuery me!04:15, 2 May 2020 (UTC)
The discussion above 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.
Request
Dear SQL, you gave me a message on my talk page a week ago, but I'm still in trouble. I will appreciate it if you give me IPBE permission. Thank you very very much! 04:20, 25 April 2020 (UTC)
RuiyuShen, I am so sorry that I haven't been able to get back to you. I'm just not in a position right now to help. Risker, L235, stwalkerster, TonyBallioni, is there any way one of you would be able to help with this request. There's a mail in the checkuser OTRS regarding this too. SQLQuery me!04:15, 2 May 2020 (UTC)
Noted, SQL. RuiyuShen, I've granted for 6 months as you're a pretty new user. You can ask for an extension at that point, if required. I'll leave a note on your own talk page as well. Risker (talk) 04:32, 2 May 2020 (UTC)
I'm requesting to see if this edit fits RD1. The edit that was made was a line for line script of the Minecraft parody of this song titled "Revenge". — Preceding unsigned comment added by OcelotCreeper (talk • contribs)
I don't understand half of what you do, but I sure know that I wouldn't be able to do what I do if you didn't do it. All the best, ——Serial#11:55, 3 June 2020 (UTC)
The future of IPCheck
I've lost a lot of trust towards WMF, and a lot of interest in helping the project because of these events.
It's going to be a while to get back to the point that we were at before this.
Some time away has helped, work is far less stressful, let's put this to bed for now.
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.
First and foremost, I would like to apologize to those that have come to depend on IPCheck in it’s current state.
I noticed T248525 in my phabricator feed some time ago. And other tickets like this one. I’ve been noticing them for some time now. Never mentioned in them, or pointed to them, but noticed for sure.
I asked directly tonight, if I should spend any further time on IPCheck, or if WMF are planning on replacing it. The short version is that I was told that it wouldn’t make sense for me to invest any more time or effort into IPCheck due to the coming IP Masking.
After working on this tool for years, this is devastating to me.
I am presently considering moving IPCheck off of toolforge, to my own private machines. This will very likely mean removing Oauth, returning the remainder of my grant (which only ever went to paying for IPQS, I have never accepted any money for any code contributions), disabling IPQS, and moving the project to a closed source (with credits to the current contributors, or course). I will try to keep the service up, and free for as long as possible. I understand that this may break some MediaWiki: links, and I apologize for that. I don’t think that it’s appropriate to redirect from ipcheck.toolforge.org to our new home, but I may leave a link to it for as long as it’s allowed.
I’d like to thank MusikAnimal for the help making the tool look great, work great, answering my silly questions, and helping to clean up my terrible code - that was the big turning point. Tks4Fish for the support, and feedback, and especially TonyBallioni for encouragement, feedback and helping me publicize the tool that existed for years before it became mainstream!
I have good things in the works still for the tool, and major updates planned. I’ll try to keep everyone updated as the situation evolves.
As for me? Tomorrow’s my first day off work in weeks. I think my wife and I are going to take the dogs, and kids on a hike (if I can find somewhere that isn't packed!), no devices! I'm probably going to be away for a while. SQLQuery me!04:59, 2 May 2020 (UTC)
We don't say "thank you" often enough; we tend to just assume people know we appreciate them. Well, I appreciate how much effort you have put into this project, and I'm sorry that things aren't working out as you had hoped. Glad to hear that you're getting some time off; I hope the hike is enjoyable, and the woods aren't overrun by people who've had enough of self-isolation. Please take the time you need to enjoy your well-deserved break; we'll still be here when you are ready to return. Thank you. Risker (talk) 12:30, 2 May 2020 (UTC)
Thanks for letting me be a part of it! I want to make it clear your efforts haven't been futile, nor have they gone unnoticed. IPCheck is a complete game changer that revolutionized our day to day work. Having it for any amount of time, however brief, made the work worthwhile. I do not have any inside information or know anymore than you do, but it is my impression that IPCheck is a major source of inspiration for what WMF is planning on making. To your concerns about IP masking -- you're not alone. We are all concerned. The entire web is changing into this same privacy-conscious mindset. There's not much we can do about it. Overall I think it is a good thing, but it will pose a great challenge for communities like Wikipedia. You should ask the people who would know, but I really suspect it will be a "while" before IP masking goes live. I don't see any harm in keeping IPCheck on Toolforge until the very day it is obsolete, but this is your decision. I have maintainer access, so if you'd like, I can keep an eye on it until that day comes. At any rate, thank you immensely for all of the amazing tools you've built. Code quality and eye candy are secondary. You did the real work, and you alone had the talent, creativity and drive to make IPCheck a reality. I was just lucky to be a part of it. Please enjoy your time off, old friend! Take as long as your heart desires, but I do hope it isn't too long. We need you :) — MusikAnimaltalk21:02, 2 May 2020 (UTC)
I want to echo what Risker and MusikAnimal said above. Your work on IPCheck has been incredible. It is indeed a major source of inspiration for the work we're planning to do. I agree with MusikAnimal that it makes sense to keep IPCheck alive on Toolforge for as long as it is useful to our editing communities. Whatever we build may not come to parity with what IPCheck offers for a while. Lastly, I hope you enjoy your time off. It's been a joy to see and learn from your work. Thank you. -- NKohli (WMF) (talk) 22:05, 2 May 2020 (UTC)
NKohli (WMF), You have a lot of nerve showing up here. "source of inspriation" nothing, you're directly copying my work.You want me to keep IPCheck active until you can get your off-brand clone off the ground. Please stay off my talkpage. SQLQuery me!06:53, 13 June 2020 (UTC)
I have been using this tool as a part of my ACC work and it's been really helpful. Thank you and enjoy your time off. ‐‐1997kB (talk) 02:36, 3 May 2020 (UTC)
Damn, I have just started using it and its API seriously for proxy detection on dewiki. It would be sorely missed if it goes offline. In any case thank you for the time and energy you invested into this. And have a great time off work! --Count Count (talk) 15:24, 19 May 2020 (UTC)
I would like to thank you for what you did with IPCheck, it's really an useful tool and I'm glad I can use it. Enjoy your break, and looking forward to seeing you again. Best, --Martin Urbanec (talk) 10:27, 20 May 2020 (UTC)
I found this tool handy and have been using this tool almost on a daily basis. I really appreciate your work and hope you enjoy your wikibreak. All the best, WhitePhosphorus (talk) 08:10, 21 May 2020 (UTC)
The discussion above 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.
Bibliomaniac15, Thank you! We'll see. I know I wasn't gone for a super long time, but I want to make sure I haven't missed any important changes. I'll sit down sometime this week and review the admin newsletters. I'm not in any hurry. SQLQuery me!11:13, 28 July 2020 (UTC)
I second this. Can't run it without SQL. I was wondering why my queries weren't recognized...I'm happy to say that this problem is solved . --TheSandDoctorTalk15:33, 2 August 2020 (UTC)
A barnstar for you!
The Technical Barnstar
I am not sure why I never thought to give you this before (and this is probably the first I've given), but you definitely deserve this barnstar for everything you have done for the projects. ♥TheSandDoctorTalk15:36, 2 August 2020 (UTC)
AFC-Ores
User:SQL/AFC-Ores hasn't updated since early May. (I have an ORES-querying bot myself, but it has been running into 500 errors from the ORES endpoint over the past few days, so I came looking to see if yours is working.) Regards, – SD0001 (talk) 17:45, 27 September 2020 (UTC)
Is there an investigation on this "Loser" vandal? I saw a huge war over someone vandalizing the page with "Losers" — Preceding unsigned comment added by 4thfile4thrank (talk • contribs)
They look to be using open proxies, and compromised / zombie machines to make these edits. There are backend measures in place to track them for now. SQLQuery me!15:12, 14 October 2020 (UTC)
Being completely honest what the heck did you do to get a trojan showing up like that? Is that an ip you punched in up there or...? I'm lost. I'm lost... -GoatLordServant (Talk) 15:43, 14 October 2020 (UTC)
It has a wikipedia article, thank goodness. So you punch in a hash for something somehow and it shows if there are malicious files within the file punched in with a hash somehow, so the program ipsharkk is a malicious website? -GoatLordServant (Talk) 15:52, 14 October 2020 (UTC)
GoatLordServant, No, the way VirusTotal works, is that you upload a file, and it uses many modern virus scanners to look at it. This isn't always foolproof, and can result in false positives.
My understanding of how the free tier of ipsharkk works (looking at the source code right now), these proxy nodes are other users running ipsharkk. So, if you use the program, you're also opening yourself up to be used as a proxy node. This is very similar to how Hola (VPN) works. I've found many other ways to identify users of that program as well.
Just wanted to say thank you very much for protecting my user talk page. I know doing so is very often a last-resort but it's certainly for the best, for the time being! Hope you're keeping safe and well. Patient Zerotalk05:16, 15 October 2020 (UTC)
SQL, since you've looked at the source code: Are there any pointers you could give me about how to confirm that someone is running ipsharkk? With this LTA it doesn't really matter, but it might come in handy some day. — Blablubbs(talk • contribs)12:05, 17 October 2020 (UTC)
Thanks for the note, your approach makes sense. I hadn't encountered that before but will definitely keep it in mind as a solution if I run into it again. Thanks, Mifter (talk) 05:31, 15 October 2020 (UTC)
ACE2020 Electoral Commission
Hello SQL. Thank you for volunteering to be an election commissioner for the 2020 Arbitration Committee Election. Following the community RfC, you have been appointed as an election commissioner! While you have certain responsibilities - you are not in this alone, along with the other appointed commissioners other community members have volunteers to assist as coordinators. Best of luck with the election this year. — xaosfluxTalk00:24, 17 October 2020 (UTC)
IPBE request
Hello, SQL. I am a Wikipedian who comes from mainland China. Because of my country's restriction, I have to use some proxies to visit and edit Wikipedia. But my proxies are blocked sometimes. I can't edit en-Wikipedia. I hope that you can grant me an IPBE flag. And I can promise I will not do vandalism.
As a Wikipedian, I have GIPBE and zh-wikipedia's local IPBE. I also have made more than 2,000 edits in zh-wikipedia. And I never do vandalism. I think I am enough to get this flag.
Hello SQL, may you be surrounded by peace, success and happiness on this seasonal occasion. Spread the WikiLove by wishing another user a Merry Christmas and a Happy New Year, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Sending you heartfelt and warm greetings for Christmas and New Year 2021. Happy editing, JACKINTHEBOX • TALK16:17, 24 December 2020 (UTC)
Hello, SQL. Please check your email; you've got mail! Message added 16:54, 25 December 2020 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
Hi, SQL, hope your new year is looking good in every way. I've blocked 2a02:6080::/64 for a week for block evasion, obvious here. But I noticed in their block log that both you and Drmies have previously blocked them for two years (each), with mysterious log notations which I do not understand. Should I block them for a couple of years also, in your opinion? Bishonen | tålk15:11, 1 January 2021 (UTC).
On 3 Dec you blocked this IP. I'm not arguing but inquiring why....? I'm curious only because I am/was involved in editing Black Monday (1987) under my former username User:Lingzhi2. That IP's last edit was a nontrivial change to Black Monday that sorta presented itself as a trivial change...... just curious. The edit looks... OK-ish if a bit lamely cited and a bit... too... pat. Is it a student edit or...? Thanks.OneOffUserName (talk) 14:19, 2 January 2021 (UTC)
Anyhow, as far as the block goes - if any uninvolved administrator believes that the block is no longer preventative - they may remove it. I don't see any reason to site-wide block them, as they're locked.
Since the fact that the emails was sent isn't being argued, there really isn't any checkuser data at play any more, and I'm sure that if an unblock were to be made, Leaderboard would be able to confirm that these emails were pretty blatant spam. I've converted the block from a CU block to a regular block.
I'm messing with a script, and thought it might be interesting to give aggregate stats on my usage of the CU tool, by running a series of regular expressions over the checkuserlog.
These are the aggregate reasons for using it (Keep in mind that one investigation often involves more than one check):
Unblock-related, 110 times.
Second opinion, 7 times.
Impersonation-related, 4 times.
SPI-related, 1 time.
Account compromise related, 1 time.
Block evasion related, 1 time.
If a CU is interested in how they use the tool, leave me a message - and I'll email you.
I will not automate this script, release the source code, or release data for others usage of the tool for any reason other than a direct request - and even then, only by email, directly to the cu making the request.
Probably not what they meant - but I got my positive COVID test result today. So far, it feels like the beginnings of a cold. SQLQuery me!00:11, 4 February 2021 (UTC)
oh crap! I just saw this. I am from India, and people in India are recovering quite easily. Although people who are above 60-70 are having some other issues after recovering from covid. Positive patients are being told to stay in a positive/non-stressed mood, and to eat healthy to be able to digest the strong medicines, and to maintain oxygen levels. I hope you get well soon. Kindly keep us updated here. I'll watchlist your talkpage. See you around. —usernamekiran (talk)19:09, 6 February 2021 (UTC)
@Usernamekiran: That's about what I'm doing - relaxing around the house, keeping busy with some projects I've been meaning to get done - and haven't had the time to do. Thank you! SQLQuery me!19:38, 6 February 2021 (UTC)
Sorry to hear that, but glad you're doing alright for now. Hope you make a speedy recovery, good to know you're taking it easy. ~ Amory(u • t • c)21:28, 6 February 2021 (UTC)
I hope you get well soon :). I have to go to school in person and it's basically scaring me as to when I'm going to catch COVID, because many people are not following protocols at school. --つがるTalk to つがる:)🍁02:34, 8 February 2021 (UTC)
Thank you つがる and Amorymeltzer! I tried to be as careful as possible, always wear a mask when not at home. I sanitized my desk, and pc every few hours as we're required to at work, and I don't really get visitors @ my office. I kept my distance from everyone, and I don't really go out anywhere. My wife and kids don't seem to have it yet, according to the tests. It's still mostly like a cold. I've had my good days, and bad days so far - with mornings typically being the worst. I'm coughing a little, sneezing a little, have had a couple headaches, and some sore joints. I've been keeping an eye on my SpO2 levels, all seems well so far. SQLQuery me!02:40, 8 February 2021 (UTC)
Shared IP Editing
Hey, on an unrealted note, Let's say I am going to be using the school's IP address/WiFi Network to edit Wikipedia and check my Gmail, etc. Is it safe to log in on a public Wifi network, if it's not, what are my options? --つがるTalk to つがる:)🍁02:50, 8 February 2021 (UTC)
I think it would depend on your threat model (e.g. whom are you trying to protect against? A state-level actor, with the full resources of the state, or a skript kiddie at a coffee shop?). If you're in a repressive country like China, Turkey, or similar I would say probably not. That being said, I probably wouldn't risk being caught using a VPN either there, FWIW. It is trivial to see whom is using a VPN, or proxied connection.
In the free world, the connection to Wikipedia, and Gmail are encrypted to begin with - so under normal circumstances, it's likely fine. The only lingering concern is that people on your wifi network may be able to see what sites you're visiting, depending on their capabilities. For me, this isn't a big deal - I don't use wikipedia or gmail on networks that it's not allowed, and I don't really care whom knows that I've visited either - or what pages I've visited. I hope some of this helps. SQLQuery me!03:03, 8 February 2021 (UTC)
I try telling people I know free VPNs are next to useless, but they don't seem to believe it. (Even with paid VPNs I have suspicions too). Also, could someone use my IP as a VPN IP? --つがるTalk to つがる:)🍁03:15, 8 February 2021 (UTC)
It depends. There are some third-party peer-to-peer "VPN" apps that I won't name here - that give you the appearance of a residential connection. The cost of that appearance, is that you're allowing others to share your connection - and often is misused to do awful things - leaving you responsible. I really wouldn't recommend these types of apps. SQLQuery me!03:22, 8 February 2021 (UTC)
Hallo, I don't spend much time looking at ArbCom cases, but a couple of mentions on user talk pages I watch led me to look at Wikipedia:Arbitration/Requests/Case/RexxS. I'm a bit baffled as I can't see the original statement raising the case. From RexxS's statement it seems it was raised by ProcrastinatingReader, but the only statement by them I can see is under "statements by uninvolved editors". Looking at the page history I see you say "It's been a while, but I'm pretty sure I've got this right - Open Case", but I wonder if something is missing? Apologies if I'm missing something. Thanks for your work. PamD08:29, 27 February 2021 (UTC)
Statements by parties: Copy statements by named parties from the case request to the "Preliminary statements" section of the new case page. Statements on both the request page and the new case page should have === Level 3 === headings. If any statement has an excessive amount of supplementary comments or replies to arbitrators, you may wish to surround some of that statement with {{Collapse top}} and {{Collapse bottom}}. If any statement has replies or supplementary statements in === Level 4 === or other sub-headings, you should remove these sub-headings, because they are unnecessary and will clutter the new case page.
Statements by other editors: When you have moved the statements by named parties from the case request to the case page, you will be left with the other statements by uninvolved editors. These statements will need to be preserved, but they should be collapsed. Copy all of these statements into the "Preliminary statements" section, underneath the statements by parties. Surround them with {{hat|Preliminary statements by uninvolved editors.}} and {{hab}}. Note: On older cases these preliminary statements by uninvolved parties were placed on the case talk page. SQLQuery me!04:31, 28 February 2021 (UTC)
Thanks for the explanation. It does seem very strange that the case has no "lead", and the opening words of the first statement make no sense out of context: "This is a vexatious filing". The reader/editor coming to that main case page then has to read on to find an editor named in the second sentence, and click to expand "statements by uninvolved editors" to see what the "vexatious filing" said. In an article that first sentence would be tagged with {{clarify|reason=What filing?}}. It would be helpful if ArbCom added a statement to the effect that "We have decided that the editor who filed a case for ArbCom to consider is not an involved party: their statement may be seen below". But then I suppose ArbCom case pages are only intended to be read by the cognoscenti who are familiar with all the prior discussion. Ah well. Back to my gnoming. PamD09:02, 28 February 2021 (UTC)
Question
In the evidence phase of an ArbCom case, can we present diffs that represent the antithesis of the alleged behavior, or is that phase reserved for evidence that supports the allegations? Also, can we comment about the diffs provided by others? Atsme💬📧14:32, 2 March 2021 (UTC)
My Checkuser Stats for Feb 2021
Like Last month, I'm posting some basic details on how I use the checkuser tool. This is based on running regular a series of regular expressions over the CU log, and might not be accurate. Some items are probably not optimally named.
I used the tool 253 times in Feb.
In Feb, I used the tool in the following modes:
In 'ipedits' mode 169 times.
In 'userips' mode 81 times.
In 'ipusers' mode 0 times.
In 'useredits' mode 0 times.
In 'investigate' mode 3 times.
These are the aggregate reasons for using it (Keep in mind that one investigation often involves more than one check):
Unblock-related: 164 times.
IPBE-related: 21 times.
SPI-related: 33 times.
Second Opionion: 11 times.
Comparison: 8 times.
Bot-related: 6 times.
LTA-related: 6 times.
Block Evasion: 2 times.
Testing: 1 time.
CUWiki-related: 1 time.
If a CU is interested in how they use the tool, leave me a message, or email me.
I will not automate this script, release the source code, or release data for others usage of the tool for any reason other than a direct request - and even then, only by email, directly to the cu making the request.
Hello, SQL. Please check your email; you've got mail! The subject is IP block exemption request. Message added 14:04, 17 March 2021 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
About two weeks ago I put in a request for an IP block exemption to the queue and as of today I still haven’t gotten a response from the team. Does it usually take this long? If so, when can I expect a response? LJF2019talk10:03, 28 March 2021 (UTC)
@CatcherStorm and LJF2019: (confused on the signature, I got an email from LJF as well, so I'll ping you both?) I have not personally worked the queue in weeks, work has picked up, and I have not had the time. If your request isn't relatively strong, it could potentially take a while to find a CU that is comfortable enough to accept.
In any case, I have already explained to you via email the types of requests that I am comfortable handling - and I do not believe that your request falls into any of those categories. Continuing to contact me about your request is unlikely to be fruitful. SQLQuery me!02:03, 29 March 2021 (UTC)
I do not. You have quite literally contacted the entire checkuser team in order to consider your request if I understand correctly. I do not know of others that you should ask to consider your request. In many cases, edge cases that policy perhaps technically supports in theory, but that make the checkuser team uncomfortable (and policy cannot compel/force us to grant or decline any request) may well sit for an extended period of time before being accepted or declined. As I mentioned above, and by email - I am not comfortable handling your request. SQLQuery me!03:54, 29 March 2021 (UTC)
My Checkuser Stats for March 2021
Like the last couple months, I'm posting some basic details on how I use the checkuser tool. This is based on running regular a series of regular expressions over the CU log, and might not be accurate. Some items are probably not optimally named.
I used the tool 71 times in March.
In March, I used the tool in the following modes:
In 'ipedits' mode 49 times.
In 'userips' mode 22 times.
In 'ipusers' mode 0 times.
In 'useredits' mode 0 times.
In 'investigate' mode 0 times.
These are the aggregate reasons for using it (Keep in mind that one investigation often involves more than one check):
Unblock-related: 34 times.
Second Opionion: 10 times.
SPI-related: 10 times.
Double check: 8 times.
Suspected Socking: 7 times
Comparison: 2 times.
If a CU is interested in how they use the tool, leave me a message, or email me.
I will not automate this script, or release the source code. I will not release data for others usage of the tool for any reason other than a direct request - and even then, only by email, directly to the cu making the request.
Like the last couple months, I'm posting some basic details on how I use the checkuser tool. This is based on running regular a series of regular expressions over the CU log, and might not be accurate. Some items are probably not optimally named.
I used the tool 11 times in April.
In April, I used the tool in the following modes:
In 'ipedits' mode 8 times.
In 'userips' mode 3 times.
In 'ipusers' mode 0 times.
In 'useredits' mode 0 times.
In 'investigate' mode 0 times.
These are the aggregate reasons for using it (Keep in mind that one investigation often involves more than one check):
Unblock-related: 11 times.
If a CU is interested in how they use the tool, leave me a message, or email me.
I will not automate this script, or release the source code. I will not release data for others usage of the tool for any reason other than a direct request - and even then, only by email, directly to the cu making the request.
I won't swear on anything, but I intend to try to hit one or two unblock requests every day that I log on, just to do my part to keep the list down to manageable size. Finding out about that is going to make it easier, I imagine quite a bit of backlog is requests that are waiting for a response that may never come. --Floquenbeam (talk) 22:46, 11 May 2021 (UTC)
@Floquenbeam: I appreciate the hell out of anyone that wants to help out at CAT:RFU, even non-admins. If there's anything I can do, questions I can answer, or any way that you think I might be able to help - please ping me! SQLQuery me!22:57, 11 May 2021 (UTC)
OK, we'll have this talk here then.
@Jmorrison230582: I saw your rude message to 331dot on my watchlist, and then went to go see if the article linked needed protection (per your request) to be applied. The first thing I saw was you calling other editors "IDIOTS". Between the message to 331dot, and the edit summary at the article, I decided to remind you about one of our core policies. I hadn't seen at the time that you were reverting messages from other editors about civility / personal attacks out-of-hand. That's why you got a warning from me, as well.
"I hadn't seen at the time that you were reverting messages from other editors about civility / personal attacks out-of-hand. That's why you got a warning from me, as well." I am entitled to remove messages from my talk page, as you should well know. Removing the message means I have read it and don't want to discuss it further. Stop spamming my page (and indirectly my email account) with the same message. Jmorrison230582 (talk) 09:37, 17 May 2021 (UTC)
Two messages is hardly spam, and they were not the same messages. I made an attempt on your talkpage which was removed without response to remind you of one of our core principles. I made an attempt here to explain WHY you got the warning from me, and a request for evidence to back up the accusation that you had made. Indeed - you have the ability to remove most messages. In turn, doing so may result in getting duplicates from other people, as it is hardly reasonable to expect others to look over your talkpage history before leaving a message. SQLQuery me!09:40, 17 May 2021 (UTC)
My Checkuser Stats for May 2021
Like the first half of this year, I'm posting some basic details on how I use the checkuser tool. This is based on running regular a series of regular expressions over the CU log, and might not be accurate. Some items are probably not optimally named.
These are the aggregate reasons for using it (Keep in mind that one investigation often involves more than one check):
Unblock-related: 182 times.
LTA related: 19 times.
Block evasion: 7 times.
SPI case: 3 times.
Second opinion: 3 times.
Cross-wiki abuse: 2 times.
If a CU is interested in how they use the tool, leave me a message, or email me.
I will not automate this script, or release the source code. I will not release data for others usage of the tool for any reason other than a direct request - and even then, only by email, directly to the cu making the request.
I'm letting you know in advance about a meeting I'd like to invite you to regarding the Universal Code of Conduct and the community's ownership of its future enforcement. I'm still in the process of putting together the details, but I wanted to share the date with you: 27 June, 2021. I do not have a time on this date yet, but I will let you soon. We have created a meta page with basic information. Please take a look at the meta page and sign up your name under the appropriate section.
Hello. I go through unblock requests a lot and I noticed that you use the idletimestamp parameter for the unblock template. I was wondering how that worked? HighInBCNeed help? Just ask.12:53, 18 June 2021 (UTC)
I just wanted to thank you for the comments you made after and during the recent RFA from hell. They meant a lot to me even though that was not my RFA. Wikipedia needs more people like you. Scorpions13256 (talk) 06:21, 26 June 2021 (UTC)
Same. I tend to avoid that area and focus more on films, disasters, and zoology. To avoid getting angry at other editors, I tell myself that deep down we all just want what is best for the project. Scorpions13256 (talk) 21:34, 26 June 2021 (UTC)
Hi, in this edit at User talk:Elan Morin Tedronai, your edit summary said "Remove from category until the question asked is responded to". I'm guessing you mean the question I asked Elan, and he actually did finally answer it (he just keeps adding more comments to his unblock request so it might not be obvious). After my two questions, he added (bold is mine): I have to cite the resource like (copied from [[<page name>]]), I believe, even if it's forms entire another article or was from that article, but it belongs in its place. I believe so. I have to cite the resources in the edit summary, I think. I admit I haven't paid attention. But: please don't block me for life. It's deep wound in my everyday life. Since losing my job in 2018, I concentrated on this, but my health in 2020, while suffering two or three prolonged illnesses from COVID-19 and coupled with an epileptic seizure after my birthday. I totally agree to the instructions of Wikipedia:Copying within Wikipedia. I should've put a (Copied content from [[<page name>]]; see that page's history for attribution)? Yes? That's all I can say. Block me for life you want, but that's written in the rules. Most of the unblock request is emotional pleading, but he does seem to realize how to avoid the problem in the future (finally). Your call (or another reviewing admin's). Cheers! Schazjmd(talk)14:30, 3 July 2021 (UTC)
Like the first half of this year, I'm posting some basic details on how I use the checkuser tool. This is based on running regular a series of regular expressions over the CU log, and might not be accurate. Some items are probably not optimally named.
These are the aggregate reasons for using it (Keep in mind that one investigation often involves more than one check):
Unblock-related: 65 times.
SPI case: 13 times.
IPBE-Related: 11 times
Block evasion: 5 times.
LTA related: 5 times.
Potentially Compromised Account: 2 times.
Impersonation: 2 times.
If a CU is interested in how they use the tool, leave me a message, or email me.
I will not automate this script, or release the source code. I will not release data for others usage of the tool for any reason other than a direct request - and even then, only by email, directly to the cu making the request.
Articles for Creation July 2021 Backlog Elimination Drive
Hello SQL:
WikiProject Articles for creation is holding a month long Backlog Drive!
The goal of this drive is to eliminate the backlog of unreviewed articles. The drive is running until 31 July 2021.
Barnstars will be given out as awards at the end of the drive.
There is currently a backlog of over 1100 articles, so start reviewing articles. We're looking forward to your help!
I appreciate your support in my recent run for admin. Please feel free to call on me if I can be helpful or if I make an error. Thanks again. BusterD (talk) 04:48, 17 July 2021 (UTC)
Feedback request: Wikipedia technical issues and templates request for comment
You refer to yourself as "We". Why is that? How many people have access to your account?
Can you describe the nature of your relationship with the subject of that article?
Regarding "All we did was add new sources"... That's not true at all. Let's take a good look at the edits you made there since the release of your block.
One of these edits was adding a new source. It's unwise to say "Look at the history", when I can, and the history does not support your version of what happened.
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.
Don't worry about it. I expected nothing more, although collapsing a discussion immediately after commenting is unacceptable anywhere on Wikipedia. As SQL said, if these behavioural issues continue, they can be discussed elsewhere. This isn't the venue, nor is SQL the editor to blame for the mess. The Rambling Man (Keep wearing the mask...) 23:13, 7 August 2021 (UTC)
OK, apologies to SQL. I dislike it when I see good editors being bullied. I seem to recall I was flayed alive by her for a mass change, but she seems to get away with it, despite being told by numerous editors to stop. - Aussie Article Writer (talk) 23:16, 7 August 2021 (UTC)
I don't know a nice way to say this - but I have absolutely no time, or interest in getting into that level of drama at this time. !ɘM γɿɘυϘ⅃ϘƧ23:25, 7 August 2021 (UTC)
And if you don't want to get involved, then I suggest you don't re-hat a comment that originally called the person who responds to defend themselves from a personal attack a "troll". TRM might not care, but I certainly do - the editor he responded to has already been desysopped for bullying, and with the greatest of respect, you seem to be tacitly allowing it to continue. - Aussie Article Writer (talk) 23:31, 7 August 2021 (UTC)
The discussion above 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.
Editing the archive to add: I was incorrect above - I had not asked AAR to stay off my talkpage. I had confused them with another editor. !ɘM γɿɘυϘ⅃ϘƧ23:42, 7 August 2021 (UTC)
My Checkuser Stats for July 2021
Like the first half of this year, I'm posting some basic details on how I use the checkuser tool. This is based on running regular a series of regular expressions over the CU log, and might not be accurate. Some items are probably not optimally named.
These are the aggregate reasons for using it (Keep in mind that one investigation often involves more than one check):
Unblock-related: 156 times.
SPI case: 29 times.
LTA related: 14 times.
Block evasion: 10 times.
If a CU is interested in how they use the tool, leave me a message, or email me.
I will not automate this script, or release the source code. I will not release data for others usage of the tool for any reason other than a direct request - and even then, only by email, directly to the cu making the request.
(Replying to User talk:Wolverine1203 since it didn't seem like a conversation appropriate to a new users' talk page.)
Please look at the CU and contributions for the range. I went for the closest-sounding template so colocation may not be the best word for it, but it belongs to a company that provides a VPN for coworking offices. The result is multiple users from multiple locations in the US sharing the same pool of obscured IPs that geolocate to New York, which I believe violates both the spirit and letter of our proxy policy. With the exception of occasional use by (IIRC) one established editor, it has almost exclusively been used for spam, UPE and sockpuppetry. – Joe (talk) 13:57, 21 August 2021 (UTC)
So I would argue that that's not really an "open proxy" - it obscures the user's location, sure, but is only available to a fairly restricted set of people. Not saying that there aren't problems on that range (obviously, I don't know which one, just going off of Joe's comment above) but I'm not sure that our proxy policy justifies preemptively blocking that. As a comparison, I'm pretty sure SubjectiveNotability's contribs (often made from my work computer) show up in a different state than where I'm actually editing from, since I think the company routes most traffic through one of the other offices. Doesn't mean anyone is trying to obfuscate anything. GeneralNotability (talk) 19:43, 22 August 2021 (UTC)
Your backwards signature...
...is quite cool, and I hadn't found it offputting at all, until I was just attempting to review a certain exceedingly long user talk page to find some comments you had made. CtrlF + sql didn't work for me - I'm guessing that it didn't like the backwards letters - so I had to search the history to find the diffs and work it out from there. I'm not demanding that you change it or anything, just letting you know that's a thing, in case you hadn't considered it. Cheers GirthSummit (blether)17:02, 26 August 2021 (UTC)
Could you look at UTRS appeal #47301. It says, "Hello Wikipedia Support, I am contacting you from Netcrawler Network support. We are an ISP that is registered to operate in Canada. You have previously blocked 172.110.128.0/18. However, part of that range belongs to Netcrawler now. IP Range 172.110.176.0/22 was transferred to us by ARIN earlier this summer. You can validate this by verifying our ASN number which is AS399337. Can you please unblock our range as many of our home subscribers are unable to edit Wikipedia pages. Thanks" --Deepfriedokra(talk)16:29, 2 September 2021 (UTC)
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.
Technical news
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.
Arbitration
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.
Reply-link officially superseded by DiscussionTools
Hi! Reply-link has officially been superseded by mw:DiscussionTools, which you can install using the "Discussion tools" checkbox under Preferences → Beta features. DiscussionTools, developed by the WMF's Editing Team, is faster and has more features than reply-link, and it wouldn't make sense for me to keep developing reply-link. I think the Editing Team is doing amazing work, and look forward to what they can do in the future. Thank you for using reply-link over the years! Enterprisey (talk!) 06:11, 6 September 2021 (UTC)
Feedback request: Wikipedia proposals request for comment
@Bbb23: Indeed, they made many errors with the {{unblock}} template. I'd be willing to bet that they have the experience needed to put together a coherent unblock request. SQLQuery Me!13:06, 9 September 2021 (UTC)
(edit conflict) It looks like they tried to add a table to the unblock request, and it was completely screwed up. The problem is that before your decline, it looked like a stupid unblock request, not a mangled one, but the decline looks mangled. Although the user is a troll and doesn't deserve all this attention, perhaps it would be best to revert to before the unblock request and tell the user they have to formulate a correct unblock request if they want it reviewed. The other option would be to try to fix their unblock request before declining it. I assumed before I looked at the edit history that you had declined it and the user had vandalized your decline. :-) --Bbb23 (talk) 13:16, 9 September 2021 (UTC)
Source: Available on request. Private version control access is available upon request at my discretion.
Notes: Tool isn't done / is barely ready. See TODO's in the HTML comments. Currently limited to IPv4. Wikitext output isn't up and running yet. SQLQuery Me!08:07, 12 September 2021 (UTC)
Feedback request: Wikipedia policies and guidelines request for comment
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.
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.
Miscellaneous
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.
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.
Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
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)
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.