Skip to content
This repository has been archived by the owner. It is now read-only.
Bridge between Telegram and Matrix
Branch: master
Clone or download
Latest commit 4206b4f Aug 14, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
telematrix Log to console when there is an error joining the room Feb 1, 2018
.gitignore Revert .gitignore to correct version Nov 2, 2017
.travis.yml Fix CI Nov 16, 2016
LICENSE Initial commit Sep 13, 2016
README.md
app_service.py Fix CI Nov 16, 2016
asconfig.yaml.example added example configuration Oct 8, 2016
config.json.example Make Matrix AS port configurable. Fixes #35 Oct 18, 2017
requirements.txt Add rudimentary sticker support (#25) Feb 19, 2017

README.md

DEPRECATED

Use tulir/mautrix-telegram instead. It's much better.

Old README.md for reference:

telematrix

A bridge between Telegram and Matrix. Currently under development — this project isn't considered to be in a usable state right now.

Usage

After the 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:

virtualenv venv -p $(which python3)
. venv/bin/activate

Then install the requirements using pip:

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.

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:

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!

You can’t perform that action at this time.