social.coves.community.post.getStatus
Get one community's admission decision about one post. Intentionally UNAUTHENTICATED: the caller with the strongest need is an author on another server whose post is pending on this host, and they have no account here to authenticate with. It is also the only way a rejection is reachable at all - a submission refused before it was ever accepted writes no community record, so there is no repository record and no firehose event carrying it, and without this endpoint an author whose post vanished could never learn that it was refused or why. The accepted cost is that anyone who can name a post AT-URI learns its status in a community. Both parameters are required: a post carries independent decisions from several communities, so there is no single status of a post.
Details · query
| Kind | query |
|---|---|
| Authority | post.community.coves.social |
| Indexed |
Query
query · GETParameters
query stringOutput
application/jsonacceptanceUri
string · at-uriAT-URI of the live community acceptance record, so the caller can read the signed attestation rather than trusting this AppView's summary of it. Present only while an acceptance stands.
decisionAt
string · datetimeWhen the refusal above was decided
decisionCode
stringWhy the post was refused. Present only for rejected and removed. The vocabulary is open and spans both the codes a community publishes in a removal record and the admission-time codes that never reach a repository.
The community's decision state. Reported verbatim rather than collapsed: an author who edited an accepted post needs pending_reacceptance to be distinguishable from a post that was never accepted, because the two have completely different next steps.
knownValues: pending | accepted | pending_reacceptance | rejected | removed
Errors
InvalidRequest
A missing or malformed post or community parameter
NotFound
This community has no decision about this post
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Whether the AppView accepted records the caller wrote to their own repository. Community records are projected from the firehose, not written through this service, so a record that violates a rule this service enforces — a name already taken, a post link the Community's postPolicy forbids — lands in the author's repository and is then silently dropped. This is how the author finds out. Only the caller's own records may be queried.
-
app.didpic.admin.getPost
queryGet a post or comment's moderation state and labels.
-
Minimal author info for blocked posts
-
A community's attestation that it accepts a post. Written only by the community's key holder, automatically once admission checks pass - machine attestation, not human approval. The community is implicit in the repository this record lives in. The record key is deterministic: the unpadded lowercase base32 encoding of the SHA-256 digest of the canonical subject AT-URI (fixed 52 characters, always rkey-safe), so a post has exactly one acceptance rkey per community, concurrent writers converge idem