Page MenuHomeMiraheze

Allow content to be reported from wiki pages
Open, LowPublic

Description

In order to improve the ease and accessibility of access to Trust and Safety, we should allow content and perhaps even wikis/users in general to be reported directly to TSPortal via buttons within the MediaWiki interface.

Event Timeline

Owen triaged this task as Low priority.Jul 17 2022, 15:47
Owen created this task.
Unknown Object (User) added a comment.Jul 17 2022, 15:53

This can probably be done by either extending the RemovePII extension, or creating a new extension, but my issue is a UI perspective, I am not certain how to do this in wiki pages that will work and appear good on all skins. My suggestion would be maybe a sidebar link (Like ManageWiki links) to a special page allowing reporting it. But even that, I don't know what to call the special page? I also don't know (yet, but may be able to figure it out) how to make a special page submission actually submit to an API to create the report/DPA in TSPortal. If you have any suggestions for how you would like this done, please do let me know. Thank you!

Unknown Object (User) moved this task from Backlog to Long Term on the MediaWiki (SRE) board.Sep 12 2022, 22:16
Unknown Object (User) moved this task from Backlog to MediaWiki on the Goal-2022-Jul-Dec board.
Unknown Object (User) moved this task from Long Term to Goals on the MediaWiki (SRE) board.Sep 12 2022, 22:18

This can probably be done by either extending the RemovePII extension, or creating a new extension, but my issue is a UI perspective, I am not certain how to do this in wiki pages that will work and appear good on all skins. My suggestion would be maybe a sidebar link (Like ManageWiki links) to a special page allowing reporting it. But even that, I don't know what to call the special page? I also don't know (yet, but may be able to figure it out) how to make a special page submission actually submit to an API to create the report/DPA in TSPortal. If you have any suggestions for how you would like this done, please do let me know. Thank you!

This is a very late comment but I did actually have that idea previously though there's a few issues. One of them is that a "Report" button would have to link to a regular page on Meta which would explain what needs to be reported to CVT and what needs to be reported to T&S, to avoid people going to T&S for everything. I would say adding it to RemovePII wouldn't make much sense as that extension is really specific to removing PII.

The easiest I would say is probably to include such a link in the sidebar and the footer and save the trouble, though admittedly a "button" like for example the ones on the Main Page would look nicer

Unknown Object (User) added a comment.Dec 19 2022, 16:59

My idea here is to create an action (?action=report) that will be forum to allow content to be immediately reported. Alternatively, a link could be added, that upon click opens a JavaScript-powered OOUI popup to report content. I am not sure the best approach here.

Your JavaScript OOUI popup idea would make this much more easier, as we could just add an API on MW for logged-in users (or allow everyone and auto-generate usernames for anons, maybe?) that would act as a proxy to the TSPortal API (so that we don't have to reveal the writekey to the user), then make a form with JavaScript and call the API from JS, but that would exclude users without JavaScript, or users that have disabled JavaScript on specific wikis (I for example only allow JavaScript on Meta and Phabricator, as you never know what interface admins on other wikis have on their site js when you first visit it).

A more universal solution would be to use an special page in place of the JavaScript form, maybe even lifting some code over from the RequestWiki form and modifying it to mimic the form at TSPortal.

But for me, the real issue here is where do we put the report button? Take Vector 2022 for example (not even talking about the other skins, that's a whole another issue), you could put it in:

  • The sidebar (in which case, where in the sidebar?).
  • The "more" menu.
  • At the bottom of the article, for example where the [Mark as patrolled] button appears.
  • At the page footer, next to the "Privacy policy, etc" links.

None of these sound ideal to me. There's also the fact that the community should be consulted to see what they think of this, as there's likely to be backlash if this is enabled on production without consulting.

Perhaps in the tools section of the sidebar where it'd fit in best. Adding another footer link could also work.

Unknown Object (User) moved this task from Backlog to MediaWiki on the Goal-2023-Jan-Jun board.

The main issues with all these proposals is that they seem to want to report things to T&S directly, which should not be the case. 95% of content can and should be reported to the CVT team, only (seriously) illegal content should be reported to T&S.

If we added a Report button users would surely not make the difference between reporting serious things to T&S and reporting less serious matters to CVT and would use the Report button for everything, which we don't want as T&S itself always defers to CVT when possible, so it would just create more work for them.

What I'd propose then is that clicking the button would either: (a) simply link to a page on Meta where it's proposed that they either report to CVT or T&S depending on the circumstances or (b) a pop-up of some sorts which also gives these two options (but it has to be detailed what falls under T&S' scope)

Could this work something like Twinkle?

The issue is that it would have to be something available to all users, not something that needs enabling like a Gadget.

I just mean "something like" Twinkle. I sent Agent Isai a copy of a prototype but I don't know if they've tried it out yet. If they don't like that one, I will try something else via the backend

I just mean "something like" Twinkle. I sent Agent Isai a copy of a prototype but I don't know if they've tried it out yet. If they don't like that one, I will try something else via the backend

That could work. Though how would you plan on handling the Stewards/Global Sysops vs. T&S issue?

@Reception123 Which one could work? The first or the second?

As for "handling the issue", those things are supposed to be discussed rather than decided by whoever is making the feature. I could do whatever makes the most sense to me, but then what happens to everyone else?

@Reception123 Which one could work? The first or the second?

As for "handling the issue", those things are supposed to be discussed rather than decided by whoever is making the feature. I could do whatever makes the most sense to me, but then what happens to everyone else?

That's the issue. There's nothing to discuss really, the current rules are that most things go to Stewards and Global Sysops and only very serious illegal activity is reported to T&S. In some cases, Stewards/GS may choose to pass on reports to T&S themselves, but in either case every report should not go to T&S first. So what I am asking (and I don't have an answer myself) is how the tool can be made to include both cases.

I was thinking something like an option to choose between the two, but it would have to include an explanation. Such as Stewards/GS --> Everything, T&S --> Only very serious violations which are illegal under UK law

I meant the discussion of how the interface should work, not the discussion of what the rules are.

@Agent_Isai Have you had a chance to try out the current working version? Will it work or not? If not, I will try making something else

An option is to put the item under the tab that says 'Move', 'Purge', and for sysops on wikis 'Delete', we could add another tab that says 'Report', which would take the user to Special:Report, with the page filled in and all that.

@BrandonWM Only the Vector and Vector-2022 skins work like that. No other skins do. Actions are handled outside of skin-specific stuff but it depends on what people want. I thought people wanted something in the toolbox, as otherwise this would too easily repeat the mistakes of the Report extension

@Agent_Isai Have you had a chance to try out my prototype yet?

The Move/Purge/Delete tab is usually more familiar to administrators rather than regular users so I wouldn't think it would be a good idea to have it there and also because as Naleksuh says, many skins are different.

Unknown Object (User) unsubscribed.Mar 18 2023, 03:30