In T10568#219220, @Dmehus wrote:

I would probably suggest keeping this separate from the actual TSportal. That being said, I think the TSportal codebase could be forked to provide a separate OSrequests portal.

I would probably suggest keeping this separate from the actual TSportal. That being said, I think the TSportal codebase could be forked to provide a separate OSrequests portal. Ideally, I would prefer TSportal to be moved to a more specific subdomain, perhaps tsreports.miraheze.org, and then the OSrequests portal could live at osrequests.miraheze.org (or something like that). You get the idea. But in general, I like the idea of using this for OS requests. :)

In T10551#212505, @BrandonWM wrote:

@Owen To clarify, you mean add “DPA” as an option under the Reports tab? DPA stands for Data Protection, which is already an option on the main bar at TSPortal, though for categorization, not creating a report.

Or do you mean adding it as an option under the “+” button to create a new report, alongside Data Protection and Report?

Or both? (also if that was confusing, apologies, happy to clarify if necessary)

@Owen To clarify, you mean add “DPA” as an option under the Reports tab? DPA stands for Data Protection, which is already an option on the main bar at TSPortal, though for categorization, not creating a report.

In T10439#210352, @Universal_Omega wrote:

https://github.com/Universal-Omega/DiscordNotifications/pull/19 — this will allow us to basically use the PageSaveComplete hook (and other hooks for other types of checks), then the new services this introduces, and basically like this (where the embedFields uses the new DiscordEmbedBuilder service to add fields to the embed):

$discordNotifier = MediaWikiServices::getInstance()->getService( 'DiscordNotifier' );
$message = 'Text matched x';
// might need to support other actions also
$action = 'article_saved';
// this would be changed to get and truncate content to only a certain number of characters before and after the relevant match
$embedFields = [ 'summary' => $summary, 'content' => '(content)' ];
// Would be a private config, and used as the webhook for specific matches only
$webhook = 'xxxx';
$discordNotifier->notify( $message, $user, $action, $embedFields, $webhook );

Of course that is just a proof of concept, nothing working yet, but the patch works to maintain current functionality also (already tested), though it might be kinda messy implementation here, we can probably add a new DiscordMatchNotifierHooks.php file (or something similar, maybe not exact name) in MirahezeMagic for the hooks to notify to Discord.

https://github.com/Universal-Omega/DiscordNotifications/pull/19 — this will allow us to basically use the PageSaveComplete hook (and other hooks for other types of checks), then the new services this introduces, and basically like this (where the embedFields uses the new DiscordEmbedBuilder service to add fields to the embed):

My CVTBot supports edit summaries (not text as wanted here) with command (including Regex support) (based on #miraheze-feed), I thought about initially letting it use MW API, but it seems like it would cause excessive requests, and performance impact in addition to rate limiting. It uses the API for some things, like getting interface messages, and admin and bot lists, but using it for everything seems like it would have some impact.

The existing IRC feed bots analyze the postings in the main #miraheze-feed channel and relay matching patterns/strings etc to the cvt feed. To be able to look at changed/added text, it would have to use the MW api.

In T10167#209881, @OrangeStar wrote:

@Owen What elements from the DPA do you want to be able to copy via left-click?

@Owen What elements from the DPA do you want to be able to copy via left-click?

New PR to get the rest of the task done: https://github.com/miraheze/TSPortal/pull/10

PR got merged, only thing missing now is to add the copyToClipboard class to any elements whose text should be copied when clicked.

https://github.com/miraheze/TSPortal/pull/8

This has now been completed - POST requests can be sent to /api/report and /api/dpa to generate these requests.

If this is now low priority it can be raised again.

This can be started once the appeals process is reviewed at the Board meeting tomorrow.

This is now done within RemovePII, it will be deployed alongside our 1.38 upgrade, as it won't work on 1.37.

https://github.com/miraheze/RemovePII/pull/57