@@ -25,20 +25,23 @@ The OS ingress accepts the Buzz link forms and nothing else:
2525Entity sections are ` files ` , ` commits ` , ` issues ` , ` prs ` , ` contributors ` , and
2626` channels ` ; omitting the section opens the overview. Repository commit links add
2727` &tab=commits&commit=<40- or 64-hex hash> ` . Identifiers use 1-64 ASCII letters,
28- digits, ` _ ` , ` - ` , or ` . ` , without a leading dot or ` .. ` . Unknown or duplicate
29- parameters are rejected. The same forms work in message content.
28+ digits, ` _ ` , ` - ` , or ` . ` , without a leading dot or ` .. ` . Query parameters outside
29+ a form's grammar are ignored, with their values and any repeats, so a link that
30+ another client decorated still opens; a duplicated known parameter is rejected as
31+ ambiguous. The ` channel ` forms carry everything in the path and ignore any query.
32+ The same forms work in message content.
3033
3134None carries a community, so each binds to the currently selected community and
3235viewer, and fail ` unavailable ` when no community is selected or no identity is
33- known. Every other link, including ` buzz://open?target=… ` , ` buzz://join ` ,
34- incomplete entity links, unknown hosts and oversize links, fails as
35- ` invalid-target ` and shows "This destination couldn't open" with
36- ** Open Settings ** . Unsupported links have no Retry action. Nothing is
37- auto-joined. A valid address is never authorization: bound targets pass the same
38- viewer, membership and channel checks as in-app navigation, so a link into a channel
39- you cannot read still fails ` denied ` . The frontend expects the canonical lowercase
40- ` buzz: ` scheme; the native URL parser can normalize scheme case before delivery,
41- so uppercase OS input is not guaranteed to be rejected.
36+ known. Every other link, including ` buzz://join ` , incomplete entity links ,
37+ unknown hosts and oversize links, fails as ` invalid-target ` and shows "This
38+ destination couldn't open" with ** Open Settings ** . Unsupported links have no
39+ Retry action. Nothing is auto-joined. A valid address is never authorization:
40+ bound targets pass the same viewer, membership and channel checks as in-app
41+ navigation, so a link into a channel you cannot read still fails ` denied ` . The
42+ frontend expects the canonical lowercase ` buzz: ` scheme; the native URL parser
43+ can normalize scheme case before delivery, so uppercase OS input is not
44+ guaranteed to be rejected.
4245
4346The latest arriving link wins. Before readiness, one pending intent is retained;
4447if identity or community is missing, select a community and use ** Retry navigation** .
@@ -61,8 +64,9 @@ explicit Git sections report navigation failure, not an empty successful page.
6164This deliberately omits the sender's community and identity: recipients must select
6265the correct community before opening it. Original mobile Buzz requires a UUID
6366channel identifier; named development channels are supported here but do not imply
64- mobile compatibility. Existing ` buzz://open ` locators still preserve community
65- context for in-app use and remain unsupported at the OS boundary.
67+ mobile compatibility. The app has no link form of its own beyond the Buzz ones:
68+ unknown ` buzz:// ` hosts are rejected everywhere, staying plain text in message
69+ content and failing ` invalid-target ` at the OS boundary.
6670
6771## Testing locally
6872
0 commit comments