PC-Admin/redlight
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
An advanced abuse management tool. It's a Synapse module that allows server owners to safely host rdlist, or use rdlist to prevent users from accessing tagged rooms.
13 Commits 2 Branches 0 Tags 251 KiB
Python 100%
f52b0c39dc
Go to file
PC-Admin f52b0c39dc update technical again
2023-08-11 04:41:11 +08:00
logo initial commit, simple hello world module hooked into user_may_join_room() 2023-08-09 23:02:59 +08:00
notes update redlight client module to double hash the room_id with sha256 2023-08-11 03:30:40 +08:00
LICENSE Initial commit 2023-08-03 08:24:35 -04:00
README.md update technical again 2023-08-11 04:41:11 +08:00
redlight_client_module.py update redlight client module to double hash the room_id with sha256 2023-08-11 03:30:40 +08:00
redlight_server_module.py create initial redlight_server_module.py script 2023-08-11 02:27:33 +08:00
style_guide.md initial commit, simple hello world module hooked into user_may_join_room() 2023-08-09 23:02:59 +08:00
technical_spec.md update technical again 2023-08-11 04:41:11 +08:00

README.md

redlight

redlight logo

"The red light means STOP!"

An advanced abuse management tool. It's a Synapse module that allows server owners to either run a "redlight server", or to act as a "redlight client" to prevent their own users from accessing abusive rooms. It's designed to block child sexual abuse material (CSAM) and other abusive content on the Matrix network.

This software attempts to resolve the complex problem of how to share pointers to rooms containing abusive content in order to block or report activity. These room lists are sensitive and sharing them can not only aid people in blocking this content but also direct bad actors to said content.

The goal of this tool is to simply block this content as efficiently as possible across many small-medium sized servers.

Features

Easy, setup for homeserver owners via Synapse Module
Private, hashing is used to prevent redlight clients from sharing room_ids with redlight servers
Decentralised, many people can run redlight servers with their own blocking policies, redlight clients are free to pick a provider
Safe, access restrictions and ratelimiting are used to guard the content of Redlight list

How it Works

"Redlight servers" will be trusted homeservers that are modified, they'll cache Redlight list in memory while providing an API interface to "Redlight clients". Redlight servers will pick their own "content tags" that they are filtering, which by extension will allow clients to pick a level of filtering that suits them.

Redlight clients will be untrusted homeservers that are whitelisted by their desired Redlight server. When a user on a client homeserver attempts to join a room, the hash of the room_id will be sent to the redlight server, which will confirm or deny if the room is abusive, the client then denies the user entry to that room if it is flagged.

For a more detailed description of how it will work please consult the Technical Specification.

Coming soon...

License

This project is licensed under the MIT License.

Contributing

We warmly welcome contributors who are interested in improving Matrix Lantern. Whether you're fixing bugs, improving documentation, or proposing new features, your efforts are greatly appreciated. Please ensure that new contributions follow our Style Guide.

Acknowledgements

Redlight is a community-driven project aimed at protecting the Matrix network's users from harmful content. Our thanks go out to the Matrix network, Glowers Club, and all our contributors who make this project possible.

Roadmap

  1. Get a basic prototype working.