From 6c1358d0c84bdd4d75549fb4723cca8997618bf6 Mon Sep 17 00:00:00 2001
From: strawberry <strawberry@puppygock.gay>
Date: Wed, 24 Jan 2024 12:15:23 -0500
Subject: [PATCH] send home_server on login response again

a 6+ year old deprecated field that isnt even spelled
right, and no clients use it must still be sent
according to spec

Signed-off-by: strawberry <strawberry@puppygock.gay>
---
 src/api/client_server/session.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/api/client_server/session.rs b/src/api/client_server/session.rs
index f3dc91fe..b7c8df09 100644
--- a/src/api/client_server/session.rs
+++ b/src/api/client_server/session.rs
@@ -184,7 +184,7 @@ pub async fn login_route(body: Ruma<login::v3::Request>) -> Result<login::v3::Re
 
     info!("{} logged in", user_id);
 
-    // home_server is deprecated but ruma skips serialising if None, so this is fine
+    // home_server is deprecated but apparently must still be sent despite it being deprecated over 6 years ago.
     // initially i thought this macro was unnecessary, but ruma uses this same macro for the same reason so...
     #[allow(deprecated)]
     Ok(login::v3::Response {
@@ -199,7 +199,7 @@ pub async fn login_route(body: Ruma<login::v3::Request>) -> Result<login::v3::Re
             }
         },
         expires_in: None,
-        home_server: None,
+        home_server: Some(services().globals.server_name().to_owned()),
         refresh_token: None,
     })
 }