12 lines
1.1 KiB
HTML
12 lines
1.1 KiB
HTML
<p>Session archives are how teams learn. Without them, every live is a rumor. With them, you can answer who gifted, when chat spiked, and whether the disconnect was 20 seconds or 20 minutes.</p>
|
||
<h2>What to store</h2>
|
||
<p>Event log (JSON or CSV), a short metadata file (room, start, end, operator), and optionally a recap note. Video is optional and heavy. Start with events.</p>
|
||
<h2>Naming</h2>
|
||
<p>Use UTC timestamps in filenames: <code>2026-08-24T1900Z-room-handle</code>. Human titles belong inside the metadata file. Clever folder art does not survive a second operator.</p>
|
||
<h2>Retention</h2>
|
||
<p>Decide a retention window before you accumulate a disk of chat logs. Personal data in comments is still personal data. Shorter is usually better.</p>
|
||
<h2>Export formats</h2>
|
||
<p>CSV for spreadsheets. JSON for tooling. If your only export is a screenshot, you do not have an archive.</p>
|
||
<h2>Access control</h2>
|
||
<p>Chat logs can include phone numbers, insults, and minors’ usernames. Do not dump archives into a shared drive with “everyone” access because it is convenient.</p>
|