mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-12 21:53:00 -06:00
docs: explain Buzz archived room handling
This commit is contained in:
@@ -212,6 +212,11 @@ profile subscription does not reach EOSE within 10 seconds, OpenClaw treats the
|
||||
Buzz relay session as stalled and recycles only that Buzz account connection;
|
||||
the Gateway keeps running.
|
||||
|
||||
Archived rooms are omitted from directory results and live room subscriptions.
|
||||
If a configured room is archived or restored while OpenClaw is connected, the
|
||||
plugin recycles only its Buzz connection so the subscription set matches the
|
||||
relay's current metadata. The Gateway keeps running.
|
||||
|
||||
Each configured room uses one room-scoped relay subscription. OpenClaw reserves
|
||||
three of Buzz's 1,024 connection subscriptions for membership and metadata
|
||||
queries, so one account can configure up to 1,021 rooms. Near that limit,
|
||||
|
||||
@@ -49,7 +49,9 @@ openclaw directory groups members --channel buzz --group-id buzz:<ROOM_UUID>
|
||||
```
|
||||
|
||||
Buzz profile and room names are used as display labels, while public keys and
|
||||
room UUIDs remain the stable identities.
|
||||
room UUIDs remain the stable identities. Archived rooms are omitted; an
|
||||
archive or restore event rebuilds only the Buzz connection's room
|
||||
subscriptions and does not stop the Gateway.
|
||||
|
||||
Send a test message:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user