| 28 Sep 2020 |
 Myrex | fair enough | 13:01:31 |
| Myrex | seems checklist didn't help, but helped leaving private with bot and creating it again | 13:28:16 |
| Myrex | for future reference - why it could happen? | 13:28:40 |
 Sunita Shou | Redacted or Malformed Event | 13:50:33 |
|  CHAN .KIM joined the room. | 17:55:06 |
|  Amy joined the room. | 21:00:12 |
| 29 Sep 2020 |
|  @romanjankowski:matrix.org left the room. | 03:22:53 |
 dexterlb | tulir: the setup.py of all mautrix- projects seems to copy example-config.yaml into /usr instead of into /etc/<project> or /usr/lib/<project> or something similar | 08:52:39 |
| dexterlb | is this expected? | 08:52:47 |
 tulir | yes, that's why the setup instructions include a virtualenv | 08:53:07 |
| dexterlb | ok, thanks | 08:53:24 |
 Oleg | Is it possible to use matrix bots in a telegram bridged room? | 14:24:43 |
| tulir | yes | 14:27:44 |
| Oleg | Do I need to have a relaybot functionality for that?
Currently I created a matrix room and then run !tg create group. The replies of the bots are this way not bridged to Telegram. | 14:31:43 |
| Oleg | * Do I need to have a relaybot functionality for that?
Currently I created a matrix room and then run !tg create group. The replies of the bots are this way not bridged to Telegram. | 14:35:38 |
|  @ka3jgx:matrix.org left the room. | 14:49:31 |
| tulir | In reply to @oleg:fiksel.info
Do I need to have a relaybot functionality for that?
Currently I created a matrix room and then run !tg create group. The replies of the bots are this way not bridged to Telegram. well yes you obviously need some telegram-side account for bridging the messages | 15:19:03 |
| tulir | which means either using the relaybot or logging the matrix bots into telegram (which can also be done with a telegram bot token) | 15:19:29 |
|  jwh joined the room. | 17:11:45 |
|  telegram_1290015299 joined the room. | 17:28:07 |
| jwh | hm | 17:30:27 |
| jwh | something has gone awry, getting user not registered and also some telegram users don't get created (and then the bridge can't decrypt anything sent obviously) | 17:31:13 |
| jwh | doesn't look like it even tries | 17:31:25 |
| jwh | mautrix.errors.request.MForbidden: Application service has not registered this user - only for some DMs though | 17:41:13 |
| tulir | you can try setting registered=false in the puppet table | 17:49:48 |
| jwh | ah hm | 17:53:37 |
| Oleg | In reply to @tulir:maunium.net
well yes you obviously need some telegram-side account for bridging the messages Thanks Tulir!
I was just confused, that m.notice were not bridged and that why I was thinking, that the bridging doesn't work. | 20:44:49 |
| tulir | oh there's probably some additional option for m.notice specifically | 20:45:18 |
| tulir | (but a relaybot or puppeting is required anyway) | 20:45:28 |
|  xzax_ joined the room. | 21:04:57 |
