Why identity history matters
In a growing community, display-name changes make manual impersonation checks slow and inconsistent. The workflow creates a durable identity trail instead of relying on memory or screenshots.
Two-table design
One table stores the latest known member state. A second appends every detected identity change. This keeps current lookups fast while preserving audit history.
Hourly operation
- Fetch server members.
- Compare usernames and nicknames with stored state.
- Update current records.
- Append changed fields to history.
- Alert moderators when protected identities need review.
Human control
The automation surfaces evidence; moderators make the final judgment. This is safer than automatic punishment based on a name similarity alone.