Addshore added a comment.
This should be verified once deployed.
This should be deployed on the evening of the 17th October.
We can verify by making sure the query service gets requests with the new UATASK DETAILhttps://phabricator.wikimedia.org/T204471EMAIL
gerritbot added a comment.
Change 463923 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Set custom user agent in SparqlHelper
https://gerrit.wikimedia.org/r/463923TASK DETAILhttps://phabricator.wikimedia.org/T204471EMAIL
gerritbot added a comment.
Change 463923 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/WikibaseQualityConstraints@master] Set custom user agent in SparqlHelper
https://gerrit.wikimedia.org/r/463923TASK
Smalyshev added a comment.
Rate limiting is bucketing based on IP+User agent, so having distinctive user agent for WBQC is certainly a good idea.TASK DETAILhttps://phabricator.wikimedia.org/T204471EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc:
Lucas_Werkmeister_WMDE added a comment.
TBD / TBA does the query service actually differentiate requests from a single IP with different UAs?
That sounds like a really easy way for any spammer to circumvent a ban, so I would be very surprised if we actually did this tbh.
Proposed UA:
