Because the current method (direct db editing!) is far less than ideal.
Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
app.py: make it possible to block a user from running queries | analytics/quarry/web | master | +9 -2 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | Framawiki | T224376 Create simple admin management tool | |||
Declined | None | T104322 Have an easy way to ban users from Quarry |
Event Timeline
Comment Actions
If the concern is abusive users (as oppose to well-intentioned but clueless ones), just block them on meta and rely on the OAuth block data?
Comment Actions
Change 462534 had a related patch set uploaded (by Framawiki; owner: Framawiki):
[analytics/quarry/web@master] app.py: make it possible to block a user from the site
Comment Actions
Change 462534 merged by jenkins-bot:
[analytics/quarry/web@master] app.py: make it possible to block a user from running queries
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2018-09-24T17:53:08Z] <framawiki> deployed 028a292 on quarry-web-01 T205286 T104322