Page MenuHomePhabricator
Create Task
Maniphest T165081

Disable Content Translation Tool for non-extenedconfirmed users on English Wikipedia
Closed, DeclinedPublic
Actions

Description

Due to the abuse filter created by the English Wikipedia community, the experience for new users trying to use the Content Translation Tool is now:

  1. Write a translation
  2. Submit it for publication
  3. Solve a CAPTCHA
  4. Get the following error screen which tells them to try to publish again:

Screen Shot 2017-05-11 at 11.27.11 AM.png (951×1 px, 371 KB)

  1. Solve another CAPTCHA
  2. Get the same error screen
  3. Repeat

This is a very broken user experience. Until we can convince the English Wikipedia community to extend this feature to more users, we should just disable it for those users so that they aren't going through such a terrible user experience and wasting their effort. (So far, over 5000 users have written translations only to be hit with this abuse filter when trying to publish.)

Related Objects

Event Timeline

kaldari created this task.May 11 2017, 6:52 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 11 2017, 6:52 PM
kaldari updated the task description. (Show Details)May 11 2017, 6:55 PM
Framawiki subscribed.May 11 2017, 7:29 PM

» T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks

kaldari added a comment.May 11 2017, 8:15 PM

I think we should implement both T114621 and this ticket separately. In the case of this issue, we shouldn't even allow new editors to access the Content Translation Tool, as there is no way for them to meet the requirements of the abuse filter.

Amire80 subscribed.May 18 2017, 12:02 PM

Even if this change is easy to make, I prefer to invest time in fixing the issues that caused people to want the Abuse Filter than in perpetuating it.

First step would be T165562.

Framawiki added a comment.May 18 2017, 4:21 PM

@kaldari it seems to me that users can always publish to one of their subpage, then move page to the main, no ?

Pginer-WMF closed this task as Declined.May 4 2018, 10:38 AM
Pginer-WMF subscribed.

For version 2, we plan to communicate this better (T192144). Currently the destination selector allows a path forward by publishing under the user namespace. If as part of the work on version 2, we can make some improvement to version 1 (make user namespace the default if we detect you cannot publish to main namespace) we'll consider it, but our main focus is on version 2 to make it replace version 1 as soon as possible.

Pginer-WMF mentioned this in T192144: CX2: Communicate that publishing is only allowed to experienced editors.May 4 2018, 10:41 AM
Pginer-WMF mentioned this in T194147: CX1: Communicate that publishing is only allowed to experienced editors .May 8 2018, 11:21 AM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits