Files
chanora/poc/tsclientlib-channel-query-spike/VERIFICATION.md
T

61 lines
1.7 KiB
Markdown

# Verification record — `tsclientlib-channel-query-spike`
## Result
PASS. On 2026-05-25, the spike connected to `kr.teamspeak.app`, listed the
visible channels, resolved channel `1`, requested its description, and printed
live channel metadata plus current occupants from a normal TeamSpeak client
session.
## Environment
| Field | Value |
|---|---|
| Date | 2026-05-25 |
| Host OS | Linux (x86_64) |
| Build profile | dev |
| Target server | `kr.teamspeak.app` |
## Command
```bash
cargo run --offline -- \
--address kr.teamspeak.app \
--nickname ChanoraPoC-ChannelInspector \
--target-channel-id 1
```
## What was observed
- The visible channel table populated successfully from the live client state.
- Channel `1` resolved as `Default Channel`.
- `channelgetdescription` succeeded and populated the channel description in
`tsclientlib` state.
- Printed channel data for `Default Channel`:
- `cid=1`
- parent: `Root (0)`
- topic: `Default Channel`
- type: `Permanent`
- default channel: `Yes`
- password-protected: `No`
- codec: `OpusMusic`
- codec quality: `6`
- unencrypted: `No`
- max clients: `Unlimited`
- max family clients: `Unlimited`
- needed talk power: `-1`
- GUID: `76789d5c-8aac-4740-9d03-e66f09317153`
- icon id: `399174223`
- Channel description was visible and included bilingual contact text pointing
users to `me@edison.network`.
- Current occupancy for channel `1` during the run:
- `ChanoraPoC-ChannelInspector`
- `EdisonJwa`
- `observer`
## Conclusion
This spike proves that a normal TeamSpeak client connection can inspect visible
channel metadata, request channel descriptions, and enumerate current occupants
without ServerQuery credentials.