Lexicon Garden

chat.yakka.resolveChannel

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).

Repository @yakka.chat did:plc:wpjoy2orkqq5m65vq7gg7liz namespace authority
Details · query
Kindquery
Authorityyakka.chat
Indexed
Compare Edit in builder → Fork →

Query

query · GET

Parameters

query string

ref

requiredstring

A channel name or a channel TID.

server

requiredstring · did

The server's DID.

Output

application/json

schema

ref
Reference

#output

object

Properties

kind

requiredstring

`renamed` means the ref matched by TID rather than by name — the caller should redirect to the name it now has.

  • knownValues: ok | renamed | forbidden | gone | notFound

name

string

The name a `gone` channel had, so a tombstone can say what it was.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • chat.yakka.resolveMessage

    query

    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.