chat.yakka.resolveMessage
Resolve a permalink fragment's message ref within a channel. `ambiguous` is the case the explicit fragment form exists to avoid: two authors can in principle mint the same TID in one channel. Rare at any single channel's scale, not impossible across many — so it is a case, not an assumption.
Details · query
| Kind | query |
|---|---|
| Authority | yakka.chat |
| Indexed |
Query
query · GETParameters
query string#output
objectProperties
candidates
arrayknownValues: ok | ambiguous | gone | notFound
message
refseq
integerA deleted message keeps its sequence so the timeline can still scroll to it (ADR 0010).
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Resolve a URL's channel segment, which may be a name or a TID. Called by the client's route guard before anything renders. The five outcomes are distinct on purpose. Collapsing them would either lie about deleted channels or hide gated ones, and both are facts a reader is entitled to. `forbidden` deliberately reveals that a channel exists — which is safe only because channels are whole spaces and the credential mint has already made the same disclosure (ADR 0007).