HMD / Dev Guide

Health and Metrics

1. Open HMD from an allowed HMD/dev/admin account.
2. Review system, storage, and database snapshots.
3. Use logs to inspect recent platform activity.
4. Check service scale estimates in Admin if needed.

Emergency Controls

1. Use shutdown only when the server needs to block normal users.
2. Shutdown keeps owner/admin/HMD access available.
3. Restart returns service to normal access.
4. Create backups before risky changes.

Friends and Account Data

• Friend discovery depends on saved account/profile grade.
• If grade search looks empty, inspect the user record and profile grade.
• Same-grade users can discover each other; outside-grade adds require exact username.
• Profiles, friends, DMs, and groups are stored in the data directory shown by HMD/local tools.

Calls and Screen Share

• WebRTC config is returned from server state as rtcConfig.
• STUN is included by default, but real cross-network reliability needs TURN.
• Check INNER_TURN_URLS, INNER_TURN_USERNAME, INNER_TURN_CREDENTIAL, and INNER_RTC_RELAY_ONLY.
• Screen share needs browser display capture; many phones cannot initiate screen share.
• Failed/disconnected peers rebuild fresh offers in v213.

Localhost Tools

• Use localhost tools for desktop/local runs.
• Check persistence paths before testing uploads.
• Use the health endpoint after boot.
• Camera/mic require HTTPS or localhost, so localhost is valid for local call testing.

Advanced Tools

• Prepare bots and plugins.
• Configure AI provider settings where available.
• Review automod and moderation settings.
• Keep hidden admin/HMD tools restricted.
• Use dark/readable themes when reviewing UI from phones at night.