Kumi
4f13125c4e
Introduced a new template for the bridge configuration in the matrix_double_puppeting_bridge project, defining necessary parameters such as homeserver details, appservice information, and external service integration. This template lays the groundwork for customizable bridge deployment. Updated the `.gitignore` to track the default configuration files, ensuring they are version-controlled for template consistency and ease of updates. This change facilitates the initial setup process for users by providing a clear and structured configuration file template. It is a step towards simplifying the deployment and customization of the bridge, making it more accessible for administrators to integrate their services with the Matrix protocol. |
||
---|---|---|
src/matrix_double_puppeting_bridge | ||
.gitignore | ||
LICENSE | ||
pyproject.toml | ||
README.md |
Matrix Double Puppeting Bridge
This is a simple demonstration of how to write a Matrix double puppeting bridge using the mautrix-python library.
At this point, it is not complete. It is a work in progress I am using to learn how to write a Matrix bridge, and one I hope I will be able to fork and use as a starting point for future projects.
What is a double puppeting bridge?
A double puppeting bridge handles multiple users on both sides of the bridge. Each user on Matrix is represented by an individual account on the remote service, and each user on the remote service is represented by an individual puppet account on Matrix.
How does it work?
The bridge listens for messages on the Matrix side and sends them to the remote service. It also listens for messages on the remote service and sends them to the Matrix side.
License
This project is licensed under the MIT License. See the LICENSE file for details.