User talk:SQL

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. SQL^{Query me!} 04:27, 21 April 2020 (UTC)

The (WMF) suffix is protected by meta:Title blacklist, which does raise the bar from "anyone with an unblocked IP address" to "someone who can SE an editor with the right permissions into creating the account". --AntiCompositeNumber (talk) 04:58, 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. SQL^{Query 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. SQ1L^{Query 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. SQL^{Query 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! $\sideset {_{R}^{u}}{_{u}^{y}}\prod _{\clubsuit }^{i}$ ${}_{S}^{h}\!\Omega _{n}^{e}$ 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. SQL^{Query 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)

Thank you kindly.$\sideset {_{R}^{u}}{_{u}^{y}}\prod _{\clubsuit }^{i}$ ${}_{S}^{h}\!\Omega _{n}^{e}$ 04:55, 2 May 2020 (UTC)

Request to RD1 content

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)

Primefac, Oshwah is there any way either of you could help OcelotCreeper out here please? SQL^{Query me!} 04:16, 2 May 2020 (UTC)

The future of IPCheck

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.

Effective immediately, I have frozen/archived the public codebase at commit ce9657c8eb39485114aace57594d39aee47b3bea.

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. SQL^{Query me!} 04:59, 2 May 2020 (UTC)