This user is busy in real life and may not respond swiftly to queries.
This user has CheckUser privileges on the English Deep web.
This user has administrator privileges on the English Deep web.
This user is an Arbitration clerk on the English Deep web.

User talk:SQL

From Deep web, the free encyclopedia
  (Redirected from User:SQL)
Jump to navigation Jump to search

Deep web Administrator.svgThis user has been an admin for
12 years, 4 months and 21 days.
Deep web Checkuser.svgThis user has checkuser rights on the English Deep web. (verify)
Clerk-fez.pngThis user is a clerk for the Arbitration Committee.
164 Users were created in the last hour


Hi SQL, all the best and a prosperous 2020! Today I checked (not cached) and the IPQualityScore section said Proxy/Recent abuse/Bot/Score 100. Checking against where is said No proxy/No spam/Score 28. Any ideas? --Achim (talk) 12:50, 9 January 2020 (UTC)

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 see, thank you very much. So we can trust ipcheck's info ;) Cheers, --Achim (talk) 15:12, 9 January 2020 (UTC)


Sorry about the fat finger mobile rollback. (I will remove rollback from my mobile skin.) Levivich 22:04, 29 January 2020 (UTC)

Levivich, No problem. SQLQuery me! 22:08, 29 January 2020 (UTC)

IRC help[edit]

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. Bobherry Talk Edits 10:56, 4 February 2020 (UTC)

Bobherry, #wikipedia-en-help connect SQLQuery me! 17:01, 4 February 2020 (UTC)
I mean the helper channel not the help. I could connect to help but not helper Bobherry Talk Edits 22:12, 4 February 2020 (UTC)
Bobherry, #wikipedia-en-helpers connect SQLQuery me! 22:28, 4 February 2020 (UTC)
Thanks. Bobherry Talk Edits 22:54, 4 February 2020 (UTC)

Deep web:Arbitration/Requests/Case/Kudpung/Workshop edits[edit]

I made 2 edits not realizing you'd closed the case. One was a clarification I felt was necessary and the other an apology for editing after close. If you feel these edits should be removed, please do so (link provided to make it easier for you). Buffs (talk) 17:01, 6 February 2020 (UTC)

Buffs, Not a big deal at this point. I hadn't seen this until just now (work and all). SQLQuery me! 04:23, 7 February 2020 (UTC)

Bot problem: stale?[edit]

Hi there, please review this, immediately following this. Thanks - DVdm (talk) 09:38, 14 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)
Ok, thanks! - DVdm (talk) 12:51, 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)
Asynchronicity has always been a tough one. Keep up the good work! :-) - DVdm (talk) 22:58, 14 February 2020 (UTC)