From 82886e4c8f0a639dba38ba91b625bee12b8c2357 Mon Sep 17 00:00:00 2001 From: Matthew Hodgson Date: Wed, 12 Dec 2018 00:57:39 +0000 Subject: hide_profile: false should mean not to hide the profile :/ --- synapse/handlers/profile.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'synapse/handlers/profile.py') diff --git a/synapse/handlers/profile.py b/synapse/handlers/profile.py index 58e9181f01..0a952dab97 100644 --- a/synapse/handlers/profile.py +++ b/synapse/handlers/profile.py @@ -274,9 +274,9 @@ class BaseProfileHandler(BaseHandler): """ Sets the 'active' flag on a user profile. If set to false, the user account is considered deactivated or hidden. - If 'hide' is true, then we just try hide the user rather than deactivate it. - This means withholding it from replication (and mark it as inactive) rather than - clearing the profile from the HS DB. + If 'hide' is true, then we interpret active=False as a request to try to hide the + user rather than deactivating it. This means withholding the profile from replication + (and mark it as inactive) rather than clearing the profile from the HS DB. Note that unlike set_displayname and set_avatar_url, this does *not* perform authorization checks! This is because the only place it's used currently is in account deactivation where we've already done these checks anyway. -- cgit 1.5.1