How it works
Each message contributes to the hourly score as a single signal. We count the event, not the content.
New joins add activity weight so growth spikes are visible even when chat is quiet.
Commands, buttons, and other bot interactions count as direct engagement with Forge.
Voice join/leave and active time contribute to the score without recording transcripts or audio.
What we do not collect
The feature stores weighted event metadata only. It is intentionally narrow so the public profile can show activity without exposing private conversation data.
Trend calculation
Trend percentages compare the last 24 hours with the previous 24 hours.
If the previous window is too small or the difference is too noisy, the trend stays hidden instead of showing a misleading percentage.
The public chart renders in the viewer's browser timezone when available. That makes the hour labels read naturally for each visitor.
Telemetry is kept only as long as the feature needs it, then cleaned up automatically by the retention job.
Owners can enable or disable the chart at any time from the dashboard. The public card respects that setting immediately.
FAQ
No. Server owners must enable it manually in the dashboard.
The chart renders in the viewer's browser timezone when available. If not, it falls back to UTC.
Telemetry is retained only for the window the feature needs, then cleaned up automatically.
The chart is meant to be useful, not invasive.
If the activity signal is not strong enough to be meaningful, the UI should stay quiet. That is better than exaggerating change or implying we know more than we do.