Temporarily disable sending metaverse username in domain connect request due to signature requirements

This commit is contained in:
MayaTheShy
2025-11-16 19:42:23 -05:00
parent f32e3276fc
commit 1ed1ad2a28

View File

@@ -1397,11 +1397,12 @@ void OverteClient::sendDomainConnectRequest() {
qs.writeQString(""); qs.writeQString("");
// 14. Directory services (metaverse) username (QString) // 14. Directory services (metaverse) username (QString)
// TEMPORARILY DISABLED: Sending username might require signature
std::string metaverseUsername = ""; std::string metaverseUsername = "";
if (m_auth && m_auth->isAuthenticated()) { // if (m_auth && m_auth->isAuthenticated()) {
metaverseUsername = m_auth->getUsername(); // metaverseUsername = m_auth->getUsername();
std::cout << "[OverteClient] Including metaverse username: " << metaverseUsername << std::endl; // std::cout << "[OverteClient] Including metaverse username: " << metaverseUsername << std::endl;
} // }
qs.writeQString(metaverseUsername); qs.writeQString(metaverseUsername);
// 15. Username signature (QString) - empty (no keypair authentication yet) // 15. Username signature (QString) - empty (no keypair authentication yet)