Handles, Usernames & 7-Day Cooldown
Global identity addressing, unique handle constraints, and atomic 7-day rate-limiting cooldowns.
#The NSGO Global Handle
In the NS ecosystem, your handle (@handle) is your universal identifier. It is what other developers see on the public leaderboard, how teammates find your profile at /u/[handle], and what connected tools use as your public moniker.
Unlike arbitrary display names, handles are strictly unique, case-insensitive, and immutable during active authentication sessions.
#Changing Your Handle
To update your handle, visit /account/profile under the "Basic Identity" tab:
1. Enter your desired handle in the "Propose New Handle" field.
2. NSGO performs real-time validation via check_username_details() to check availability, format, and blacklist rules.
3. If available and your account is eligible, click "Update Handle".
#The 7-Day Cooldown Protection
To prevent identity squatting, rapid cycling, impersonation, and broken links across connected services, handle updates enforce a strict 7-day database cooldown.
When you change your handle, the timestamp is recorded in the username_history audit table. The update_username() RPC rejects subsequent changes until exactly 7 full days (168 hours) have elapsed.
#Blacklist of Reserved Handles
NSGO maintains a database table of reserved keywords (reserved_usernames) that cannot be claimed by standard accounts. This includes system keywords (admin, root, administrator, system, guest), platform tools (nsgo, iplogger, nishdrop, vault, threatshield), and protocol terms (api, oauth, oidc, auth, jwks, well-known).