Council/tickets
1
0
Fork 0
Code Issues 12 Pull requests Projects Releases Packages Wiki Activity Actions

CSAM on Matrix: Request for Council Legal & Resource Support #530

New issue
Open
opened 2025-05-23 22:19:40 +00:00 by jflory7 · 1 comment
jflory7 commented 2025-05-23 22:19:40 +00:00
Contributor
Copy link

Summary

Request for Fedora Council to provide legal support, strategic guidance, and resources to address the escalating issue of Child Sexual Abuse Material (CSAM) attacks on Fedora's Matrix communication platforms and to support our community moderators.

Background

Fedora's Matrix channels have been subjected to increasing waves of malicious attacks involving the posting of Child Sexual Abuse Material (CSAM). This content, which inherently depicts the abuse of minors, is graphically disturbing and psychologically harmful. These attacks, often originating from external, untrusted federated Matrix servers, create a hostile environment, place a significant emotional and operational burden on our volunteer Matrix moderators, and have resulted in CSAM being viewed by community members, including a minor using an independent Matrix account. Current reactive measures are insufficient to manage this escalating problem, which now occurs on a near-daily basis, necessitating a more comprehensive and supported strategy.

Details

To effectively address this critical issue, I request the Fedora Council to undertake the following actions:

  1. Facilitate Legal Consultation: Initiate and support consultation with Red Hat Legal, and potentially other external legal specialists, to:

    • Clarify Fedora's legal obligations regarding CSAM encountered on its platforms (e.g., reporting, data handling, content removal), particularly considering the complexities of federated systems and potential future self-hosting of more Matrix infrastructure components.
    • Provide guidance on developing legally sound Acceptable Use Policies (AUPs) and incident response protocols for CSAM.

  2. Secure HR and Well-being Support Guidance: Facilitate consultation with Human Resources experts or similar specialists to identify and recommend resources or strategies for providing psychological support, counseling, and well-being programs for volunteer moderators exposed to CSAM.

  3. Empower and Support the Fedora Matrix Working Group:

    • Formally recognize and task the Fedora Matrix Working Group (a sub-team of the Community Operations team) with leading the development and implementation of a comprehensive CSAM incident response plan.
    • Request the Matrix Working Group to nominate a dedicated liaison to the Fedora Council for ongoing communication and coordination on this issue.
    • Consider sponsoring this work as a Fedora Community Initiative to provide structure, visibility, and appropriate resourcing.

  4. Explore Resource Allocation: Investigate and identify options for allocating Fedora Project funds or resources towards:

    • Acquiring or developing enhanced moderation tools suitable for detecting and managing CSAM in a federated environment.
    • Providing specialized training for volunteer moderators on handling CSAM, operational security, and self-care.
    • Supporting other necessary measures identified by the Matrix Working Group and legal advisors.

  5. Foster a Collaborative Approach:

    • Support the Matrix Working Group in addressing this as a collaborative challenge, recognizing that Fedora is not alone and that other open source communities and the Matrix Foundation are also working on these issues.
    • Encourage the sharing of learnings and best practices with the wider open source ecosystem where appropriate.

This effort should aim to address both the immediate, critical need to scale and improve our CSAM moderation capabilities and the long-term need to establish sustainable systems for community protection. It is important to note that currently, the CSAM encountered is understood to be hosted on external federated servers, not Fedora Project infrastructure. However, proactive legal guidance is crucial as we plan the future of our Matrix platform.

Outcome

A comprehensive, legally sound, and sustainable framework is established to protect the Fedora Project community from CSAM, effectively support our volunteer moderators, and help ensure Fedora's communication platforms are safer and more welcoming for all users.

