iartamonov/mautrix-telegram

T

Tulir Asokan cb0d931652 Add JSDocs to app.js (ref #1 )

2017-11-21 17:32:10 +02:00

Add script to download older telegram-mtproto commit

2017-11-20 21:46:59 +02:00

Add JSDocs to app.js (ref #1 )

2017-11-21 17:32:10 +02:00

.editorconfig

Authentication may or may not now work

2017-11-13 01:19:12 +02:00

.eslintrc.json

Format and maybe break code

2017-11-21 14:30:59 +02:00

.gitignore

Authentication may or may not now work

2017-11-13 01:19:12 +02:00

example-config.yaml

More code

2017-11-21 00:10:34 +02:00

LICENSE

Initial commit

2017-11-12 17:42:45 +02:00

mautrix-telegram

Authentication may or may not now work

2017-11-13 01:19:12 +02:00

package-lock.json

Another sync commit with an useless message

2017-11-15 01:16:58 +02:00

package.json

Add script to download older telegram-mtproto commit

2017-11-20 21:46:59 +02:00

README.md

Update README.md

2017-11-16 17:57:55 +02:00

README.md

mautrix-telegram

Only the very basic functionality has been implemented.

A Matrix-Telegram puppeting bridge.

Usage

Create a copy of example-config.yaml and fill out the fields.
Generate the appservice registration with ./mautrix-telegram -g. You can use the -c and -r flags to change the location of the config and registration files. They default to config.yaml and registration.yaml respectively.
Run the bridge ./mautrix-telegram. You can also use forever: forever start mautrix-telegram (probably, I didn't actually test it).
Invite the appservice bot to a private room and view the commands with !tg help.