Zache added a comment.
@taavi Adding Superset support to Pywikibot was pretty one of the first use cases for Superset when it published the replica access, and the point of it is that it doesn't require a Toolforge account as because managing the new Toolforge accounts doesn't scale. For example, there are security reasons not to create Toolforge accounts for random workshop participants or, in our current case, for Outreachy contribution period volunteers, if nothing else. Using OAuth login and HTTP API will scale to that usecase. Another thing is that this affects other tools too, not just superset. For example, Wikimedia Commons Query Service, which is used and it is meant to be used from bots. Also If the general idea is to put tools behind OAuth, then it will become a problem pretty fast for the bots and other server side tools, which you need to address. (i.e., https://meta.wikimedia.org/wiki/Third-party_resources_policy) TASK DETAIL https://phabricator.wikimedia.org/T408286 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/
_______________________________________________ pywikibot-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
