You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 786ecad
Browse filesBrowse the repository at this point in the historyBrowse files
committed
fix(navigation): let bare buzz:// open Buzz without a broken-link notice
Builderlab's console "Open Buzz app" links to bare `buzz://`. The OS ingress
treated it as malformed, so the button showed "This link doesn't work" (and
opened Inbox on a cold start). Native already brings the app forward on any
deep link, so ingress now skips bare `buzz://` and `buzz:///`: no notice, no
navigation, and it never displaces a real link queued in the same batch.
Other malformed links keep the notice; tests that used `buzz://` as their
malformed example now use `buzz://unknown`.
Co-authored-by: Vimes <d26902ac60a55be3ce7c6bb44cf3b0a0a09cf3b89067f6d9cc6e2e5015bd59a3@remote-agent-pilot.communities.buzz.xyz>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: Stuart Douglas <[email protected]>
-`buzz://` (also `buzz:///`), the Builderlab console's **Open Buzz app**: it
34
+
only brings Buzz to the front and opens nothing, at cold start too. It shows
35
+
no notice and never replaces a link still waiting to open
33
36
34
37
External authorization links show owner consent. They never grant access on arrival. The [external app protocol](agents.md#external-app-authorization) defines the callback, S256 exchange, scopes, and expiry. Handshake values stay outside navigation history.
35
38
@@ -105,7 +108,7 @@ link; HTTPS itself is not registered as an OS handler. `buzz://connect`
105
108
community **Open in Buzz**; `name` is ignored) are the same form without a code:
106
109
they open the join dialog with the relay prefilled or, when this device already
107
110
belongs to that community, switch to it. Links that name no destination, such
108
-
as bare `buzz://`, unknown hosts, missing or malformed parameters, malformed join
111
+
as unknown hosts, missing or malformed parameters, malformed join
109
112
or community links, incomplete entity or plugin links and oversize links, show a "This
110
113
link doesn't work" notice. In a running app the notice shows over the current
111
114
page, and history is unchanged. A link that launches the app, read before the
@@ -156,7 +159,7 @@ For OS ingress, use a packaged app or debug bundle. Write a link by hand, such a
156
159
`buzz://channel/general` or `buzz://message?channel=general&id=<64-hex event id>`.
157
160
A warm packaged app should come to the front and open the conversation. A cold
158
161
start should launch, show the start page, then open the destination once the
159
-
client is ready. A malformed link such as `buzz://` or
162
+
client is ready. A malformed link such as `buzz://unknown` or
160
163
`buzz://join?relay=example` must show the "This link doesn't work" notice over
161
164
the current page when warm, and open Inbox with it on a cold start. Ordinary `just desktop` keeps in-app Buzz links and
162
165
**Copy link**, but external `buzz://` delivery is not a supported development
0 commit comments