We’re currently in the trenches of DSA compliance. Part of this involves looking at our use of Discourse, as our discussion board qualifies as an “online platform” under the DSA.
As you may know, there is now a standardised Content Moderation Transparency Report, which removes any flexibility we had previously. An additional requirement on top of this is to submit applicable Statements of Reasons to the DSA Transparency Database, and we’ve run into some limitations with the moderation abilities in Discourse.
In particular, we need to be able to consistently record structured information alongside moderation decisions:
Expanded, custom suspension reasons, which we can align with the DSA’s standardised taxonomy. It’s currently not possible to add additional suspension reasons, rather than renaming the existing predefined reasons
Whether the decision relates to illegal content or a Terms & Conditions violation
The contractual basis for the decision
The information source (user report, own-initiative moderation, Trusted Flagger, etc.)
It doesn’t seem possible to configure custom dropdowns within the suspension UI to capture this information, but please correct me if I’m mistaken. We can provide additional information through the “Email Message” field, but this doesn’t feel like a viable long-term solution, as it puts a lot of responsibility on our moderators and doesn’t give us the structured data we yearn for.
I’d be really interested to know how other EU customers (and Discourse themselves?) are approaching the standardised DSA reporting + Statement of Reasons requirements, and whether any additional functionality in this area is planned. We really don’t want to move away from Discourse, so I hope we can work something out - any advice appreciated!
I did some digging and it does look like we are in scope to use this horrific template. Let me do some due diligence with our lawyer and I’ll come back to you.
I hope you don’t mind, but I’d prefer not to publicly identify my employer from this account. We haven’t yet published a report using the new standardised template, which is what prompted this.
That’s fine, it just makes it a bit harder to help because I don’t know where you are starting from. Theoretically you have a well developed report already (like ours) so I wondered specifically what gaps you have outside of the submission of reasons.
Update for you @Jay-C—we are spec’ing out the work required to add additional data fields for the machine readable report and for submissions to the SOR database. We will update in due course.
Hey @HAWK ! I notice the new DSA features in Experimental, which is super cool! I tried adding some Community Rules, making sure the ‘DSA reporting enabled’ box was checked, but the Community Rules don’t seem to be working - none of the custom options are appearing within the moderation list of reasons. I assume this is known and due to its Experimental nature, but wanted to let you know.
Alright, I DMed myself from an alt account, Flagged it, and handled it as a moderator. Admittedly I do find the workflow a bit confusing as it stands.
The ‘Ground’ entered in /admin/schema/dsa_community_rules appears to become the title of the ‘Community Rule’, which doesn’t feel intuitive
The ‘Ground’ entered in /admin/schema/dsa_community_rules is then shown under the ‘Community Rule’ dropdown in the DSA Classification screen shown above, but I’m not sure this is the best place for it
Neither Ground or Explanation appears to be shown to the end-user for Statement of Reasons purposes (nothing in my alt account inbox or DMs referencing this)
I’m not sure what the relevance of ‘Explanation’ in /admin/schema/dsa_community_rules is at this time, or where it’s shown
Curious what do you think would be a better place to show this?
We’re aware of this gap and are working to include the ground and explanation in moderation notices that we send out.
The explanation is used when submitting statement of records to the transparency database which requires a field to “to explain as to why the information is considered incompatible with a specific section in the service’s terms and conditions. The explanation does not have to repeat the facts and circumstances but can refer to those”
It seems like there are a lot of areas to take moderator action that are not behind flags, like deleting posts, suspending/silencing users. I don’t think I have a way to require moderators to use the flagging system to delete a post either, as opposed to just using the delete/edit buttons.
I’m an American so I’m no DSA expert, is this something that needs to be fixed?
Also, even if I am not subject to the reporting requirements of Article 15, I believe there are no exemptions to Article 17, where the user needs to receive:
where the decision is based on the alleged incompatibility of the information with the terms and conditions of the provider of hosting services, a reference to the contractual ground relied on and explanations as to why the information is considered to be incompatible with that ground
I have set up reasons with references to specific sections of our TOS/Guidelines etc., but I’m not sure if my selection in the DSA classification is actually emailed/displayed anywhere to the affected user? If not, sending the selection in the DSA classification box to the affected user should probably also be considered I think. edit: nvm I see that’s right above this lol
I would also love this just because moderators frequently fail to fill out the explanation box to users, and then I get a lot of questions from people wondering why they were suspended or where their posts are.