No description
Find a file
Kumi 390db18623
feat: add CLI config support and script entry
Introduced command-line argument parsing to allow specifying configuration file paths, enhancing the tool's flexibility for different environments. Additionally, integrated a script entry in pyproject.toml to facilitate direct execution of the bridge, improving usability. The bridge now correctly initializes the matrix client, ensuring proper operation. These changes make deployment and configuration more straightforward, adaptable to user needs.

- Command-line arguments for custom config paths.
- Script entry for easier execution.
- Fixed matrix client initialization in the bridge.
2024-05-20 11:57:12 +02:00
src/matrix_double_puppeting_bridge feat: add CLI config support and script entry 2024-05-20 11:57:12 +02:00
.gitignore feat: Add bridge config template 2024-05-20 11:50:49 +02:00
LICENSE feat: Initialize Matrix double puppeting bridge project 2024-05-16 10:10:19 +02:00
pyproject.toml feat: add CLI config support and script entry 2024-05-20 11:57:12 +02:00
README.md feat: Initialize Matrix double puppeting bridge project 2024-05-16 10:10:19 +02:00

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.