diff --git a/docs/buzz-help.md b/docs/buzz-help.md index b3ac9dd387..c1da4487d9 100644 --- a/docs/buzz-help.md +++ b/docs/buzz-help.md @@ -158,8 +158,31 @@ that agent in Buzz; they do not notify the external app through this connection. the same key as another shortcut, Settings → Shortcuts marks it "Also used by"; change one of them to choose which fires. - **Sharing a Solo chat** grants access to its conversation history, not only - the next message. Copying its link alone does not grant access. Check the - intended people and destination before changing access. + the next message. Its access dialog offers **View only** for community reading + or **Private** for people added to the chat. Public is not offered in + this UI; a Public policy set through another client appears as + **Public (existing)**. This is not protocol enforcement. View-only visitors + cannot post; existing members keep their roles. Returning to Private warns + about retained viewers unless verified roles show no Guests, including while + roles load or fail to load; remove them in People to end their access. Public + (existing) → Private also warns that joined members retain their access. + Public (existing) → View only confirms that existing + members keep their access. Agents the owner adds through + access search or a composer mention receive Bot access so they can reply, + including with a Guest admission default. Conversion to a channel offers + Private, View only and Public, starts from the chat's current access, and saves + the selected policy. Choosing Private during conversion also warns that people + who joined keep their access until removed in People. Opening a private chat to the community warns that its full + history and Canvas, including workspace folders and agent instructions, become + readable. View only retains Guest admission. Copying its link alone does not grant access. Check the intended people + and destination before changing access. If an older saved invitation granted + view-only access, remove that person in People and invite them again for + participation. For an older unresolved invitation, use **Retry** in Outbox + or add the person again if the receipt is already Seen. After its 15-minute + delivery window, Buzz verifies the original command and current membership + before allowing a fresh participation invitation; failed checks keep the original. + If the original invitation was applied and the person was later removed, Retry + clears the old row without re-adding them. Use **Add** in People to invite them again. - **Sidebar width**: drag the sidebar's right edge, or focus its resize handle and use the Left/Right arrow keys. Double-click the handle to reset the width. Messages and plugin pages share the saved width within the same community diff --git a/docs/identity.md b/docs/identity.md index a76859d803..232034e740 100644 --- a/docs/identity.md +++ b/docs/identity.md @@ -1012,8 +1012,10 @@ message/event writes use this identity. [Join recovery](communities.md#packaged- records public progress before remote changes. The existing durable outbox retains uncertain delivery across restart; retry uses the same signed event with fresh HTTP authentication. Events older than 15 minutes get a strong ID readback instead of -being republished or silently re-dated. Missing/failed readback retains uncertainty; -the user must inspect the conversation before explicitly sending a new message. +being republished or silently re-dated. For ordinary messages, missing/failed +readback retains uncertainty; inspect the conversation before explicitly sending +another. Expired no-role Solo invitations have a narrower verified retirement +path through [Outbox Retry](solo/sharing.md). Protected media and uploads are native, because the webview cannot attach Blossom (kind 24242) authentication itself: ``, `