From dad9e1426cf1ae04d5b71ad5e4610a96d659d239 Mon Sep 17 00:00:00 2001 From: Bardi Harborow Date: Wed, 4 Nov 2026 22:03:24 +1100 Subject: [PATCH] fix: Advertise m.forget_forced_upon_leave capability according to config --- changelog.d/2452.bugfix.md | 1 + src/api/client/capabilities.rs | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) create mode 100644 changelog.d/2452.bugfix.md diff --git a/changelog.d/2452.bugfix.md b/changelog.d/2452.bugfix.md new file mode 100644 index 000000000..451d8a020 --- /dev/null +++ b/changelog.d/2452.bugfix.md @@ -0,0 +1 @@ +The `m.forget_forced_upon_leave` capability now reflects the `forget_forced_upon_leave` config option instead of always being advertised as enabled. diff --git a/src/api/client/capabilities.rs b/src/api/client/capabilities.rs index 28a5e0fc5..d5d6e9f56 100644 --- a/src/api/client/capabilities.rs +++ b/src/api/client/capabilities.rs @@ -46,7 +46,8 @@ pub(crate) async fn get_capabilities_route( capabilities.get_login_token = GetLoginTokenCapability::new(services.server.config.login_via_existing_session); - capabilities.forget_forced_upon_leave.enabled = true; + capabilities.forget_forced_upon_leave.enabled = + services.server.config.forget_forced_upon_leave; if services.users.is_admin(sender_user).await { capabilities.account_moderation.lock = true;