Slavi Pantaleev 2c719b2ef7 Update beeper-linkedin configuration to latest upstream config and properly pass double-puppeting login shared secrets ... We used to pass the shared secret for double-puppeting via a `login_shared_secret` parameter, which doesn't seem to exist anymore. The proper way to do it is via `login_shared_secret_map`. The comments for `login_shared_secret_map` seem to indicate that it's only usable with the shared-secret-auth password provider. However, this bridge is based on mautrix-python (`>=0.20.5,<0.21`) as per its `requirements.txt` Support for double-puppeting via arbitrary access tokens landed in mautrix-python 0.20.1 (6f25b62e80/CHANGELOG.md (L44-L53)), so it should be possible to use appservice double-puppet. Related to af04ca1238 A bunch of other parameters seem to have moved around as well. This patch introduces some new Ansible variables for controlling additional settings related to encryption, etc.		2024-12-02 20:00:08 +02:00
..
main.yml	Fix all 300+ ansible-lint-reported errors	2023-03-07 17:28:15 +02:00
setup_install.yml	Move configuration-creation tasks for beeper-linkedin before container-related tasks	2024-12-02 19:38:02 +02:00
setup_uninstall.yml	Optimize uninstall tasks a bit	2022-11-25 17:28:57 +02:00
validate_config.yml	Update beeper-linkedin configuration to latest upstream config and properly pass double-puppeting login shared secrets	2024-12-02 20:00:08 +02:00