# Summary Request for Fedora Council to provide legal support, strategic guidance, and resources to address the escalating issue of Child Sexual Abuse Material (CSAM) attacks on Fedora's Matrix communication platforms and to support our community moderators. # Background Fedora's Matrix channels have been subjected to increasing waves of malicious attacks involving the posting of Child Sexual Abuse Material (CSAM). This content, which inherently depicts the abuse of minors, is graphically disturbing and psychologically harmful. These attacks, often originating from external, untrusted federated Matrix servers, create a hostile environment, place a significant emotional and operational burden on our volunteer Matrix moderators, and have resulted in CSAM being viewed by community members, including a minor using an independent Matrix account. Current reactive measures are insufficient to manage this escalating problem, which now occurs on a near-daily basis, necessitating a more comprehensive and supported strategy. # Details To effectively address this critical issue, I request the Fedora Council to undertake the following actions: 1. **Facilitate Legal Consultation**: Initiate and support consultation with Red Hat Legal, and potentially other external legal specialists, to: * Clarify Fedora's legal obligations regarding CSAM encountered on its platforms (e.g., reporting, data handling, content removal), particularly considering the complexities of federated systems and potential future self-hosting of more Matrix infrastructure components. * Provide guidance on developing legally sound Acceptable Use Policies (AUPs) and incident response protocols for CSAM. 2. **Secure HR and Well-being Support Guidance**: Facilitate consultation with Human Resources experts or similar specialists to identify and recommend resources or strategies for providing psychological support, counseling, and well-being programs for volunteer moderators exposed to CSAM. 3. **Empower and Support the Fedora Matrix Working Group**: * Formally recognize and task the Fedora Matrix Working Group (a sub-team of the Community Operations team) with leading the development and implementation of a comprehensive CSAM incident response plan. * Request the Matrix Working Group to nominate a dedicated liaison to the Fedora Council for ongoing communication and coordination on this issue. * Consider sponsoring this work as a Fedora Community Initiative to provide structure, visibility, and appropriate resourcing. 4. **Explore Resource Allocation: Investigate and identify options for allocating Fedora Project funds or resources towards**: * Acquiring or developing enhanced moderation tools suitable for detecting and managing CSAM in a federated environment. * Providing specialized training for volunteer moderators on handling CSAM, operational security, and self-care. * Supporting other necessary measures identified by the Matrix Working Group and legal advisors. 5. **Foster a Collaborative Approach**: * Support the Matrix Working Group in addressing this as a collaborative challenge, recognizing that Fedora is not alone and that other open source communities and the Matrix Foundation are also working on these issues. * Encourage the sharing of learnings and best practices with the wider open source ecosystem where appropriate. This effort should aim to address both the immediate, critical need to scale and improve our CSAM moderation capabilities and the long-term need to establish sustainable systems for community protection. It is important to note that currently, the CSAM encountered is understood to be hosted on external federated servers, not Fedora Project infrastructure. However, proactive legal guidance is crucial as we plan the future of our Matrix platform. # Outcome A comprehensive, legally sound, and sustainable framework is established to protect the Fedora Project community from CSAM, effectively support our volunteer moderators, and help ensure Fedora's communication platforms are safer and more welcoming for all users.
jflory7 commented 2025-05-23 22:25:03 +00:00
Author
Contributor
Copy link

See linked Fedora Discussion topic for Ticket #530

## [_See linked Fedora Discussion topic for Ticket #530_](https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-530-csam-on-matrix-request-for-council-legal-resource-support/154401)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
budget
  
Closed As
approved
Closed with the reason of approved

  
Closed As
declined
Closed with the reason of declined

  
Closed As
deferred
Closed with the reason of deferred

  
Closed As
duplicate
Closed with the reason of duplicate

  
Closed As
no action needed
Closed with the reason of no action needed

  
Closed As
resolved
Closed with the reason of resolved

  
code-of-conduct

   
documentation

   
elections

   
events

   
hackfests

   
initiatives

   
In Progress

Topics that are being actively discussed orworked on

  
mindshare

   
Needs Review

   
Next Meeting

For tickets that need to be discussed at the next council meeting

  
policies

   
spending-request

"Budget" is for big-picture things. This is for as-we-go allocations.

  
ticket-vote

Hey, council members: Let's vote on this in this ticket, right now!

  
trademarks

   
urgent
No labels
budget
Closed As
approved
Closed As
declined
Closed As
deferred
Closed As
duplicate
Closed As
no action needed
Closed As
resolved
code-of-conduct
documentation
elections
events
hackfests
initiatives
In Progress
mindshare
Needs Review
Next Meeting
policies
spending-request
ticket-vote
trademarks
urgent
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Council/tickets#530
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?