c04a8583bf
chore: upgrade bridges + bridge DBs
...
cc-ci/testme cc-ci: success
signalbridge: v0.8.7 -> v0.2606.0 (calver scheme change, already Go-based)
telegrambridge: v0.15.3 -> v0.2606.0 (Python->Go bridgev2 rewrite; config template rewritten)
signaldb/telegramdb/discorddb: postgres 13-alpine -> 14-alpine (PG13 EOL; conservative one-major bump)
.env.sample: TELEGRAM_BRIDGE_PERMISSIONS relaybot -> relay (Go bridgev2 permission rename)
2026-06-23 01:28:29 +00:00
d02981a2bf
feat: sync_channel_members configurable for telegram bridge
2023-05-10 17:57:54 +02:00
1a0211b743
fix: quote YAML inline dicts correctly
2023-01-08 01:56:30 +01:00
245e81e4bb
fix: make bridge logging ERROR only
...
Decryption happens on the bridges (between systems) so in order to stop
plaintext logging of chat messages, we default to ERROR. If people need
more, they can submit changes for customisation.
2023-01-08 01:11:58 +01:00
9b12e4a0eb
refactor!: unlimited permissions bridge config
2023-01-08 01:04:52 +01:00
1e8b616cba
feat: shared secret auth
2022-09-22 16:01:19 +02:00
2beb6e4bf0
feat: telegram bridge admins
2022-05-15 10:59:50 +02:00
00b0375b1c
fix: no underscore, synapse doesn't like it
2022-05-15 10:39:42 +02:00
dd4841dbe0
fix: telegram bot - hacking it until it runs
2022-05-12 22:27:12 +02:00
