Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/vijfhoek/telematrix
Bridge between Telegram and Matrix
https://github.com/vijfhoek/telematrix
bot bridge matrix telegram-chat
Last synced: about 1 month ago
JSON representation
Bridge between Telegram and Matrix
- Host: GitHub
- URL: https://github.com/vijfhoek/telematrix
- Owner: vijfhoek
- License: mit
- Archived: true
- Created: 2016-09-13T14:17:35.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2018-08-14T17:37:52.000Z (about 6 years ago)
- Last Synced: 2024-06-17T19:59:08.910Z (3 months ago)
- Topics: bot, bridge, matrix, telegram-chat
- Language: Python
- Homepage:
- Size: 54.7 KB
- Stars: 98
- Watchers: 15
- Forks: 20
- Open Issues: 34
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-starred - vijfhoek/telematrix - Bridge between Telegram and Matrix (bot)
README
# *DEPRECATED*
Use [tulir/mautrix-telegram](https://github.com/tulir/mautrix-telegram) instead. It's much better.
*Old README.md for reference:*
# telematrix
A bridge between Telegram and [Matrix](http://matrix.org/). Currently under development — this project isn't considered to be in a usable state right now.
## Usage
After the [installation](#installation), follow these steps to bridge a matrix room to a telegram group chat or channel:
- Invite the bot to the telegram chat.
- Send `/alias` in the telegram chat.
- The bot will answer with an alias, something like `#telegram_-XXXXXXXXX:yourserver.example`. Add that as an alias to the matrix room you want to bridge.
In case it doesn't work make sure that all these are true:
- You are on the same server as the bridge. If that is not the case, you can't set the alias, because you can only set aliases on the server you are on.
- The matrix room is not set to invite only. The bridge currently doesn't support invite only rooms, so the rooms must be set to be open for all. Guests access is not required though.
## Installation
### Dependencies
First, create a virtualenv and activate it:
```bash
virtualenv venv -p $(which python3)
. venv/bin/activate
```
Then install the requirements using pip:
```bash
pip install -r requirements.txt
```
### Configuration
**telematrix configuration**
First, copy config.json.example to config.json. Then fill in the fields:
* `tokens.hs`: A randomly generated token
* `tokens.as`: Another randomly generated token
* `tokens.telegram`: The Telegram bot API token, as generated by @BotFather
* `tokens.google`: A Google API key, used for URL shortening. Can be left out to disable.
* `hosts.internal`: The homeserver host to connect to internally.
* `hosts.external`: The external domain of the homeserver, used for generating URLs.
* `hosts.bare`: Just the (sub)domain of the server.
* `user_id_format`: A Python `str.format`-style string to format user IDs as
* `db_url`: A SQLAlchemy URL for the database. See the [SQLAlchemy docs](http://docs.sqlalchemy.org/en/latest/core/engines.html).
**Synapse configuration**
Copy asconfig.yaml.example to asconfig.yaml, then fill in the fields:
* `url`: The host and port of telematrix. Most likely `http://localhost:5000`.
* `as_token`: `token.as` from telematrix config.
* `hs_token`: `token.hs` from telematrix config.
The rest of the config can be left as is. Finally, add a relative path to this config file in the Synapse's homeserver.yaml:
```yaml
app_service_config_files:
- "../telematrix/asconfig.yaml"
```
## Contributions
Want to help? Awesome! This bridge still needs a lot of work, so any help is welcome.
A great start is reporting bugs — if you find it doesn't work like it's supposed to, do submit an issue on Github. Or, if you're a programmer (which you probably are, considering you are on this website), feel free to try to fix it yourself. Just make sure Pylint approves of your code!