app.userinput.edit
A revision of a discussion or reply, written as a sidecar that points at the original (never mutating it). Only honored when authored by the subject's own author; the newest createdAt is the live content, and the full set is the edit history. Lives in the author's repo.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | userinput.app |
| Indexed |
Record
record · key tidProperties
body
stringReplacement body.
maxLength: 20000maxGraphemes: 10000
The discussion or reply being revised. Indexed by constellation at subject.uri. The pinned cid identifies the version this edit was authored against.
tags
arrayReplacement tag values (discussion edits only), drawn from the space's tag list.
maxLength: 8
maxLength: 64
title
stringReplacement title (discussion edits only).
maxLength: 600maxGraphemes: 300
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
app.userinput.reply
recordA reply on a discussion. Lives in the author's repo.
-
app.userinput.discussion
recordA piece of feedback posted into a space. Lives in the author's repo and points at the space.
-
An author.s request to admit an exact version of their own post. discussion distinguishes a reply opt-in from a root submission.
-
app.atmobb.discussion.reply
recordA reply in a thread. Lives in the author's repo. Flat by default; parent enables quote-chain threading.
-
One revision of a post's text. Bluesky's AppView ignores updates to `app.bsky.feed.post` records, so an edit is expressed as a new record here rather than as a mutation of the post. Clients that understand this collection display the highest-numbered revision in place of the post's original text; clients that do not see the original, unchanged. The record key is `<postRkey>.<editNumber>` (for example `3abc123.1`); split on the LAST `.`, since TID-style record keys may themselves contain dots.